Task 01: Configure Management Group
DOCUMENT CATEGORY: Runbook
SCOPE: Simplified deployment — landing zone management group
PURPOSE: Create the landing zone management group under the existing root
MASTER REFERENCE: Microsoft Learn — Management Groups
Status: Active
Overview
Create the landing zone management group under the existing root management group. The subscription created in Task 02 will be placed under this landing zone MG.
What This Accomplishes
- Landing zone governance boundary — scoped policies and RBAC inheritance for Azure Local resources
- Subscription organization — the landing zone MG is the parent for the Azure Local subscription
Every Entra ID tenant has a built-in Tenant Root Group. Your organization root management group (e.g., cmp-iic-root) is created beneath it as a custom MG that serves as the top of your governance hierarchy. If the organization root MG does not exist yet, create it first — see the Full CAF/WAF Task 01 for the procedure. This task creates the landing zone management group beneath it.
Management Group Naming
Management groups have two identifiers:
| Property | Description | Can Change? |
|---|---|---|
ID (GroupName) | Used in ARM/Bicep, CLI, and policy assignments | No — immutable once created |
| Display Name | Shown in Azure Portal | Yes — editable anytime |
Example (IIC)
| Attribute | Value | Source |
|---|---|---|
| Parent MG ID | cmp-iic-root | infrastructure.yml → landing_zone.management_groups[].parent |
| Landing Zone MG ID | cmp-landing-zones-iic | infrastructure.yml → landing_zone.management_groups[].name |
| Display Name | IIC Landing Zone Management Group | infrastructure.yml → landing_zone.management_groups[].display_name |
Target Structure
Tenant Root Group
└── cmp-iic-root # already exists
└── cmp-landing-zones-iic # ← created in this task
Prerequisites
- Organization root management group exists in the tenant (or you will create it — see note above)
- Permissions: Management Group Contributor (or Owner) on the root management group. You may need to elevate access first.
- Authenticated Azure session — see Authentication
infrastructure.ymlconfigured with management group values
Values from infrastructure.yml
The values for this task come from infrastructure.yml (schema 5). Every key, with its type, default and example, is in the variables reference.
Execution Options
- Azure Portal
- Orchestrated Script
- Azure CLI
Azure Portal
When to use: Single deployment, prefer visual interface
Procedure
- Navigate to Management Groups:
- In Azure Portal, search for Management groups
- Locate the root management group (
landing_zone.management_groups[].parent)
- Create the Landing Zone Management Group:
- Click + Add management group
| Field | Value | Source |
|---|---|---|
| Management group ID | <landing-zone-mg-id> | infrastructure.yml → landing_zone.management_groups[].name |
| Management group display name | <display-name> | infrastructure.yml → landing_zone.management_groups[].display_name |
| Parent | Root MG from config | infrastructure.yml → landing_zone.management_groups[].parent |
- Save and wait for creation to complete.
Validation
- Landing zone MG appears under the root MG in the portal
- MG ID matches the value in
infrastructure.yml - Display name is correct
Links
PowerShell
No script of its own. The toolkit has no script folder for the single subscription route. Use the script of the full deployment:
scripts/deploy/02-azure-foundation/phase-01-landing-zones/full-deployment/task-01-configure-management-groups/powershell/Deploy-ManagementGroups.ps1readslanding_zone.management_groups[], and a file with one entry gives the same result. Or follow the steps in the other tab of this page.
Azure CLI
No script of its own. The toolkit has no script folder for the single subscription route. Use the Azure CLI script of the full deployment:
scripts/deploy/02-azure-foundation/phase-01-landing-zones/full-deployment/task-01-configure-management-groups/azurecli/Deploy-ManagementGroups.azcli.ps1readslanding_zone.management_groups[], and a file with one entry gives the same result. Or follow the steps in the other tab of this page.
./Deploy-ManagementGroups.azcli.ps1 -InfrastructureFile ./infrastructure.yml -WhatIf
./Deploy-ManagementGroups.azcli.ps1 -InfrastructureFile ./infrastructure.yml
Requires: PowerShell 7 and the Azure CLI, signed in with az login --tenant <azure.tenant_id>.
Troubleshooting
| Issue | Symptom | Resolution |
|---|---|---|
| Permission denied | AuthorizationFailed | Verify Management Group Contributor or Owner role on the root MG |
| Duplicate ID | ManagementGroupAlreadyExists | The MG already exists — verify it's under the correct parent and move on |
| Parent not found | ParentManagementGroupNotFound | Confirm the root MG ID in infrastructure.yml matches what exists in the tenant |
Next Steps
Proceed to Task 02: Create Subscription
References
- Management Groups Overview
- Create Management Groups
- Elevate Access to Manage All Subscriptions
- Azure Landing Zones — Start Small and Expand
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.
Navigation
| Previous | Up | Next |
|---|---|---|
| Simplified Deployment Overview | Simplified Deployment Overview | Task 02 — Create Subscription |
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
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0.0 | 2025-03-25 | Azure Local Cloud | Initial release |