Design governance
Management group, subscription and resource group structure with a tagging strategy, compliance management, and identity governance.
- 15 min
- 3 concepts
- Try it yourself
- 4-question check
Learn
Governance designs set the rails everything else runs on. The Cloud Adoption Framework's Azure landing zone gives a proven starting structure.
- 1
Recommend a structure for management groups, subscriptions, and resource groups, and a strategy for resource tagging
Keep the management group hierarchy shallow (three or four levels) and organised by governance needs, not org chart: for example Platform (identity, management, connectivity), Landing zones (corp, online), Sandbox and Decommissioned. Use subscriptions as units of scale and isolation (per workload and environment). Group resources with the same lifecycle into resource groups. Define a tagging strategy (owner, cost centre, environment, data classification) and enforce it with Azure Policy (require or inherit tags).
Remember: Management groups by policy needs, not by department chart.
- 2
Recommend a solution for managing compliance
Assign Azure Policy initiatives (such as the Microsoft cloud security benchmark, ISO 27001 or NIST) at management group scope, with exemptions where justified. Use Defender for Cloud regulatory compliance to track posture, and Microsoft Purview for data governance and classification. Use resource locks on critical resources and deployment stacks to protect deployed resources.
Remember: Assign initiatives high, use exemptions sparingly.
- 3
Recommend a solution for identity governance
Recommend PIM for just-in-time admin rights, access reviews for guests and privileged roles, entitlement management for project access, and emergency access accounts. Separate privileged admin accounts from daily accounts, and use privileged access workstations for the most sensitive roles.
Remember: No standing admin access.
Azure landing zone management groups
- Tenant root groupRarely assigned to directly
- Organisation (e.g. Contoso)Company-wide policy and RBAC
- Platform | Landing zones | Sandbox | DecommissionedDifferent policy for each
- Identity, Management, Connectivity | Corp, OnlineSubscriptions live here
Try it
Pick a policy effect for a 'require CostCentre tag' policy and see what happens.
This interactive part needs JavaScript.
In the portal
- Management groupsAzure portal: Management groups
- Policy assignmentsAzure portal: Policy > Authoring > Assignments
- Regulatory complianceAzure portal: Microsoft Defender for Cloud > Regulatory compliance
Key terms
Click a card to see the definition.
Check your understanding
4 questions. Score 80% or more and these skills are marked as confident in your AZ-305 study plan.
How should management groups be organised?
Policy needs drive the structure.
How do you make sure every resource has a CostCentre tag?
Policy enforces tags.
What's the recommended depth for a management group hierarchy?
Keep it shallow and simple.
What unit is used for workload isolation and scale?
Subscriptions separate workloads and limits.
Sources
- Microsoft Learn: Azure landing zone design areas
- Microsoft Learn: Management group and subscription organisation
- Microsoft Learn: Define your tagging strategy
- Microsoft Learn: Azure Policy exemptions
Facts in this lesson are from Microsoft Learn. This site isn't affiliated with Microsoft.