L11. Azure Policy & Blueprint Migration
Course outlineLesson 11 of 18
Use Azure Policy effects, initiatives and exemptions to govern resources. Learn remediation prerequisites and how deployment stacks and template specs replace legacy Blueprint deployments.
Quick answer: Azure Policy checks Azure resources against rules and acts through an effect: Deny blocks a non-compliant change, Audit reports it, and Modify or DeployIfNotExists fix it. Group policies into initiatives, assign them at management group, subscription or resource group scope, and use exemptions for justified exceptions. Azure Blueprints is being retired. Exam update: AZ-500 retired on August 31, 2026. Azure Policy carries over to its replacement exam: see SC-500 lesson 4: Azure Policy and Defender for Cloud standards.
What Is Azure Policy?
Azure Policy evaluates resources against rules (policy definitions) and reports or enforces compliance. Deny and Audit never change an existing resource: Deny stops future violations and Audit reports them. Modify and DeployIfNotExists can fix existing resources, but only when you run a remediation task.
Policy Effects
| Effect | Behavior |
|---|---|
| Deny | Blocks the resource creation/update if non-compliant |
| Audit | Allows the operation but marks the resource as non-compliant |
| Modify | Adds, replaces or removes a property or tag on create or update; remediation tasks fix existing resources |
| Append | Adds fields during create or update (legacy for tags: prefer Modify) |
| DenyAction | Blocks a specific action, such as deleting a resource |
| DeployIfNotExists | Deploys a related resource if it does not exist (for example, a diagnostic setting or the Azure Monitor Agent) |
| AuditIfNotExists | Audits if a related resource is missing |
| Disabled | Policy is defined but not enforced |
Initiatives (Policy Sets)
An Initiative is a collection of policy definitions grouped for a common goal. Example: the Microsoft cloud security benchmark initiative (formerly Azure Security Benchmark), which Defender for Cloud assigns by default, groups policies that implement that benchmark.
Assign an initiative to a management group, subscription, or resource group: all child resources inherit the assignment.
Exemptions and Exclusions
- Exclusion scope: Exclude a specific resource group or resource from a policy assignment entirely
- Exemption: Mark a specific resource or scope as Waiver or Mitigated, with an optional expiry date
Azure Blueprints
Blueprints are a legacy migration topic, not a recommended new deployment pattern. Microsoft documents phased retirement beginning July 31, 2026, with full retirement on January 31, 2027.
For new governance, use Azure Policy and RBAC assignments deployed through ARM or Bicep. Use deployment stacks to manage resource lifecycle and deny settings. Template specs optionally store versioned templates; stacks can deploy Bicep or ARM directly, so template specs are not mandatory. Inventory and test legacy Blueprint artifacts before migration.
References
- Policy effects
- Modify effect
- DeployIfNotExists
- Policy exemptions
- Blueprints phased retirement
- Migrate blueprints to deployment stacks
- AZ-500 retirement and legacy skills outline
Continue Learning
- ✓Deny blocks future violations; Audit reports them. Only Modify and DeployIfNotExists fix existing resources, through a remediation task
- ✓DeployIfNotExists and Modify effects require a managed identity on the policy assignment
- ✓Initiative = collection of policies for a common goal: assign once, covers all child resources
- ✓Exemptions (Waiver or Mitigated) show in compliance reports and can expire. Exclusion scopes have no built-in expiry and are changed through the assignment
- ✓Blueprints combined Policy, RBAC and templates; it is being retired in favour of Deployment Stacks plus Template Specs
1. What is the effect of an Azure Policy with the 'Deny' effect?
2. An Azure Policy initiative is best described as:
3. Which policy effect is recommended to add a required tag on creation and remediate existing untagged resources?