An Azure landing zone assigns policy to management groups, with sandboxes held to a less restrictive set
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
Microsoft Cloud Adoption Framework guidance for Azure landing zones places Azure Policy assignments on management groups: platform, landing zones, sandboxes and decommissioned. It advises few assignments at the root, a flat hierarchy of three to four levels, and no workload RBAC at management group scope, as read on 16 Nov 2026.
Microsoft assigns policy at management groups, grouped by workload type
Microsoft says to use management groups to aggregate policy and initiative assignments, and to organize subscriptions by workload type such as online, corp, local or sandbox. The reference architecture below is Microsoft's description, read 16 Nov 2026.
| Management group | Purpose in Microsoft's description | Policy posture stated |
|---|---|---|
| Platform (Security, Management, Connectivity, Identity) | Shared platform subscriptions | Specific policies to harden and manage the identity subscription |
| Landing zones | Parent of all landing zone groups | Workload-agnostic policies so workloads are secure and compliant |
| Online and Corp | Internet-facing and corporate-network workloads | Inherit the landing zone assignments |
| Local | Workloads on Azure Local clusters | Different Azure Policy requirements from the other groups |
| Sandboxes | Testing and exploration, isolated from corp and online | Less restrictive set of policies |
| Decommissioned | Canceled landing zones | Azure deletes them after 30 to 60 days |
The advice is to assign policy at the group and keep the tree shallow
Microsoft also notes that by default any principal in a Microsoft Entra tenant can create management groups, and advises enabling Azure RBAC authorization on the hierarchy to restrict it.
- Keep the hierarchy reasonably flat, ideally no more than three to four levels; a tree supports up to six levels of depth, excluding root and subscription.
- Limit the number of Azure Policy assignments at the root management group scope, to cut debugging of inherited policies lower down.
- Do not assign workload teams permissions through RBAC at management group scope; use management groups for policy assignment instead.
- Set a dedicated default management group for new subscriptions, because new subscriptions otherwise land under the tenant root group.
- Do not create management groups for production, test and development; separate those into subscriptions in the same group.
Subscriptions are placed by workload type, and sandboxes are the exception to strict policy
Microsoft says to create a sandbox management group so teams can experiment with resources before moving them to production, isolated from development, test and production. It says sandboxes have a less restrictive policy set so that testing and exploration are possible. That is a deliberate gap in the baseline, and it makes the default management group for new subscriptions a security decision: whichever group is the default receives every new subscription until someone moves it.
For location-based regulatory needs such as data residency, Microsoft advises building a management group structure based on location instead of one group per region, and it advises against creating groups only to model Azure regions.
A default policy set exists, and Microsoft says to use it as a starting point
Microsoft's governance design area says to determine which policies you need from your business controls or compliance regulations, and to use the policies in the Azure landing zone reference architecture as a starting point. It names the Azure landing zone default policy assignments Bicep module as a way to get a head start, and says change advisory review boards can hinder agility where Azure Policy automated guardrails can replace them.
What the module assigns, and how many policies: none found in the pages read on 16 Nov 2026. Read the module itself before relying on it.
Library entries show what a management group assignment does and where it leaks
The library entry Allowed locations assigned at a management group records the main trap: scopes listed in notScopes on an assignment are skipped entirely, and are not evaluated or counted in compliance. The same assignment can be tested first with enforcementMode set to DoNotEnforce, which Microsoft documents for evaluating an assignment before enforcement.
Other entries suited to an inherited baseline include Configure storage accounts to disallow public blob access and Resource locks. The management group mechanism page and the Azure Policy mechanism page explain the objects.
Related pages
Sources
- Microsoft: management groups in Azure landing zones, read 16 Nov 2026
- Microsoft: Azure governance design area, read 16 Nov 2026
- Microsoft: Azure Policy assignment structure, read 16 Nov 2026
Last reviewed 16 Nov 2026.