Container Apps: Deployment Failure Due to AKSCapacityHeavyUsage in Central US

Hello @Brittany-2456

Hey! Sorry you’re hitting this—this specific error pattern is consistent with a regional AKS/placement capacity constraint that impacts creating new Azure Container Apps managed environments in Central US.

What the error means (Central US)

Product-side investigation for this exact class of failures shows:

• New internal, VNet-integrated Container Apps environment creation (Consumption workload profile) in Central US repeatedly fails with ManagedEnvironmentCapacityHeavyUsageError / AKSCapacityHeavyUsage.
• The issue is a capacity constraint on the underlying managed Kubernetes infrastructure in the region, not something specific to your subscription and not caused by your networking, RBAC, or policy configuration.
• Existing Container Apps environments in Central US continue to run normally—only new environment creation is impacted.
• There’s no supported way to “reserve” capacity for your subscription to bypass the constraint.
• No supported configuration change (including ingress type, zone redundancy, etc.) is available that avoids the constrained capacity pool.
• Product also noted: “Creating a new cluster is unavailable at this time in region centralus.”

What you can do right now (supported workarounds)

Use an existing Central US environment

• Since your existing environments still run normally, the recommended path is to deploy additional apps/jobs into an existing managed environment rather than creating a new one.

Retry new environment creation periodically

  - Periodically retry creation in Central US.
  
     - **If you attempt again, delete the failed environment attempt before retrying** (so you don’t accumulate partial/failed resources).
     
     **If you need it urgently, create in another region**
     
        - For urgent needs, the supported workaround is to **create the managed environment in a different Azure region with capacity**.
        
           - The regions listed by the platform/product team include: **australiaeast, australiasoutheast, austriaeast, belgiumcentral, brazilsouth, canadacentral, canadaeast, centralindia, centraluseuap, chilecentral, eastasia, eastus2, eastus2euap, francecentral, francesouth, germanynorth, indonesiacentral, italynorth, japaneast, japanwest, jioindiacentral, jioindiawest, koreacentral, koreasouth, malaysiawest, mexicocentral, newzealandnorth, northeurope, norwayeast, polandcentral, southafricanorth, southcentralus, southeastasia, southindia, spaincentral, switzerlandnorth, switzerlandwest, uaecentral, uaenorth, uksouth, ukwest, westcentralus, westeurope, westus, westus2, westus3**.
           

Is there an ETA?

From the provided investigation update: capacity had not yet been fully restored and no specific ETA was available at the time of the update; platform team was expanding capacity.

Please “upvote” if the information helped you. This will help us and others in the community as well.