# Allowed locations for new resources

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

Allowed locations for new resources is an Azure guardrail written in Azure Policy. Denies creation of resources in any location that is not on the allowed list you set in the policy parameter. What it breaks: deployments to other locations return 403, and the definition itself excludes resource groups, Microsoft.AzureActiveDirectory/b2cDirectories and resources that use the 'global' region.

```text
Built-in policy definition: Allowed locations
Definition ID: e56962a6-4747-49cd-b67b-bf8b01975c4c
Category: General
Supported effects: Audit, Deny, Disabled
policyRule (copied from the repository file):
{
    "if": {
      "allOf": [
        {
          "field": "location",
          "notIn": "[parameters('listOfAllowedLocations')]"
        },
        {
          "field": "location",
          "notEquals": "global"
        },
        {
          "field": "type",
          "notEquals": "Microsoft.AzureActiveDirectory/b2cDirectories"
        }
      ]
    },
    "then": {
      "effect": "[parameters('effect')]"
    }
  }
```

- **Blocks:** Denies creation of resources in any location that is not on the allowed list you set in the policy parameter.
- **Breaks:** Deployments to other locations return 403, and the definition itself excludes resource groups, Microsoft.AzureActiveDirectory/b2cDirectories and resources that use the 'global' region. ([source](https://raw.githubusercontent.com/Azure/azure-policy/master/built-in-policies/policyDefinitions/General/AllowedLocations_Deny.json))
- **Test before applying:** As for every Azure Policy guardrail: [how to test before enforcing](/mechanisms/azure-policy/)
- **Mechanism:** [Azure Policy (built-in definitions)](/mechanisms/azure-policy/): Resources at the scope of the assignment (management group, subscription, resource group) and their children, except notScopes and exemptions
- **Taken from:** [open source set](https://raw.githubusercontent.com/Azure/azure-policy/master/built-in-policies/policyDefinitions/General/AllowedLocations_Deny.json), MIT License, Azure/azure-policy repository, https://raw.githubusercontent.com/Azure/azure-policy/master/LICENSE

## What the source says

"This policy enables you to restrict the locations your organization can specify when deploying resources." (read 10 Nov 2026).

On what it breaks: "Excludes resource groups, Microsoft.AzureActiveDirectory/b2cDirectories, and resources that use the 'global' region."

## Related guardrails

- [Deny access outside approved Regions](/guardrails/aws-scp-deny-unapproved-regions/): AWS, Service control policies (SCPs), region and residency
- [Deny enabling or disabling opt-in Regions](/guardrails/aws-scp-deny-region-enable-disable/): AWS, Service control policies (SCPs), region and residency
- [Resource location restriction](/guardrails/gcp-orgpolicy-resource-locations/): Google Cloud, Organization Policy Service (managed and legacy constraints), region and residency
- [Allowed locations assigned at a management group](/guardrails/azure-mg-assignment-allowed-locations/): Azure, Management group assignment, region and residency

## Related pages

- [Allowed resource types (Azure Azure Policy)](/guardrails/azure-policy-allowed-resource-types/)
- [Not allowed resource types (Azure Azure Policy)](/guardrails/azure-policy-not-allowed-resource-types/)
- [Do not allow deletion of resource types (Azure Azure Policy)](/guardrails/azure-policy-deny-action-delete/)

## Sources

- Allowed locations for new resources: https://raw.githubusercontent.com/Azure/azure-policy/master/built-in-policies/policyDefinitions/General/AllowedLocations_Deny.json (read 10 Nov 2026)
- How to test it first: https://learn.microsoft.com/en-us/azure/governance/policy/concepts/assignment-structure (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/guardrails/azure-policy-allowed-locations/
