Task 02: Create Subscriptions
DOCUMENT CATEGORY: Runbook
SCOPE: Full CAF/WAF subscription provisioning
PURPOSE: Create and associate dedicated subscriptions with management groups
MASTER REFERENCE: Create Azure subscriptions programmatically
Status: Active
Overview
Provision dedicated Azure subscriptions and associate each with its corresponding management group. The full CAF/WAF deployment uses separate subscriptions for platform services and landing zones, providing maximum billing isolation, RBAC boundaries, and governance flexibility.
How You Create Subscriptions
How you create subscriptions depends on your organization's billing arrangement:
| Billing Type | Creation Method | Programmatic Support |
|---|---|---|
| Enterprise Agreement (EA) | EA Portal, Azure CLI, or REST API | ✅ Full — az account create with enrollment account |
| Microsoft Customer Agreement (MCA) | Azure Portal, Azure CLI, or REST API | ✅ Full — az account create with billing profile + invoice section |
| Pay-As-You-Go / MOSP | Azure Portal only | ❌ Manual only — use the portal |
If you have an EA or MCA, you can create subscriptions programmatically using az account create or New-AzSubscriptionAlias. This is the recommended approach for the full deployment model where you need 5+ subscriptions. See the Execution Options below.
What This Accomplishes
- Billing isolation — separate cost tracking per platform function and landing zone
- Access control — subscription-level RBAC boundaries
- Resource organization — dedicated containers aligned with management group hierarchy
- Governance scope — policy and compliance boundaries per subscription
Prerequisites
| Prerequisite | Detail |
|---|---|
| Management Groups | Full hierarchy deployed (Task 01) |
| Billing Access | EA enrollment account owner, MCA billing profile owner, or Azure Portal access to create subscriptions |
| Subscription Quota | Available subscription quota in your tenant (default: 5000 per EA, varies by agreement) |
| Permissions | Management Group Contributor on target MGs (to associate subscriptions after creation) |
Subscription Architecture
Each leaf-level management group hosts a dedicated subscription:
Subscription Mapping (IIC Example)
| Management Group | Subscription Name | Config Path | Purpose |
|---|---|---|---|
cmp-platform-identity-iic | iic-platform-identity-001 | landing_zone.subscriptions[].name | Entra ID Connect, identity services |
cmp-platform-management-iic | iic-platform-management-001 | landing_zone.subscriptions[].name | Azure Monitor, Log Analytics, Automation |
cmp-platform-connectivity-iic | iic-platform-connectivity-001 | landing_zone.subscriptions[].name | Hub VNet, VPN, ExpressRoute |
cmp-lz-corp-iic | iic-lz-azurelocal-corp-001 | landing_zone.subscriptions[].name | Azure Local clusters (corporate) |
cmp-lz-online-iic | iic-lz-azurelocal-online-001 | landing_zone.subscriptions[].name | Internet-facing workloads |
Target Structure
cmp-iic-root ← organization root MG
├── cmp-platform-iic
│ ├── cmp-platform-identity-iic
│ │ └── iic-platform-identity-001 ← subscription
│ ├── cmp-platform-management-iic
│ │ └── iic-platform-management-001 ← subscription
│ └── cmp-platform-connectivity-iic
│ └── iic-platform-connectivity-001 ← subscription
├── cmp-landing-zones-iic
│ ├── cmp-lz-corp-iic
│ │ └── iic-lz-azurelocal-corp-001 ← subscription
│ └── cmp-lz-online-iic
│ └── iic-lz-azurelocal-online-001 ← subscription
├── cmp-sandbox-iic (no subscription yet)
└── cmp-decommissioned-iic (no subscription yet)
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-Subscriptions.ps1:
azure.tenant_id the tenant the sign-in must belong to
tags tags for the subscriptions created (optional)
landing_zone.subscriptions[].name the alias and the display name of the subscription
landing_zone.subscriptions[].id when set (and not all zeros) the entry is an existing subscription and is skipped
landing_zone.subscriptions[].billing_scope the billing scope the subscription is created under
landing_zone.subscriptions[].workload Production (default) or DevTest
landing_zone.subscriptions[].management_group the management group the subscription is created under (optional)
Invoke-SubscriptionMove-Orchestrated.ps1:
azure.tenant_id the tenant the sign-in must belong to
landing_zone.subscriptions[].name the label used in messages
landing_zone.subscriptions[].id the subscription to move
landing_zone.subscriptions[].management_group the management group it belongs under
Execution Options
- Azure Portal
- Orchestrated Script
- Azure CLI
Azure Portal
When to use: Pay-As-You-Go billing, or you prefer the visual interface
Procedure
-
Navigate to Subscriptions:
- In Azure Portal, search for Subscriptions
- Click + Add
-
Create each subscription from the mapping table above:
- Subscription name: Enter the name from the mapping table (e.g.,
iic-platform-identity-001) - Billing: Select your billing account / enrollment
- Management group: Select the corresponding management group from the mapping table
- Click Create
- Subscription name: Enter the name from the mapping table (e.g.,
-
Verify each subscription appears under the correct management group in Management groups view
Work through the mapping table top-to-bottom, creating all Platform subscriptions first, then Landing Zone subscriptions. The Azure Portal allows you to set the management group at creation time, saving the manual association step.
Validation
- All 5 subscriptions created with names matching
infrastructure.yml - Each subscription is under the correct management group
- You have Owner access to all subscriptions
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-02-create-subscriptions/powershell/Deploy-Subscriptions.ps1 | Creates the Azure subscriptions that landing_zone.subscriptions of infrastructure.yml lists without an id, under the management group the entry names. Supports -WhatIf. |
scripts/deploy/02-azure-foundation/phase-01-landing-zones/full-deployment/task-02-create-subscriptions/powershell/Invoke-SubscriptionMove-Orchestrated.ps1 | Moves existing subscriptions under the management groups infrastructure.yml names for them. Supports -WhatIf. |
Requires: PowerShell 7.
Run
./Deploy-Subscriptions.ps1 -InfrastructureFile ./infrastructure.yml -WhatIf
./Invoke-SubscriptionMove-Orchestrated.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-02-create-subscriptions/azurecli/Deploy-Subscriptions.azcli.ps1 | Creates the Azure subscriptions that landing_zone.subscriptions of infrastructure.yml lists without an id, with the Azure CLI. Supports -WhatIf. |
scripts/deploy/02-azure-foundation/phase-01-landing-zones/full-deployment/task-02-create-subscriptions/azurecli/Invoke-SubscriptionMove-Orchestrated.azcli.ps1 | Moves existing subscriptions under the management groups infrastructure.yml names for them, with the Azure CLI. Supports -WhatIf. |
Requires: PowerShell 7 and the Azure CLI, signed in with az login --tenant <azure.tenant_id>. Needs the Azure CLI extension account (az extension add --name account).
Install the extension once: the az account alias commands of Deploy-Subscriptions.azcli.ps1 belong to it, and without it that script stops with exit code 1. You need a role that may create subscriptions on the billing scope. The script prints the id of each subscription it creates: put it in landing_zone.subscriptions[].id. Moving a subscription changes the policy and role assignments it inherits, so review the target group and run with -WhatIf first.
Run
./Deploy-Subscriptions.azcli.ps1 -InfrastructureFile ./infrastructure.yml -WhatIf
./Deploy-Subscriptions.azcli.ps1 -InfrastructureFile ./infrastructure.yml
./Invoke-SubscriptionMove-Orchestrated.azcli.ps1 -InfrastructureFile ./infrastructure.yml -WhatIf
./Invoke-SubscriptionMove-Orchestrated.azcli.ps1 -InfrastructureFile ./infrastructure.yml
Using Existing Subscriptions
If your organization already has subscriptions provisioned (e.g., through a volume licensing agreement or prior setup), you can skip creation and just associate them with the correct management groups.
Move Existing Subscriptions
# Move a subscription to a management group
az account management-group subscription add \
--name "<management-group-id>" \
--subscription "<subscription-id-or-name>"
# PowerShell equivalent
New-AzManagementGroupSubscription `
-GroupId "<management-group-id>" `
-SubscriptionId "<subscription-id>"
Moving a subscription to a different management group changes which Azure Policies and RBAC role assignments it inherits. Review inherited policies before moving production subscriptions.
Validation
- All subscriptions exist with names from
infrastructure.yml - Each subscription is associated with the correct management group per the mapping table
- Subscriptions are visible under their respective MGs in the Azure Portal
- You have Owner or Contributor access to all subscriptions
Verify via CLI
# List subscriptions and their management group parents
az account management-group show --name "cmp-iic-root" --expand --recurse \
--query "children[].{Name:name, DisplayName:displayName, Children:children[].{Name:name, DisplayName:displayName, Subs:children[?type=='Microsoft.Management/managementGroups/subscriptions'].{Name:name, DisplayName:displayName}}}" \
-o json
# PowerShell: verify all subscriptions under root
Get-AzManagementGroup -GroupName "cmp-iic-root" -Expand -Recurse |
Select-Object -ExpandProperty Children |
Format-Table Name, DisplayName, Type -AutoSize
Troubleshooting
| Symptom | Error | Resolution |
|---|---|---|
| No enrollment account found | Empty result from az billing enrollment-account list | You need EA enrollment account owner role — contact your organization's EA admin |
| Subscription creation fails | AuthorizationFailed or BillingAccountNotFound | Verify your billing access — EA enrollment owner, MCA billing profile contributor, etc. |
| Cannot associate with MG | AuthorizationFailed | Verify Management Group Contributor role on the target MG |
| Subscription under wrong MG | Shows under root or Tenant Root Group | Move the subscription: az account management-group subscription add --name <target-mg> --subscription <sub-id> |
| Subscription quota exceeded | SubscriptionLimitReached | Request quota increase from Microsoft support |
| Subscription not visible | Not listed in Azure Portal | Verify you're signed into the correct tenant — check with az account show |
Next Steps
Proceed to Task 03: Create Resource Groups
References
- Create Azure Subscriptions Programmatically
- Create EA Subscriptions
- Create MCA Subscriptions
- Move Subscriptions Between Management Groups
- Azure Subscription Limits
Scripts for this task are located in the azurelocal-toolkit repository under scripts/deploy/ in the appropriate task folder.
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 01 — Management Groups | Full Deployment Overview | Task 03 — Create Resource Groups |
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 |