Skip to main content

Task 03: Create Resource Groups

Runbook Azure

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​

PrerequisiteDetail
SubscriptionsAll subscriptions created and associated with management groups (Task 02)
PermissionsContributor or Owner role on each target subscription
Authenticated Azure sessionSee Authentication
infrastructure.ymlConfigured with resource group names per subscription

Resource Group Plan​

Platform Identity Subscription​

Subscription: iic-platform-identity-001 (config: landing_zone.subscriptions[].name)

Resource GroupPurposeConfig Path
rg-identity-entraconnect-eus-01Entra ID Connect serverslanding_zone.resource_groups[].name
rg-identity-pim-eus-01Privileged Identity Managementlanding_zone.resource_groups[].name

Platform Management Subscription​

Subscription: iic-platform-management-001 (config: landing_zone.subscriptions[].name)

Resource GroupPurposeConfig Path
rg-mgmt-monitoring-eus-01Azure Monitor, Log Analyticslanding_zone.resource_groups[].name
rg-mgmt-automation-eus-01Automation accounts, runbookslanding_zone.resource_groups[].name
rg-mgmt-backup-eus-01Recovery Services vaultslanding_zone.resource_groups[].name

Platform Connectivity Subscription​

Subscription: iic-platform-connectivity-001 (config: landing_zone.subscriptions[].name)

Resource GroupPurposeConfig Path
rg-connectivity-hub-eus-01Hub VNet, Azure Firewalllanding_zone.resource_groups[].name
rg-connectivity-dns-eus-01Private DNS zoneslanding_zone.resource_groups[].name
rg-connectivity-bastion-eus-01Azure Bastion hostslanding_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 GroupPurposeConfig Path
rg-c01-azl-eus-01Azure Local cluster + Arc resourcesazure.resource_group
Scaling Landing Zones

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​

When to use: Single deployment, prefer visual interface

Procedure​

  1. Navigate to Resource Groups:
  • In Azure Portal, search for Resource groups
  • Click + Create
  1. Create Platform Identity RGs:
  • Subscription: Select iic-platform-identity-001
  • Resource group: Enter name from the table above
  • Region: Per config (azure.location or azure.location)
  • Click Review + create → Create
  • Repeat for each RG in the Platform Identity table
  1. Create Platform Management RGs:
  • Subscription: Select iic-platform-management-001
  • Create each RG from the Platform Management table
  1. Create Platform Connectivity RGs:
  • Subscription: Select iic-platform-connectivity-001
  • Create each RG from the Platform Connectivity table
  1. 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

Troubleshooting​

SymptomErrorResolution
Permission deniedAuthorizationFailedVerify Contributor or Owner role on the target subscription
Duplicate nameResourceGroupAlreadyExistsRG already exists — verify it's in the correct subscription and region, then move on
Invalid locationLocationNotAllowedCheck Azure Policy allowed-locations constraints on the subscription or management group
Wrong subscription contextRG created in wrong subAlways 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​



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
Task 02 — Create SubscriptionsFull Deployment OverviewPhase 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​

VersionDateAuthorChanges
1.0.02025-03-25Azure Local CloudInitial release