![\"\"](\"https:\/\/proglab.com.br\/wp-content\/uploads\/2026\/04\/image-48.png\")
<\/figure>\n\n\n\nAnd this image here outlines the four key layers. So understand the structure for those layers. <\/p>\n\n\n\n
Management groups -> Subscription -> Resource groups -> Resources <\/strong><\/p>\n\n\n\n Remember that hierarchy as part of your exam. Know that within each subscription resource groups organize related services such as resources like virtual machines and databases and storage accounts which makes it easier to manage. <\/p>\n\n\n\n At the bottom level you have your resources which are all the key components that you deploy. Virtual machines. Databases. Storage accounts and so forth. Understanding how these layers interact and how to apply policies, manage access, and use tags effectively is essential for designing an environment and preparing for your exam.<\/p>\n\n\n\n Design for governance<\/a><\/strong><\/p>\n\n\n\n Design for management groups<\/a><\/strong><\/p>\n\n\n\n Management groups manage access, policy, and compliance for multiple subscriptions.<\/p>\n\n\n\n Observations:<\/p>\n\n\n\n \u00b7 Keep the management group hierarchy reasonably flat Design for subscriptions<\/strong><\/a><\/p>\n\n\n\n Designing for multiple subscriptions<\/p>\n\n\n\n Azure subscription are logical containers for management and billing.<\/p>\n\n\n\n Align your subscriptions with business needs and priorities – consider billing and cost reporting<\/p>\n\n\n\n Consider subscription scale limits – specialized workloads, loT, SAP Secure workloads that require additional policies and role-based access control to achieve compliance Organizing Subscriptions Design for resource groups<\/a><\/strong><\/p>\n\n\n\n Resource groups organize related services such as resources like virtual machines and databases and storage accounts which makes it easier to manage.<\/p>\n\n\n\n Design for resource tags<\/a><\/strong><\/p>\n\n\n\n Understand tagging and understand a strong tagging strategy. This is going to be important also. And keep in mind that they’re especially useful in large environments where visibility and control are crucial. <\/p>\n\n\n\n https:\/\/learn.microsoft.com\/en-us\/azure\/azure-resource-manager\/management\/move-limitations\/app-service-move-limitations<\/a><\/p>\n\n\n\n![\"\"](\"https:\/\/proglab.com.br\/wp-content\/uploads\/2026\/04\/image-26.png\")
<\/figure>\n\n\n\n
\u00b7 Consider a top-level management group
\u00b7 Consider an organizational or departmental structure
\u00b7 Consider a geographical structure
\u00b7 Consider a production management group
\u00b7 Consider a sandbox management group
\u00b7 Consider isolating sensitive information in a separate management group<\/p>\n\n\n\n![\"\"](\"https:\/\/proglab.com.br\/wp-content\/uploads\/2026\/04\/image-27.png\")
<\/figure>\n\n\n\n
Consider administrative management – centralized or decentralized
Consider a dedicated shared services subscription – common services everyone shares
Group subscriptions together under management groups – apply common policies and role assignments.
Make subscription owners aware of their roles and responsibilities
Consideration for when to use subscriptions:<\/p>\n\n\n\n
Specialized workloads and the need to scale outside the subscription limits
Manage and track costs for your organizational structure
Identify different environments such as development, test, and production that are often isolated from a management perspective
Use Cases:<\/p>\n\n\n\n
Centralized Governance and Policy Management
Simplified Access Control
Cost Management and Budgeting
Scenario:
An organization with multiple departments can create a management group for each department and then assign subscriptions for each department’s resources to their respective management group.<\/p>\n\n\n\n