Skip to content
Cloud Governance Tools

Azure blocks at create and update, and a deny does not touch what already exists

The library holds 30 Azure guardrails across 10 risk classes, written in Azure Policy (built-in definitions), Azure RBAC deny assignments (created by deployment stacks), Azure resource locks, Management group assignment. 28 of them have a documented way to test the effect before enforcing.

All guardrails ยท Azure mechanisms

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, while modify and deployIfNotExists change or deploy settings instead of blocking, and audit only warns. Effects are evaluated in order, so an earlier modify or append can change the request so a deny does not trigger. Existing resources that match are only marked noncompliant. Assignments cascade from management groups by inheritance, and scopes excluded with notScopes are not evaluated at all.

Three other mechanisms sit beside it. Resource locks block deletion or modification at a subscription, resource group or resource and override user permissions, but they apply only to control plane operations. Deny assignments attach deny actions to principals at a scope; Azure creates them for generally available scenarios such as deployment stack deny settings, and customer-managed deny assignments are in private preview. Management groups organize subscriptions into a hierarchy up to six levels deep. The library holds 30 Azure entries, 27 of them Azure Policy.

The mechanisms

The 30 entries

"Tested first" says whether the provider documents a way to see the guardrail's effect before enforcing it. Read 10 Nov 2026.
GuardrailCloudMechanismRisk classTested first
Allowed locations for new resourcesAzureAzure Policy (built-in definitions)Region and residencydocumented
Allowed resource typesAzureAzure Policy (built-in definitions)Resource and costdocumented
Not allowed resource typesAzureAzure Policy (built-in definitions)Resource and costdocumented
Do not allow deletion of resource typesAzureAzure Policy (built-in definitions)Organization integritydocumented
Allowed virtual machine size SKUsAzureAzure Policy (built-in definitions)Resource and costdocumented
Network interfaces should not have public IPsAzureAzure Policy (built-in definitions)Public exposuredocumented
Network interfaces should disable IP forwardingAzureAzure Policy (built-in definitions)Network perimeterdocumented
Gateway subnets should not have a network security groupAzureAzure Policy (built-in definitions)Network perimeterdocumented
Configure storage accounts to disallow public blob accessAzureAzure Policy (built-in definitions)Public exposuredocumented
Storage accounts should disable public network accessAzureAzure Policy (built-in definitions)Public exposuredocumented
Storage accounts should have the specified minimum TLS versionAzureAzure Policy (built-in definitions)Encryption and keysdocumented
Storage accounts should prevent shared key accessAzureAzure Policy (built-in definitions)Identity and privilegedocumented
Storage SAS tokens should adhere to 7 day maximum validityAzureAzure Policy (built-in definitions)Data exfiltrationdocumented
Key vaults should have deletion protection enabledAzureAzure Policy (built-in definitions)Encryption and keysdocumented
Azure Key Vault should use the RBAC permission modelAzureAzure Policy (built-in definitions)Identity and privilegedocumented
Configure key vaults to enable the firewallAzureAzure Policy (built-in definitions)Network perimeterdocumented
OS and data disks should be encrypted with a customer-managed keyAzureAzure Policy (built-in definitions)Encryption and keysdocumented
Azure SQL Database should have Microsoft Entra-only authentication enabledAzureAzure Policy (built-in definitions)Identity and privilegedocumented
Deploy diagnostic settings for Key Vault to Event HubAzureAzure Policy (built-in definitions)Logging and monitoringdocumented
Application Insights components should block non-Entra ingestionAzureAzure Policy (built-in definitions)Logging and monitoringdocumented
Configure Cognitive Services accounts to disable public network accessAzureAzure Policy (built-in definitions)AI servicesdocumented
Configure Cognitive Services accounts to disable local authenticationAzureAzure Policy (built-in definitions)AI servicesdocumented
Configure Azure AI Services resources to disable local key accessAzureAzure Policy (built-in definitions)AI servicesdocumented
Configure Azure Machine Learning workspaces to disable public network accessAzureAzure Policy (built-in definitions)AI servicesdocumented
Azure Machine Learning registry deployments restricted to the allowed registry (preview)AzureAzure Policy (built-in definitions)AI servicesdocumented
Microsoft Foundry agents and toolboxes should not use denied tools (preview)AzureAzure Policy (built-in definitions)AI servicesdocumented
Azure AI Search services should disable public network accessAzureAzure Policy (built-in definitions)AI servicesdocumented
Deployment stack deny settings (Azure RBAC deny assignment)AzureAzure RBAC deny assignments (created by deployment stacks)Organization integritynone found
Resource locks (CanNotDelete and ReadOnly)AzureAzure resource locksOrganization integritynone found
Allowed locations assigned at a management groupAzureManagement group assignmentRegion and residencydocumented

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.

Sources

  1. Azure Policy (built-in definitions), read 10 Nov 2026
  2. Azure RBAC deny assignments (created by deployment stacks), read 10 Nov 2026
  3. Azure resource locks, read 10 Nov 2026
  4. Management group assignment, read 10 Nov 2026

Last reviewed 16 Nov 2026.