Skip to content
Cloud Governance Tools

Allowed locations assigned at a management group

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.

More region and residency guardrails ยท About Management group assignment

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)
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)
Mechanism
Management group assignment: All subscriptions and resources under the management group in the hierarchy
Taken from
provider documentation, 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."

Sources

  1. Allowed locations assigned at a management group, read 10 Nov 2026
  2. What it breaks, read 10 Nov 2026
  3. How to test it first, read 10 Nov 2026

Last reviewed 16 Nov 2026.