How I work: from intake to handover, as a pipeline

This is how I work: like a pipeline. Every assignment runs through the same stages — and prefers to fail early rather than late.

Pipelines I build for you

• intune-config-as-codeExport Intune and Microsoft 365 configuration (Microsoft365DSC), review it in Git and roll it out automatically to every tenant. With drift check.
  Azure DevOps · Microsoft365DSC
• azure-infra-bicepLanding zone, network and AVD host pools as Bicep. Plan, review, deploy — repeatable across test, acceptance and production.
  Bicep · ARM
• avd-image-buildBuild, test and publish the golden image to the host pool. Every month, no handwork.
  YAML · PowerShell
• workplace-drift-checkNightly check for drift in Intune and Azure, with a report in the morning. You see what's off before the user does.
  KQL · Graph
• tenant-security-baselineSecurity baseline (CIS, Microsoft) as code: review Conditional Access, Defender and Entra settings in Git and roll them out to every tenant. Compared with reality every night; drift becomes a pull request.
  Entra · Defender · Graph

# how-i-work.yml
trigger: new-assignment
pool: { name: Mand-IT, demands: [KRIS] }
stages:
  - stage: Intake       # listen first
  - stage: Analyse      # look at what's there
  - stage: FixAndBuild  # fix, build, as code where it counts
  - stage: SecurityGate # fail early, not late
  - stage: Deploy       # pipelines, no click-ops
  - stage: Handover     # your team carries on