Azure Policy (built-in definitions): what it can block and where it stops
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Azure Policy (built-in definitions) is a Azure mechanism. Azure Policy evaluates resource create and update requests against assigned policy definitions. It applies to resources at the scope of the assignment (management group, subscription, resource group) and their children, except notScopes and exemptions.
All mechanisms ยท Azure guardrails
Azure Policy evaluates resource create and update requests against assigned policy definitions. With the deny effect, a matching request is stopped before it reaches the resource provider; other effects such as modify and deployIfNotExists change or deploy settings instead of blocking.
Azure Policy evaluates create and update requests against assigned definitions. With the deny effect a matching request is stopped before it reaches the resource provider; modify and deployIfNotExists change or deploy settings instead. It applies at the scope of the assignment (management group, subscription or resource group) and below, except notScopes and exemptions.
Limits: deny acts on create and update, so existing matching resources are only marked noncompliant, and denyAction does not protect child and extension resources when a delete targets the parent. To test, set enforcementMode to DoNotEnforce on the assignment, or assign with the audit effect first. 27 library entries use Azure Policy, taken from the Azure/azure-policy repository.
Documented limits
- Deny acts on create and update requests; existing resources that match are only marked non-compliant. (source)
- Scopes excluded with notScopes are not evaluated at all. (source)
- Effects are evaluated in order, and an earlier modify or append can change the request so a deny does not trigger. (source)
- denyAction does not protect child and extension resources when the delete targets the parent. (source)
Testing before enforcement
Set enforcementMode to DoNotEnforce on the assignment to evaluate it before enforcement; the audit effect separately creates a warning event without stopping the request. (source)
The 27 library entries written in it
- Allowed locations for new resourcesAzure, Azure Policy (built-in definitions), region and residency
- Allowed resource typesAzure, Azure Policy (built-in definitions), resource and cost
- Not allowed resource typesAzure, Azure Policy (built-in definitions), resource and cost
- Do not allow deletion of resource typesAzure, Azure Policy (built-in definitions), organization integrity
- Allowed virtual machine size SKUsAzure, Azure Policy (built-in definitions), resource and cost
- Network interfaces should not have public IPsAzure, Azure Policy (built-in definitions), public exposure
- Network interfaces should disable IP forwardingAzure, Azure Policy (built-in definitions), network perimeter
- Gateway subnets should not have a network security groupAzure, Azure Policy (built-in definitions), network perimeter
- Configure storage accounts to disallow public blob accessAzure, Azure Policy (built-in definitions), public exposure
- Storage accounts should disable public network accessAzure, Azure Policy (built-in definitions), public exposure
- Storage accounts should have the specified minimum TLS versionAzure, Azure Policy (built-in definitions), encryption and keys
- Storage accounts should prevent shared key accessAzure, Azure Policy (built-in definitions), identity and privilege
- Storage SAS tokens should adhere to 7 day maximum validityAzure, Azure Policy (built-in definitions), data exfiltration
- Key vaults should have deletion protection enabledAzure, Azure Policy (built-in definitions), encryption and keys
- Azure Key Vault should use the RBAC permission modelAzure, Azure Policy (built-in definitions), identity and privilege
- Configure key vaults to enable the firewallAzure, Azure Policy (built-in definitions), network perimeter
- OS and data disks should be encrypted with a customer-managed keyAzure, Azure Policy (built-in definitions), encryption and keys
- Azure SQL Database should have Microsoft Entra-only authentication enabledAzure, Azure Policy (built-in definitions), identity and privilege
- Deploy diagnostic settings for Key Vault to Event HubAzure, Azure Policy (built-in definitions), logging and monitoring
- Application Insights components should block non-Entra ingestionAzure, Azure Policy (built-in definitions), logging and monitoring
- Configure Cognitive Services accounts to disable public network accessAzure, Azure Policy (built-in definitions), ai services
- Configure Cognitive Services accounts to disable local authenticationAzure, Azure Policy (built-in definitions), ai services
- Configure Azure AI Services resources to disable local key accessAzure, Azure Policy (built-in definitions), ai services
- Configure Azure Machine Learning workspaces to disable public network accessAzure, Azure Policy (built-in definitions), ai services
- Azure Machine Learning registry deployments restricted to the allowed registry (preview)Azure, Azure Policy (built-in definitions), ai services
- Microsoft Foundry agents and toolboxes should not use denied tools (preview)Azure, Azure Policy (built-in definitions), ai services
- Azure AI Search services should disable public network accessAzure, Azure Policy (built-in definitions), ai services
Where Act is behind
Act writes guardrails in the provider's own mechanisms and hands them to your pipeline to enforce, so it is bounded by what those mechanisms can express in each cloud. It does not apply them itself, the boundary types it names are AWS's and Azure's, and exception and waiver handling after a guardrail ships was described as roadmap.
Related pages
Sources
- Azure Policy (built-in definitions), read 10 Nov 2026
- Limit, read 10 Nov 2026
- Limit, read 10 Nov 2026
- Limit, read 10 Nov 2026
- Testing, read 10 Nov 2026
Last reviewed 16 Nov 2026.