| name | azure-capacity-management |
| description | This skill should be used when the user asks about Azure capacity management, quota
operations, or capacity planning for SaaS ISVs running workloads in their own Azure
subscriptions under EA or MCA. Relevant queries include: how to increase VM quota across
subscriptions, how quota groups work, how to create or share capacity reservation groups,
what the difference is between capacity reservations and Azure Reservations or savings plans,
how to request region access or zonal enablement, how logical and physical availability zones
map across subscriptions, how to configure quota or budget or anomaly alerts, how AKS node
pools interact with capacity reservations, how to manage non-compute quotas, how deployment
stamps relate to the capacity supply chain, and how to design an estate-level capacity
governance program. Also covers quota transfers, overallocation, SKU restrictions, CRG
sharing, billing hierarchy, and subscription vending.
|
Azure capacity management
Estate-level capacity and quota management for SaaS ISVs operating workloads in subscriptions they own or control under an Enterprise Agreement (EA) or Microsoft Customer Agreement (MCA). This skill aligns with the ISV landing zone guidance and covers pure SaaS and stamp-based isolation patterns where customers are isolated through dedicated or shared deployment stamps inside the ISV's Azure estate.
Read the full supply chain reference at references/docs/operations/capacity-and-quotas/README.md.
Capacity supply chain
Treat capacity management as a four-step supply chain aligned with Well-Architected capacity planning, reliable scaling, and workload supply chain guidance:
| Step | What it does | Azure surfaces |
|---|
| Forecast | Size scale units from telemetry and business targets | Azure Monitor, capacity planning models, FinOps budgets |
| Procure | Unblock regions, zones, and SKUs; aggregate quota | Region access requests, zonal enablement, quota groups, per-VM quota increases |
| Allocate | Lock compute supply for critical SKUs | Capacity reservation groups, CRG sharing, overallocation |
| Monitor | Track utilization and promote through gates | Quota alerts, budget alerts, anomaly alerts, CI/CD gates |
Read references/docs/operations/capacity-planning/README.md for forecasting details and references/docs/operations/capacity-governance/README.md for the governance program design.
Quota operations
Azure assigns default quota limits per subscription. EA subscriptions typically start with 350 cores; pay-as-you-go subscriptions start with 20 cores. Some VM series have offer restrictions that block deployment until you request access.
Key workflows:
CLI reference:
az quota usage list --scope /subscriptions/{sub-id}/providers/Microsoft.Compute/locations/{location}
az quota create --resource-name "StandardDSv3Family" --scope /subscriptions/{sub-id}/providers/Microsoft.Compute/locations/{location} --limit-object value=500
Read references/docs/operations/quota/README.md for the complete quota operations reference.
Quota groups
Quota groups are ARM objects that aggregate compute quota across eligible subscriptions at the management group scope. They reduce stranded VM-family headroom and let you request group-level increases.
Prerequisites: Register the Microsoft.Quota resource provider on each member subscription. The management group must exist before creating the quota group.
Limitations:
- IaaS compute only — doesn't cover storage, networking, or PaaS services
- A subscription can belong to a single quota group at a time (source)
- Doesn't grant region or zone access — those require separate support requests
- Quota transfers move allocation between member subscriptions but don't change the group total
Lifecycle: Create the quota group under a management group, add subscriptions, then request group-level limit increases. Monitor allocation snapshots and transfer as demand shifts between subscriptions.
Read references/docs/operations/quota-groups/README.md for the complete reference including ARM lifecycle, transfer mechanics, and monitoring integration.
Capacity reservations
Capacity reservation groups (CRGs) guarantee compute capacity for specific VM sizes in a region or availability zone. CRGs are capacity guarantees, not pricing commitments — unused reserved capacity is billed at the pay-as-you-go rate for the VM size.
Cost implications: Reserved capacity is billed whether or not VMs run against it. Pair CRGs with Azure Reservations or savings plans to get both capacity guarantee and pricing discount.
Sharing (preview): CRGs can be shared across subscriptions within the same tenant. The ODCR owner in the consumer subscription needs Microsoft.Compute/capacityReservationGroups/share/action. The VM owner in the consumer subscription needs Microsoft.Compute/capacityReservationGroups/read, Microsoft.Compute/capacityReservationGroups/deploy, Microsoft.Compute/capacityReservationGroups/capacityReservations/read, and Microsoft.Compute/capacityReservationGroups/capacityReservations/deploy. Portal support isn't available in preview; use CLI, PowerShell, or REST API.
Overallocation: Overallocation lets you deploy more VMs than the reserved quantity. Excess VMs don't have capacity guarantees but benefit from the reservation when capacity is available.
Zone alignment: CRGs are zone-specific. Before sharing across subscriptions, verify logical-to-physical zone mapping with the Get-AzAvailabilityZoneMapping.ps1 script — logical zones can map to different physical zones across subscriptions.
Read references/docs/operations/capacity-reservations/README.md for the complete reference including automation patterns (REST API, Bicep, Terraform).
AKS capacity governance
AKS node pools consume VM quota and can associate with capacity reservation groups, but with constraints specific to the AKS lifecycle:
- Node pool CRG association happens at creation time — you can't associate an existing node pool with a CRG after the fact
- Identity requirement: The AKS cluster must use a user-assigned managed identity with
Microsoft.Compute/capacityReservationGroups/read permission on the CRG
- Disassociation removes the CRG association but doesn't delete the node pool
- Zone alignment matters for cross-subscription CRG sharing — verify physical zone mapping before configuring AKS node pools against shared CRGs
Read references/docs/operations/aks-capacity/README.md for the complete reference including Bicep and Terraform examples.
Non-compute quotas
Storage accounts, App Service plans, Cosmos DB throughput, Service Bus namespaces, Key Vault transactions, and other services have their own quota limits outside the compute quota system. Quota groups don't cover these — manage them through standard quota requests and service-specific scaling controls.
Read references/docs/operations/non-compute-quotas/README.md for service-specific quota references.
Monitoring and governance
Three alert types cover the capacity governance space:
- Quota alerts: Azure Monitor alerts triggered when quota usage crosses a configured threshold. Requires Reader or higher on the subscription.
- Budget alerts: Cost Management alerts triggered when actual or forecasted spend exceeds budget thresholds. Uses Cost Management RBAC.
- Anomaly alerts: Cost Management anomaly detection that flags unexpected spending patterns. Deploy with
references/scripts/anomaly-alerts/Deploy-AnomalyAlert.ps1 or bulk deploy with references/scripts/anomaly-alerts/Deploy-BulkALZ.ps1.
Governance cadence: Monthly quota reviews, quarterly capacity planning cycles, and post-incident reviews when scaling events fail. Read references/docs/operations/monitoring-alerting/README.md for alert configuration details and references/docs/operations/capacity-governance/README.md for the governance program design.
Scripts quick reference
| Script | Path | Purpose |
|---|
| Get-AzVMQuotaUsage.ps1 | references/scripts/quota/ | Multi-threaded quota analysis across subscriptions |
| Show-AzVMQuotaReport.ps1 | references/scripts/quota/ | Single-threaded quota reporting |
| Get-AzAvailabilityZoneMapping.ps1 | references/scripts/quota/ | Logical-to-physical zone mapping |
| Get-BenefitRecommendations.ps1 | references/scripts/rate/ | Reservation and savings plan recommendations |
| Deploy-AnomalyAlert.ps1 | references/scripts/anomaly-alerts/ | Deploy cost anomaly alerts |
| Deploy-BulkALZ.ps1 | references/scripts/anomaly-alerts/ | Bulk deploy anomaly alerts |
| Deploy-Budget.ps1 | references/scripts/budgets/ | Deploy individual budgets |
| Deploy-BulkBudgets.ps1 | references/scripts/budgets/ | Bulk deploy budgets |
| Suppress-AdvisorRecommendations.ps1 | references/scripts/advisor/ | Suppress Advisor recommendations |
| calculator.py | references/scripts/calculator/ | Safe math evaluation for cost modeling |
| Serverless SQL workbook | references/scripts/serverless-sql-storage/ | Azure Monitor workbook for serverless SQL allocated vs. used storage; identifies databases worth shrinking to reclaim billing waste |
Read the README in each script directory for parameter requirements and prerequisites.
Key distinctions
These are commonly confused — keep them separated:
- Capacity reservation vs Azure Reservation vs savings plan: Capacity reservations guarantee compute supply. Azure Reservations and savings plans provide pricing discounts. Capacity guarantees supply; pricing commitments reduce cost.
- Quota group vs management group: Quota groups aggregate compute quota. Management groups organize subscriptions for RBAC and policy. Quota groups are created under management groups but don't inherit their policy or access controls.
- Logical vs physical zone: Logical zones are subscription-specific labels. Physical zones are datacenter locations. Zone 1 in subscription A may map to a different physical zone than zone 1 in subscription B.
- Region access vs quota increase: Quota increases raise limits within an already-enabled region. Region access requests unblock a restricted region for the subscription.
Operational agent
The azure-capacity-manager agent is a capacity management specialist. It handles operational tasks like quota analysis and reservation evaluation, but it's also effective for thinking through architecture decisions, sanity-checking assumptions, exploring what-if scenarios, or talking through a customer engagement. It has deep domain expertise in the full capacity supply chain, access to the same references, and can run scripts and az commands for live operations. An expert on tap — use it liberally.
Documentation map
| Domain | Reference path |
|---|
| Supply chain hub | references/docs/operations/capacity-and-quotas/README.md |
| Glossary | references/docs/operations/glossary.md |
| Quota operations | references/docs/operations/quota/README.md |
| Quota groups | references/docs/operations/quota-groups/README.md |
| Capacity reservations | references/docs/operations/capacity-reservations/README.md |
| AKS capacity | references/docs/operations/aks-capacity/README.md |
| Non-compute quotas | references/docs/operations/non-compute-quotas/README.md |
| Monitoring and alerting | references/docs/operations/monitoring-alerting/README.md |
| Capacity governance | references/docs/operations/capacity-governance/README.md |
| Capacity planning | references/docs/operations/capacity-planning/README.md |
| Billing (EA) | references/docs/billing/legacy/README.md |
| Billing (MCA) | references/docs/billing/modern/README.md |
| Deployment patterns | references/docs/deployment/README.md |
| Tools and scripts | references/docs/operations/tools-scripts/README.md |
| Quota scripts | references/scripts/quota/README.md |
| Anomaly alerts | references/scripts/anomaly-alerts/README.md |
| Budgets | references/scripts/budgets/README.md |
| Rate optimization | references/scripts/rate/README.md |
| Serverless SQL storage | references/scripts/serverless-sql-storage/README.md |
