# Allowed locations assigned at a management group

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

Allowed locations assigned at a management group is an Azure guardrail written in management group assignment. Assigning the Allowed locations policy at a management group applies it to every subscription and resource under that group through inheritance, so one assignment covers many subscriptions.

```text
Management group scope for Azure Policy: assign the built-in definition "Allowed locations" (ID e56962a6-4747-49cd-b67b-bf8b01975c4c, see azure-policy-allowed-locations) at the management group.
Microsoft's documented example: "You can create a hierarchy that applies a policy, for example, that limits VM locations to the West US region in the management group called Corp".
```

- **Blocks:** Assigning the Allowed locations policy at a management group applies it to every subscription and resource under that group through inheritance, so one assignment covers many subscriptions.
- **Breaks:** Policy and access assigned at a management group cascade to all child subscriptions, and scopes listed in notScopes on the assignment are skipped entirely: they are not evaluated or included in the compliance count. ([source](https://learn.microsoft.com/en-us/azure/governance/policy/concepts/scope))
- **Test before applying:** Set enforcementMode to DoNotEnforce on the policy assignment made at the management group, which Microsoft documents as the way to evaluate an assignment before enforcement. ([source](https://learn.microsoft.com/en-us/azure/governance/policy/concepts/assignment-structure))
- **Mechanism:** [Management group assignment](/mechanisms/management-groups/): All subscriptions and resources under the management group in the hierarchy
- **Taken from:** [provider documentation](https://learn.microsoft.com/en-us/azure/governance/management-groups/overview), provider documentation

## What the source says

"You can create a hierarchy that applies a policy, for example, that limits VM locations to the West US region in the management group called Corp" (read 10 Nov 2026).

On what it breaks: "Resources within these scopes aren't evaluated or included in the compliance count."

## 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 for new resources](/guardrails/azure-policy-allowed-locations/): Azure, Azure Policy (built-in definitions), region and residency

## Related pages

- [Disable service account key creation (Google Cloud Organization Policy Service)](/guardrails/gcp-orgpolicy-disable-sa-key-creation/)
- [Disable automatic IAM grants for default service accounts (Google Cloud Organization Policy Service)](/guardrails/gcp-orgpolicy-no-auto-iam-grants-default-sa/)
- [Require OS Login (Google Cloud Organization Policy Service)](/guardrails/gcp-orgpolicy-require-os-login/)

## Sources

- Allowed locations assigned at a management group: https://learn.microsoft.com/en-us/azure/governance/management-groups/overview (read 10 Nov 2026)
- What it breaks: https://learn.microsoft.com/en-us/azure/governance/policy/concepts/scope (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-mg-assignment-allowed-locations/
