Task 03: Create Resource Groups
DOCUMENT CATEGORY: Runbook
SCOPE: Full CAF/WAF resource group structure
PURPOSE: Create multi-subscription resource group organization
MASTER REFERENCE: Microsoft Learn — Resource Groups
Status: Active
Overview
Create resource groups within each subscription following the full CAF/WAF deployment model. Each subscription gets resource groups organized by function, providing granular access control, cost tracking, and lifecycle management.
What This Accomplishes
- Resource organization — logical grouping of related Azure resources per subscription
- Access control — resource group-level RBAC boundaries within each subscription
- Cost tracking — granular cost allocation using subscription + resource group + tags
- Lifecycle management — coordinated resource deployment and cleanup per function
Prerequisites
| Prerequisite | Detail |
|---|---|
| Subscriptions | All subscriptions created and associated with management groups (Task 02) |
| Permissions | Contributor or Owner role on each target subscription |
| Authenticated Azure session | See Authentication |
infrastructure.yml | Configured with resource group names per subscription |
Resource Group Plan
Platform Identity Subscription
Subscription: iic-platform-identity-001 (config: landing_zone.subscriptions[].name)
| Resource Group | Purpose | Config Path |
|---|---|---|
rg-identity-entraconnect-eus-01 | Entra ID Connect servers | landing_zone.resource_groups[].name |
rg-identity-pim-eus-01 | Privileged Identity Management | landing_zone.resource_groups[].name |
Platform Management Subscription
Subscription: iic-platform-management-001 (config: landing_zone.subscriptions[].name)
| Resource Group | Purpose | Config Path |
|---|---|---|
rg-mgmt-monitoring-eus-01 | Azure Monitor, Log Analytics | landing_zone.resource_groups[].name |
rg-mgmt-automation-eus-01 | Automation accounts, runbooks | landing_zone.resource_groups[].name |
rg-mgmt-backup-eus-01 | Recovery Services vaults | landing_zone.resource_groups[].name |
Platform Connectivity Subscription
Subscription: iic-platform-connectivity-001 (config: landing_zone.subscriptions[].name)
| Resource Group | Purpose | Config Path |
|---|---|---|
rg-connectivity-hub-eus-01 | Hub VNet, Azure Firewall | landing_zone.resource_groups[].name |
rg-connectivity-dns-eus-01 | Private DNS zones | landing_zone.resource_groups[].name |
rg-connectivity-bastion-eus-01 | Azure Bastion hosts | landing_zone.resource_groups[].name |
Landing Zone Subscriptions
Each landing zone subscription (e.g., iic-lz-azurelocal-corp-001) gets a single resource group per cluster — the same pattern as simplified deployment:
| Resource Group | Purpose | Config Path |
|---|---|---|
rg-c01-azl-eus-01 | Azure Local cluster + Arc resources | azure.resource_group |
For multiple clusters in the same subscription, increment the cluster identifier: rg-c01-azl-eus-01, rg-c02-azl-eus-01, etc.
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.
azure.tenant_id, azure.subscription_id, azure.resource_group, azure.location, tags
landing_zone.subscriptions[].name, .id the subscription of each entry
landing_zone.resource_groups[].name, .subscription, .location, .purpose
(purpose is shown in the progress lines and in the result; it is not written to Azure)
Execution Options
- Azure Portal
- Orchestrated Script
- Azure CLI
Azure Portal
When to use: Single deployment, prefer visual interface
Procedure
- Navigate to Resource Groups:
- In Azure Portal, search for Resource groups
- Click + Create
- Create Platform Identity RGs:
- Subscription: Select
iic-platform-identity-001 - Resource group: Enter name from the table above
- Region: Per config (
azure.locationorazure.location) - Click Review + create → Create
- Repeat for each RG in the Platform Identity table
- Create Platform Management RGs:
- Subscription: Select
iic-platform-management-001 - Create each RG from the Platform Management table
- Create Platform Connectivity RGs:
- Subscription: Select
iic-platform-connectivity-001 - Create each RG from the Platform Connectivity table
- Create Landing Zone RGs:
- Subscription: Select each landing zone subscription (e.g.,
iic-lz-azurelocal-corp-001) - Create the cluster RG:
rg-c01-azl-eus-01 - Repeat for each landing zone subscription
Validation
- All resource groups created in the correct subscriptions
- Resource group names match
infrastructure.yml - Resource groups are in the correct region
Links
PowerShell
When to use: Run the task from a management workstation or a pipeline. The script reads
infrastructure.ymland carries no values of its own.
Script
| Script | What it does |
|---|---|
scripts/deploy/02-azure-foundation/phase-01-landing-zones/full-deployment/task-03-create-resource-groups/powershell/Deploy-ResourceGroups.ps1 | Creates the Azure resource groups that landing_zone.resource_groups of infrastructure.yml lists. Supports -WhatIf. |
Requires: PowerShell 7.
Run
./Deploy-ResourceGroups.ps1 -InfrastructureFile ./infrastructure.yml -WhatIf
Azure CLI
When to use: Run the task from a host that has the Azure CLI and not the Az PowerShell modules. The script is PowerShell 7 that calls
az; it readsinfrastructure.ymland carries no values of its own.
Script
| Script | What it does |
|---|---|
scripts/deploy/02-azure-foundation/phase-01-landing-zones/full-deployment/task-03-create-resource-groups/azurecli/Deploy-ResourceGroups.azcli.ps1 | Creates the Azure resource groups that landing_zone.resource_groups of infrastructure.yml lists, with the Azure CLI. Supports -WhatIf. |
Requires: PowerShell 7 and the Azure CLI, signed in with az login --tenant <azure.tenant_id>.
Azure side only. A resource group that exists is left alone: its location and tags are never changed, and nothing is deleted or moved. You need Contributor or Owner on each subscription.
Run
./Deploy-ResourceGroups.azcli.ps1 -InfrastructureFile ./infrastructure.yml -WhatIf
./Deploy-ResourceGroups.azcli.ps1 -InfrastructureFile ./infrastructure.yml
Troubleshooting
| Symptom | Error | Resolution |
|---|---|---|
| Permission denied | AuthorizationFailed | Verify Contributor or Owner role on the target subscription |
| Duplicate name | ResourceGroupAlreadyExists | RG already exists — verify it's in the correct subscription and region, then move on |
| Invalid location | LocationNotAllowed | Check Azure Policy allowed-locations constraints on the subscription or management group |
| Wrong subscription context | RG created in wrong sub | Always run Set-AzContext -Subscription before New-AzResourceGroup |
Next Steps
After resource groups are deployed:
- Proceed to the next phase of the Azure Foundation deployment
- Apply tagging policies at the management group or subscription level
- Configure RBAC assignments on each resource group as needed
References
- Azure Local Toolkit — Governance Module
- Microsoft Learn — Manage Resource Groups
- Microsoft Learn — Resource Naming Conventions
- Microsoft Learn — Resource Tagging
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 |
|---|---|---|
| Task 02 — Create Subscriptions | Full Deployment Overview | Phase 02 — Resource Providers |
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 |