Manage Infrastructure as Code — MOC
MS Learn path: Manage infrastructure as code using Azure · Prophecy: environments built from code, not clicks.
Planned concepts
IaC · Bicep · ARM templates · terraform · desired-state · azure-machine-configuration · azure-deployment-environments · configuration-drift · provisioning-pipeline · immutable-infrastructure · Azure Landing Zone IaC Accelerator
Modules in this path
- intro-infrastructure-as-code — what IaC is, declarative vs imperative, desired state
- use-bicep-arm — author & deploy with Bicep (and ARM templates) via a provisioning pipeline
- terraform-in-azure — cross-cloud IaC with the AzureRM provider, state file & lifecycle
- configuration-and-drift — parameterize config, detect/fix drift, keep environments reproducible
Skills
Declarative provisioning, Azure Machine Configuration/desired state, governed on-demand environments, and drift.
Evidence route
Complete the Bicep deploy and rollback lab for the provisioning foundation, then IaC desired state and pipeline maintenance. The second exercise separates resource provisioning, guest configuration, on-demand environments, drift, and pipeline operations.
Route check: From a what-if result and a guest-compliance report, say which system owns the discrepancy and which source-controlled change should fix it.
Practice questions
- az400-q-iac-001 — Bicep vs ARM templates
- az400-q-iac-002 — detecting Terraform configuration drift
Conceptual checkpoint
Explain the sequence in this path using one workload scenario: identify the boundary being changed, the identity or tool acting on it, the expected evidence, and the failure that would change your decision.
Sources and re-audit
- AZ-400 course overview, checked 2026-08-31.
- AZ-400 study guide, checked 2026-08-31.
Re-audit when the AZ-400 course path, study-guide effective date, or the services and permissions taught here change.