How to fix Error: Error creating AKS Cluster: QuotaExceeded in Terraform

TerraformINTERMEDIATEHIGHUpdated Dec 31, 2025· 114 views

This error occurs when your Azure subscription has reached its resource quota limit for creating AKS clusters or provisioning the required vCPUs for nodes. Azure enforces quota limits per subscription and region to prevent unintended over-provisioning. Resolving this requires either requesting a quota increase or using fewer resources in your cluster configuration.

Quick fix

Fixes QuotaExceeded

az vm list-usage --location eastus -o table
  1. Check current quota usage and limits
  2. Request a quota increase via Azure Portal
  3. Reduce node count or VM size in your Terraform configuration
  4. Switch to a different region if available
terraform — error
az vm list-usage --location eastus -o table
Error: Error creating AKS Cluster: QuotaExceeded

What this error means

Azure Kubernetes Service enforces quota limits on the number of managed clusters and vCPU resources available in each subscription per region. When you attempt to create or scale an AKS cluster via Terraform, Azure Resource Manager validates that the operation won't exceed these approved limits. If the requested resources exceed the current quota, the operation fails with a QuotaExceeded error. This is a safety mechanism to prevent unexpected costs and resource exhaustion.

Typical symptoms

  • Terraform apply fails with 'QuotaExceeded' error message during AKS cluster creation
  • Error message mentions 'exceeding approved' quota for cores or vCPU family
  • Scaling an existing AKS cluster fails with quota errors
  • Error specifies 'Total Regional Cores quota' or specific VM family quota (e.g., 'standardDSv3Family Cores')
  • Same Terraform configuration works in one region but fails in another
  • Cluster creation worked previously but now fails

Common causes

  1. Your Azure subscription has reached the maximum number of AKS clusters allowed per region
  2. The vCPU quota for your chosen VM family is exhausted in the selected region
  3. The total regional vCPU quota is insufficient for the requested node pool size
  4. Previous failed deployments left resources consuming quota that weren't cleaned up
  5. Default quota limits for new subscriptions are too low for multi-cluster deployments
  6. You're deploying in a region with high demand and reduced available capacity

How to fix "Error: Error creating AKS Cluster: QuotaExceeded"

1Check current quota usage and limits

In the Azure Portal, navigate to your subscription > Usage + quotas. Search for 'Compute' to view vCPU and managed cluster quotas. Note the current usage and limits for each VM family and region where you're deploying. Use the Azure CLI command:

bash
az vm list-usage --location eastus -o table

Replace 'eastus' with your target region. This shows current usage vs. limits for all compute resources.

2Request a quota increase via Azure Portal

Go to Azure Portal > Subscriptions > select your subscription > Usage + quotas. Click 'Request increase' next to the quota that's exceeded (typically 'Total Regional vCPUs' or a specific family like 'Standard DSv3 Family vCPUs'). In the request form:
- Select the VM family or Total Regional vCPUs option
- Enter the new quota limit you need
- Provide a business justification
- Click 'Request' to submit

Quota increase requests are typically approved within 1-2 business days.

3Reduce node count or VM size in your Terraform configuration

While waiting for quota approval, temporarily reduce the cluster size in your main.tf:

hcl
resource "azurerm_kubernetes_cluster" "example" {
  default_node_pool {
    vm_size       = "Standard_B2s"  # Use smaller SKU
    node_count    = 1               # Start with 1 node
    max_count     = 5
    min_count     = 1
  }
}

After quota increase is approved, update these values to your desired configuration and run terraform apply again.

4Switch to a different region if available

If the quota increase is urgent, deploy your AKS cluster in a different Azure region that has available capacity. Update your Terraform provider or variable:

hcl
provider "azurerm" {
  features {}
}

variable "location" {
  default = "westus2"  # Different region
}

Run terraform plan to verify the new region has sufficient quota, then apply. Once your primary region quota is increased, migrate your cluster or deploy additional clusters.

5Verify quota increase approval and retry deployment

After Azure approves your quota increase request (typically 1-2 business days), verify in Azure Portal > Usage + quotas that the new limits are in place. Then update your Terraform configuration back to your desired settings:

bash
terraform plan

If the plan shows no errors, proceed with:

bash
terraform apply

Your AKS cluster should now create successfully.

6Clean up failed deployments and unused clusters

To free up quota for future deployments, remove unused AKS clusters in your subscription. Check your Terraform state for orphaned or failed clusters:

bash
terraform state list

Delete unused clusters either via:

bash
terraform destroy -target=azurerm_kubernetes_cluster.example

Or manually in Azure Portal > Resource groups > select group > select cluster > Delete. This immediately frees up quota for new deployments.

Advanced notes

AKS quota operates at the subscription and region level. As of September 2025, Azure rolled out a managed cluster quota that limits the number of AKS clusters per subscription per region (typically 100). Each cluster also requires vCPU quota for its nodes. Free trial subscriptions and 'Azure for Students' accounts have lower quota limits and may not be eligible for increases—upgrading to a pay-as-you-go subscription resolves this. For multi-region deployments, track quota per region separately. When upgrading an AKS cluster, temporary surge nodes consume additional vCPU quota; set max_surge values conservatively. If your organization uses cost controls or spending limits, verify those aren't also blocking the deployment. Enterprise Agreement (EA) customers may have higher base quotas; contact Microsoft support for region-specific capacity planning.

Frequently asked questions

What does "QuotaExceeded" mean?
Azure Kubernetes Service enforces quota limits on the number of managed clusters and vCPU resources available in each subscription per region. When you attempt to create or scale an AKS cluster via Terraform, Azure Resource Manager validates that the operation won't exceed these approved limits. If the requested resources exceed the current quota, the operation fails with a QuotaExceeded error.
How do I fix "QuotaExceeded"?
This error occurs when your Azure subscription has reached its resource quota limit for creating AKS clusters or provisioning the required vCPUs for nodes. Azure enforces quota limits per subscription and region to prevent unintended over-provisioning. Resolving this requires either requesting a quota increase or using fewer resources in your cluster configuration.
What causes "QuotaExceeded"?
Your Azure subscription has reached the maximum number of AKS clusters allowed per region The vCPU quota for your chosen VM family is exhausted in the selected region The total regional vCPU quota is insufficient for the requested node pool size
Is the "QuotaExceeded" error serious?
Yes. This is a high-severity error that usually blocks work until it is fixed, but the steps above resolve it.

Official resources & further reading