Study guide
12.1 Azure Policy for Security Governance: Definitions, Initiatives, Effects & Remediation
Microsoft Azure Security Technologies AZ-500
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Azure Security Architecture Foundation
1.1 Azure Security Engineer Role & Exam Logistics 1.2 Microsoft Cybersecurity Reference Architecture & Zero Trust Principles
2 Chapter 2: Secure Identity and Access - Authentication, MFA & PIM
2.1 Microsoft Entra ID Security, Users, and Groups 2.2 Authentication Methods, MFA, and Conditional Access Policy Design 2.3 Microsoft Entra Privileged Identity Management (PIM)
3 Chapter 3: Secure Identity and Access - RBAC & Workload Identity
3.1 Azure RBAC, Custom Roles, and Governance 3.2 Workload Identities and Managed Identities 3.3 External Identities and Cross-Tenant Collaboration
4 Chapter 4: Microsoft Entra Application Access & Consent Governance
4.1 Enterprise Applications, OAuth Permission Grants & Consent Governance 4.2 App Registrations, Permission Scopes & Service Principal Credentials
5 Chapter 5: Secure Azure Networking - Boundary & Perimeter Protection
5.1 Virtual Network Security & Micro-segmentation 5.2 Azure Firewall and Firewall Manager 5.3 Web Application Firewall (WAF) & Azure Front Door
6 Chapter 6: Secure Azure Networking - Private Access & Monitoring
6.1 Private Connectivity with Private Endpoints & Private Link 6.2 Azure Bastion & Remote Management Security 6.3 Network Perimeter Protection & Flow Monitoring
7 Chapter 7: Network Architecture, Routing & Hybrid Connectivity
7.1 Azure Virtual Network Manager, Network Groups & User-Defined Routes 7.2 VPN Gateway, ExpressRoute Encryption & Virtual WAN Secured Hub 7.3 Network Integration for App Service, Functions, App Service Environment & SQL Managed Instance
8 Chapter 8: Public and Edge Access Protection
8.1 Azure Application Gateway Security, TLS Policy & Mutual Authentication 8.2 Azure Front Door, CDN Caching & TLS for App Service and API Management
9 Chapter 9: Compute, Container & Registry Security
9.1 Azure Virtual Machine Hardening & Host Security 9.2 Azure Key Vault Deep Dive & Secrets Lifecycle 9.3 Container & Azure Kubernetes Service (AKS) Security 9.4 Azure Container Instances, Container Apps & Registry Access Control
10 Chapter 10: Storage Security, Access Methods & Data Protection
10.1 Storage Account Security & Access Controls 10.2 Selecting and Configuring Access to Azure Files 10.3 Selecting and Configuring Access to Azure Blob Storage 10.4 Storage Data Protection: Soft Delete, Versioning, Point-in-Time Restore & Backup
11 Chapter 11: Data Platform & Database Security
11.1 Azure SQL Database Security & Always Encrypted 11.2 Database Auditing & Vulnerability Assessment 11.3 Data Discovery, Classification, & Microsoft Purview Integration
12 Chapter 12: Cloud Governance, Key Lifecycle & Asset Protection
12.1 Azure Policy for Security Governance: Definitions, Initiatives, Effects & Remediation 12.2 Key Vault Backup, Recovery & Automated Key Rotation 12.3 Implementing Security Controls to Protect Backups 12.4 Security Controls for Asset Management: Locks, Tags, Resource Graph & Azure Arc
13 Chapter 13: Microsoft Defender for Cloud - Posture & Workload Protection
13.1 Microsoft Defender for Cloud & Secure Score 13.2 Defender Cloud Workload Protection (CWP) Plans 13.3 Defender for Cloud Inventory, Compliance Standards & Custom Standards 13.4 Connecting AWS and GCP Environments to Microsoft Defender for Cloud
14 Chapter 14: External Attack Surface & Vulnerability Management
14.1 Microsoft Defender External Attack Surface Management (EASM) 14.2 Agentless Scanning & Microsoft Defender Vulnerability Management for Azure VMs 14.3 Defender for Cloud DevOps Security: GitHub, Azure DevOps & GitLab
15 Chapter 15: Security Monitoring, Microsoft Sentinel & Automation
15.1 Azure Monitor Data Collection Rules & Network Security Event Monitoring 15.2 Microsoft Sentinel Data Connectors, Content Hub & Normalization 15.3 Microsoft Sentinel Workspace & KQL Threat Hunting 15.4 Sentinel Incident Management & SOAR Automation
12.1 Azure Policy for Security Governance: Definitions, Initiatives, Effects & Remediation
Key Takeaways Explain This Topic AI
Azure Policy governs resource properties while Azure RBAC governs who may act — the exam pairs them, never substitutes one for the other.
Effect evaluation runs Disabled first, then Append and Modify, then Deny, then Audit, with AuditIfNotExists and DeployIfNotExists running after the resource provider succeeds.
DeployIfNotExists and Modify assignments require a managed identity holding the roles needed to perform the remediation.
A remediation task is what brings pre-existing non-compliant resources into line; assignment alone only affects new or updated resources.
Exemptions with a Waiver or Mitigated category are the auditable way to accept risk, unlike removing the scope from the assignment.
Last updated: August 2026
Policy vs RBAC vs Locks
Three governance mechanisms, three different jobs:
- Mechanism Question it answers Example
- Azure RBAC Who can perform an action? Only the platform team can create virtual networks
- Azure Policy What may the resource look like? No storage account may allow public blob access
- Resource locks May this resource be deleted or changed at all? The production hub VNet cannot be deleted
A user with Owner rights still cannot create a resource that a Deny policy forbids — that is why Policy, not RBAC, is the answer to "prevent anyone, including administrators, from creating X".
The Object Model
Policy definition — one rule: an if condition over resource properties and a then effect.
Initiative (policy set) — a bundle of definitions treated as one compliance unit. The Microsoft Cloud Security Benchmark (MCSB) is the default initiative assigned by Microsoft Defender for Cloud, and regulatory standards such as PCI DSS, ISO 27001, and NIST SP 800-53 ship as initiatives too.
Assignment — the definition or initiative applied at a management group, subscription, resource group, or resource scope, with parameters and optional notScopes exclusions.
Compliance state — Compliant, Non-compliant, Exempt, Conflicting, or Not started.
Scope inheritance flows downward, so a Deny assigned at a management group applies to every subscription beneath it. That is where security baselines belong.
Effects and Evaluation Order
- Effect Behaviour
- Disabled Turns the rule off for testing without deleting the assignment
- Append Adds fields to the request payload (legacy; Modify is preferred)
- Modify Adds, updates, or removes properties or tags — needs a managed identity
- Deny Blocks the create or update request outright
- DenyAction Blocks a specific action , most usefully DELETE , protecting resources from removal
- Audit Records non-compliance without blocking
- AuditIfNotExists Audits when a related resource is missing (for example, no diagnostic setting)
- DeployIfNotExists Deploys the missing related resource — needs a managed identity
- Manual Attestation-based control for process requirements that Azure cannot evaluate
Evaluation order matters: Disabled is checked first, then Append and Modify , then Deny , then Audit . The IfNotExists effects ( AuditIfNotExists , DeployIfNotExists ) are evaluated after the resource provider has returned a success code, because they need the resource to exist before they can look for its companion. The practical consequence: a Modify effect can alter a payload that a Deny then rejects, and a DeployIfNotExists never fires on a request that Deny already blocked.
Managed identity for deployment effects
DeployIfNotExists and Modify assignments create resources or change properties on your behalf, so the assignment needs an identity:
Choose system-assigned or user-assigned on the assignment.
Grant that identity the roles listed in the policy definition's roleDefinitionIds — for example, Log Analytics Contributor for a diagnostic-settings policy.
Grant them at a scope covering the resources being remediated. Missing role assignments are the single most common cause of "the policy shows non-compliant and remediation fails".
Remediation: Fixing What Already Exists
Assigning a policy only evaluates and enforces on new or updated resources. Everything already deployed is simply marked non-compliant. To fix them:
Create a remediation task from the assignment (portal, az policy remediation create , or Start-AzPolicyRemediation ).
The task enumerates non-compliant resources and invokes the deployment or modification using the assignment's managed identity.
Track progress per resource; failures usually trace back to missing role assignments or resource locks.
Evaluation itself runs on a roughly 24-hour cycle plus on resource change, and can be triggered on demand with an on-demand compliance scan when you do not want to wait.
Exemptions vs Exclusions
Both remove enforcement, but only one leaves an audit trail:
- Mechanism How it works Auditability
- Exclusion (notScopes) Scope removed from the assignment Weak — invisible unless you read the assignment
Exemption A dated object on the resource with category Waiver (accepting the risk) or Mitigated (handled by another control), plus an expiry date and description Strong — appears in compliance reporting as Exempt
Use exemptions for accepted risk so the acceptance expires and gets re-reviewed. Use exclusions only for scopes that structurally do not belong, such as a sandbox management group.
Where Policy Reaches Beyond ARM
Azure Policy for Kubernetes installs a Gatekeeper v3 admission controller add-on so definitions evaluate Kubernetes objects at admission time — the mechanism behind Pod Security Standards enforcement on AKS.
Machine configuration (guest configuration) audits and configures settings inside Windows and Linux virtual machines, which is how OS security baselines become measurable compliance data.
Defender for Cloud consumes all of this: your Secure Score recommendations are backed by policy definitions, and adding a custom initiative is how a custom standard appears on the regulatory compliance dashboard.