# Management group assignment: what it can block and where it stops

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

Management group assignment is a Azure mechanism. Management groups organize subscriptions into a hierarchy so that policy and access assigned on a management group cascade to all its subscriptions by inheritance. It applies to all subscriptions and resources under the management group in the hierarchy.

Management groups organize subscriptions into a hierarchy so that policy and access assigned on a management group cascade to all its subscriptions by inheritance.

Management groups organize subscriptions into a hierarchy, so that policy and access assigned on a management group cascade to all its subscriptions by inheritance. A guardrail assigned there reaches every subscription and resource beneath it.

Limits: the tree supports up to six levels of depth, a single directory up to 10,000 management groups, and all subscriptions in one management group must trust the same Microsoft Entra tenant. No dry run was found for the management group itself on 2026-11-10, but a policy assigned there can use enforcementMode DoNotEnforce. 1 library entry covers allowed locations assigned at a management group.

## Documented limits

- A management group tree supports up to six levels of depth. ([source](https://learn.microsoft.com/en-us/azure/governance/management-groups/overview))
- A single directory supports up to 10,000 management groups. ([source](https://learn.microsoft.com/en-us/azure/governance/management-groups/overview))
- All subscriptions in one management group must trust the same Microsoft Entra tenant. ([source](https://learn.microsoft.com/en-us/azure/governance/management-groups/overview))

## Testing before enforcement

none found on 2026-11-10 for the management group itself; a policy assigned there can use enforcementMode DoNotEnforce. ([source](https://learn.microsoft.com/en-us/azure/governance/policy/concepts/assignment-structure))

## The 1 library entry written in it

- [Allowed locations assigned at a management group](/guardrails/azure-mg-assignment-allowed-locations/): Azure, Management group assignment, region and residency

**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

- [Organization Policy Service (managed and legacy constraints): how it works, its limits and how to test it](/mechanisms/org-policy/)
- [Custom organization policy constraints: how it works, its limits and how to test it](/mechanisms/custom-org-policy/)
- [IAM deny policies: how it works, its limits and how to test it](/mechanisms/iam-deny/)

## Sources

- Management group assignment: https://learn.microsoft.com/en-us/azure/governance/management-groups/overview (read 10 Nov 2026)
- Testing: 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/mechanisms/management-groups/
