Is anyone else seeing the "AKSCapacityHeavyUsage" error when trying to create a new Azure Kubernetes Service cluster in Central US? The message says cluster creation is temporarily unavailable in that region and recommends choosing an alternate location. I've been running into this repeatedly and would like to know whether it's a broader regional capacity issue, whether retrying helps, or if there are specific regions or availability zones that work better.
4 Answers
Central US has had AKS capacity problems for several weeks. It may be related to exhaustion of the VM SKUs used by the node pool rather than AKS itself. Try another availability zone in Central US first, then consider East US 2 or South Central US if those are acceptable for your deployment.
This seems to be part of a wider capacity squeeze. Providers are under pressure from high memory costs and demand for AI infrastructure, while older VM SKUs are being restricted or retired. That can leave less usable rack space and power for general-purpose workloads, even when the provider technically has hardware available.
I’ve encountered the same problem in another US region, so it isn’t necessarily limited to Central US. Checking the exact node-pool SKU and testing a supported alternative SKU can help, but moving the deployment to a nearby region may be the quickest workaround.
I’ve seen a similar error when deploying Azure Container Apps, and retrying after a short wait sometimes works. It depends on the service, region, and VM SKU, though, so a different zone or region is usually more reliable than repeatedly submitting the same deployment.
That would explain why the issue seems tied to particular VM families and regions instead of affecting every deployment equally.