Microsoft AZ-104: Azure Management Groups
Management groups let a large Azure estate apply governance above individual subscriptions. The hard design problem is not creating folders in a hierarchy; it is placing subscriptions so inherited access and policy match how the organization actually operates. A hierarchy that mirrors an organization chart too closely can make policy and role inheritance harder to manage after a reorganization. Group subscriptions where governance requirements genuinely differ, and test effective policy at the destination scope.
On this page
- Organize subscriptions by governance differences, not team names alone
- Understand the tenant root and the full scope chain
- Make the hierarchy readable and governable
- Apply policies where they should remain uniform
- Delegate roles without making management groups permanent superuser zones
- Treat subscription moves as security changes
- Operate the hierarchy as a long-lived platform interface
Organize subscriptions by governance differences, not team names alone
An organization may have subscriptions for shared networking, identity infrastructure, regulated workloads, ordinary applications and experimentation. If every team receives a management group automatically, the hierarchy can become a fragile reflection of the org chart. Reorganizations then move subscriptions around and unexpectedly change inherited permissions or Azure Policy assignments. Management-group design in Microsoft AZ-104 must verify inherited policy and access effects before the hierarchy expands.
Begin with governance requirements that persist through personnel changes: data residency, connectivity patterns, baseline security restrictions, production change controls, approved service families and required logging. Group subscriptions with similar requirements. Different teams can own separate subscriptions inside a common policy boundary while using subscription-scoped permissions for their daily tasks.
Azure management groups organize subscriptions under governance scopes, allowing appropriate policies and access assignments to be inherited by descendants. A new subscription placed within a management group can therefore inherit controls that its application team did not configure directly. The design question is what each group means operationally, not how many nesting levels the tree can contain.
Understand the tenant root and the full scope chain
A management group hierarchy belongs to a Microsoft Entra tenant. All management groups and subscriptions in that tenant fold into a single root management group. The root cannot be deleted or moved like ordinary child groups. Permissions and policies assigned at root can affect the entire tenant’s Azure resource hierarchy, so root-level actions deserve exceptional care.
The resulting chain is management group, child management group where used, subscription, resource group and resource. Policy and Azure RBAC inheritance can flow from parent to child according to each service’s rules. A role assigned at a management group can grant access across many subscriptions, while a subscription-scoped role has a narrower reach. Moving a subscription can change the inherited combination without changing any permissions configured directly on its resources.
Do not give broad standing access at root simply to avoid managing ownership. Use the smallest durable scope and document why a policy or role must be shared so widely. Limit root assignments to genuinely universal requirements and tightly governed platform administrators. Some Azure RBAC and management-group permissions also have particular requirements when moving hierarchy members; consult the supported operation before treating moving a subscription as a trivial folder edit.
Make the hierarchy readable and governable
A useful hierarchy separates platform subscriptions from application landing zones and explicitly distinguishes special environments, such as sandboxes or regulated workloads, when their policies differ. For example, a platform branch may contain connectivity and identity subscriptions; a landing-zone branch may contain corporate-connected and internet-facing workload groups. The exact names matter less than the predictable policy and ownership boundaries.
Avoid excessive depth. Deep trees complicate inherited rights investigation and increase the risk of a parent assignment unexpectedly affecting a distant child. Use meaningful documentation for each level: business rationale, policy intent, delegated owners, allowed subscription categories and change process. A hierarchy diagram should help an operator predict the resulting controls on a new subscription without inspecting dozens of hidden assignments.
Decide what happens to a new subscription before automated placement is complete. New subscriptions initially appear at root under documented behavior, which can create an unintended governance gap until they are moved to the correct target. An approved subscription-vending workflow should include placement, security baseline assignment and verification before application teams receive broad deployment access.
Apply policies where they should remain uniform
Azure Policy initiatives and assignments help implement organizational rules, such as required tags, permitted locations, diagnostics or denied resource configurations. A management group can supply a baseline to many subscriptions at once. That reduces drift but amplifies the effect of an incorrect definition or enforcement mode. Test a deny rule against representative legitimate deployments before applying it to every production subscription.
An initiative is a grouping of policy definitions; it does not imply every definition has the same effect or remediation behavior. Some policies audit and report, some deny changes, and others can deploy or modify settings when properly configured with identity permissions. Record exceptions deliberately, including their scope, reason, expiration and reviewer, rather than weakening a baseline for everyone when one workload has a justified difference.
Use Azure Policy governance at the hierarchy level that matches intent. A policy designed for all public-facing production apps may belong on a relevant branch rather than the entire tenant root. Review inheritance and effective compliance per subscription, not only whether the parent assignment exists.
Delegate roles without making management groups permanent superuser zones
Platform teams may need rights to create management groups, enroll subscriptions and assign policies, but that does not mean every platform engineer needs Owner access across all workloads. Separate the administrator who maintains the hierarchy from the service owner who manages an application. Inherited Azure RBAC should correspond to the service responsibility and include a clear path for emergency escalation.
Consider a central security team assigned Reader or monitoring roles at a broad scope. That can be appropriate for visibility, whereas granting universal write permissions merely for incident investigation can widen blast radius. Review role assignment inheritance and assign narrowly scoped privileges when an investigation requires changes. Privileged Identity Management may be useful where supported, but it is not a substitute for understanding the role’s effective scope.
A concrete check is to take a representative user, find their direct and inherited role assignments, and explain exactly which management groups and subscriptions those grants affect. Repeat after a hierarchy move, a new subscription and a role assignment change. If the team cannot account for a user’s effective privileges, the tree has outgrown its governance controls.
Treat subscription moves as security changes
Moving a subscription between management groups can replace one inherited policy set with another and alter who can operate it. That is a material production change even though the subscription’s resources remain in place. Before a move, compare current and target assignments, required exceptions, role inheritance and compliance impact, and identify which teams might lose access or gain unwanted privileges.
Choose an approved change window when policy effects may block deployment workflows. Record the management group IDs, target subscription, authority to perform the move and rollback plan. Some moves require permissions on both parent groups and the subscription; do not assume a Contributor role in a workload resource group can move the entire subscription.
After the move, evaluate effective policy compliance and role assignments, then test the application’s expected deployment pipeline and monitoring visibility. An apparently successful API action does not prove all new governance controls are appropriate. Keep an audit entry describing why the subscription changed branches and which approvals allowed the new security boundary.
Operate the hierarchy as a long-lived platform interface
Management group structures change as an enterprise grows, merges or adopts more specialized workloads. A stable convention, versioned definitions and documented ownership enable new subscriptions to inherit predictable policies. Periodically check unclassified subscriptions at root, unused groups, stale exceptions and broad inherited roles that no longer correspond to active service ownership.
Use automation carefully: encode intended group paths, assignments and monitoring, but avoid deleting or moving live subscriptions automatically merely because an external organizational directory changed. Governance decisions deserve explicit review when they affect dozens of production environments. A periodic drift report can identify mismatches without turning every observation into an immediate destructive remediation.
A management-group hierarchy should make policy and access inheritance predictable when subscriptions are created, reorganized, or transferred between owners. Test an onboarding example from the root of the hierarchy to the resource, including an approved exception. A clean tree on its own is not success; success is operators knowing what is inherited and how to make a change without broad accidental effects.