Skip to main content

Task 01: Configure Management Groups

Runbook Azure

DOCUMENT CATEGORY: Runbook
SCOPE: Full CAF/WAF management group hierarchy
PURPOSE: Deploy complete CAF-aligned management group structure
MASTER REFERENCE: Azure Landing Zones — Enterprise-Scale Architecture

Status: Active

Overview​

Create the complete management group hierarchy following the Azure Landing Zone conceptual architecture. This establishes the enterprise-grade governance structure for multi-subscription Azure Local environments, with hierarchical policy inheritance and RBAC boundaries.

The management group hierarchy is the backbone of Azure governance — every policy, role assignment, and budget you define at the MG level cascades to all subscriptions and resources beneath it. Getting this right from the start means your Azure Local clusters inherit consistent security, compliance, and operational controls automatically.

What This Accomplishes​

  • Governance structure — complete CAF Enterprise-Scale management group hierarchy
  • Policy inheritance — hierarchical policy and RBAC inheritance from your organization root down through platform and landing zone scopes
  • Landing zone organization — structured landing zones for corporate (Azure Local) and online workloads
  • Lifecycle management — sandbox and decommissioned MGs for experimentation and teardown
Tenant Root Group vs. Organization Root

Every Azure tenant has a built-in Tenant Root Group that cannot be renamed or deleted. In this task, you create your organization root management group (e.g., cmp-iic-root) directly beneath it, then build the full hierarchy under that. This keeps your organization's structure cleanly separated from the tenant default.

Management Group Naming​

Management groups have two identifiers:

PropertyDescriptionCan Change?
ID (GroupName)Used in ARM/Bicep, CLI, and policy assignmentsNo — immutable once created
Display NameShown in Azure PortalYes — editable anytime

Target Hierarchy (IIC Example)​

Tenant Root Group
└── cmp-iic-root # already exists
├── cmp-platform-iic # Platform Services
│ ├── cmp-platform-identity-iic # Identity
│ ├── cmp-platform-management-iic # Management
│ └── cmp-platform-connectivity-iic # Connectivity
├── cmp-landing-zones-iic # Landing Zones
│ ├── cmp-lz-corp-iic # Corp Landing Zone
│ └── cmp-lz-online-iic # Online Landing Zone
├── cmp-sandbox-iic # Sandbox
└── cmp-decommissioned-iic # Decommissioned

Complete Hierarchy Table​

LevelDisplay NameMG ID (IIC)Config Path
1IIC Rootcmp-iic-rootlanding_zone.management_groups[].parent
2Platformcmp-platform-iiclanding_zone.management_groups[].name
3Platform — Identitycmp-platform-identity-iiclanding_zone.management_groups[].name
3Platform — Managementcmp-platform-management-iiclanding_zone.management_groups[].name
3Platform — Connectivitycmp-platform-connectivity-iiclanding_zone.management_groups[].name
2Landing Zonescmp-landing-zones-iiclanding_zone.management_groups[].name
3Corp Landing Zonecmp-lz-corp-iiclanding_zone.management_groups[].name
3Online Landing Zonecmp-lz-online-iiclanding_zone.management_groups[].name
2Sandboxcmp-sandbox-iiclanding_zone.management_groups[].name
2Decommissionedcmp-decommissioned-iiclanding_zone.management_groups[].name

Prerequisites​

  • Tenant access — you must have Owner or User Access Administrator role at the tenant root management group scope (see Elevate access to manage all Azure subscriptions)
  • Permissions — Management Group Contributor (or Owner) at the scope where you'll create the hierarchy
  • Authenticated Azure session — see Authentication
  • infrastructure.yml — configured with the full management group hierarchy names and display names

Values from infrastructure.yml​

The script reads these keys from infrastructure.yml (schema 5). Each key, with its type, default and example, is in the variables reference.

Deploy-ManagementGroups.ps1:

azure.tenant_id                                 the tenant the sign-in must belong to
landing_zone.management_groups[].name the management group id
landing_zone.management_groups[].display_name the display name (default: the name)
landing_zone.management_groups[].parent the name of the parent entry; empty for the tenant root

Set-ManagementGroupDisplayNames.ps1:

azure.tenant_id                                 the tenant the sign-in must belong to
landing_zone.management_groups[].name the management group id (the group must already exist)
landing_zone.management_groups[].display_name the display name it must have

An entry of landing_zone.management_groups that is not a map stops Set-ManagementGroupDisplayNames.ps1 (and its Azure CLI twin) with exit 2.


Execution Options​

Azure Portal​

When to use: Single deployment, prefer visual interface

Procedure​

  1. Navigate to Management Groups:
  • In Azure Portal, search for Management groups
  • Locate the root management group (landing_zone.management_groups[].parent)
  1. Create Platform Management Groups:
  • Select root MG → + Add management group
  • Create the platform container:
FieldValueConfig Path
MG IDcmp-platform-iiclanding_zone.management_groups[].name
Display NamePlatformlanding_zone.management_groups[].display_name
  • Select the platform MG → + Add management group for each child:
MG IDDisplay NameConfig Path
cmp-platform-identity-iicPlatform — Identitylanding_zone.management_groups[]
cmp-platform-management-iicPlatform — Managementlanding_zone.management_groups[]
cmp-platform-connectivity-iicPlatform — Connectivitylanding_zone.management_groups[]
  1. Create Landing Zone Management Groups:
  • Select root MG → + Add management group
  • Create the landing zones container:
FieldValueConfig Path
MG IDcmp-landing-zones-iiclanding_zone.management_groups[].name
Display NameLanding Zoneslanding_zone.management_groups[].display_name
  • Select the landing zones MG → + Add management group for each child:
MG IDDisplay NameConfig Path
cmp-lz-corp-iicCorp Landing Zonelanding_zone.management_groups[]
cmp-lz-online-iicOnline Landing Zonelanding_zone.management_groups[]
  1. Create Auxiliary Management Groups:
  • Select root MG → + Add management group for each:
MG IDDisplay NameConfig Path
cmp-sandbox-iicSandboxlanding_zone.management_groups[]
cmp-decommissioned-iicDecommissionedlanding_zone.management_groups[]

Validation​

  • Platform hierarchy complete (platform + identity, management, connectivity)
  • Landing zones hierarchy complete (landing-zones + corp, online)
  • Sandbox and Decommissioned MGs created under root
  • All IDs and display names match infrastructure.yml

Troubleshooting​

IssueSymptomResolution
Permission deniedAuthorizationFailedVerify Management Group Contributor or Owner role on the root MG
Duplicate IDManagementGroupAlreadyExistsThe MG already exists — verify it's under the correct parent and move on
Parent not foundParentManagementGroupNotFoundCreate parent MGs first (platform before platform children, etc.)
Hierarchy depth exceededHierarchyDepthExceededAzure limits MG depth to 6 levels — this hierarchy uses 3, well within limits

Next Steps​

Proceed to Task 02: Create Subscriptions

References​



Alternatives​

The procedures in this task use the methods shown in the tabs above. The toolkit is PowerShell 7 only and has no Bash scripts. A few tasks that act on Azure also have an Azure CLI script written in PowerShell. The script status page of the toolkit lists which task has which script.

PreviousUpNext
Full Deployment OverviewFull Deployment OverviewTask 02 — Create Subscriptions

Version Control

  • Created: 2026-01-15 by Hybrid Cloud Solutions
  • Last Updated: 2026-03-19 by Hybrid Cloud Solutions
  • Version: 3.0.0

Version Control​

VersionDateAuthorChanges
1.0.02025-03-25Azure Local CloudInitial release