Update akscapacityerror.md

Error code has been changed to AksCapacityHeavyUsage

Author: abubinski

support/azure/azure-kubernetes/create-upgrade-delete/akscapacityerror.md

@@ -10,33 +10,23 @@ ms.service: azure-kubernetes-service
 ms.topic: troubleshooting-problem-resolution
 ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
 ---
-# Troubleshoot the AKSCapacityError error code
+# Troubleshoot the AksCapacityHeavyUsage error code
 
-This article discusses how to identify and resolve the `AKSCapacityError` error that might occur when you create or start a Microsoft Azure Kubernetes Service (AKS) cluster.
+This article discusses how to identify and resolve the `AksCapacityHeavyUsage` error that might occur when you create a Microsoft Azure Kubernetes Service (AKS) cluster.
 
 ## Symptoms
 
-When you try to create or start an AKS cluster, you receive one of the following error messages:
+When you try to create an AKS cluster, you receive the following error messages:
 
-> **Code:** AKSCapacityError
+> **Code:** AksCapacityHeavyUsage
 >
-> **Message 1:** Creating or starting a free tier cluster is unavailable at this time in region \<Region\>. To create a new cluster, we recommend using an alternate region, or create a paid tier cluster. For a list of all the Azure regions, visit <https://aka.ms/aks/regions>. For more details on this error, visit <https://aka.ms/akscapacityerror>.
->
-> **Message 2:** Creating a new cluster or starting cluster is unavailable at this time in region \<Region>. To create a new cluster, we recommend using an alternate region. For a list of all the Azure regions, visit <https://aka.ms/aks/regions>. For more details on this error, visit <https://aka.ms/akscapacityerror>.
-
-If you then try to do an operation on that cluster after it doesn't start, you receive the following error message:
-
-> **"statusCode":** "InternalServerError",
->
-> **"serviceRequestId":** null,
->
-> **"statusMessage":** "{**\"code\":** \"KubernetesAPICallFailed\", **\"message\":** \"API call to Kubernetes API Server failed.\"}.
+> **Message:** AKS is experiencing heavy usage in region <Region>. We are working on adding new capacity. In the meantime, please consider creating new AKS clusters in a different region. For a list of all the Azure regions, visit https://aka.ms/aks/regions. For more details on this error, visit https://aka.ms/akscapacityheavyusage.
 
 ## Cause
 
-You're trying to deploy a cluster in a region that has limited capacity.
+You're trying to create a cluster in a region that has limited capacity.
 
-When you create or start an AKS cluster, Microsoft Azure allocates compute resources to your subscription. You might occasionally experience the `AKSCapacityError` error because of significant growth in demand for Azure Kubernetes Service in specific regions.
+When you create an AKS cluster, Microsoft Azure allocates compute resources to your subscription. You might occasionally experience the `AksCapacityHeavyUsage` error because of significant growth in demand for Azure Kubernetes Service in specific regions.
 
 The `KubernetesAPICallFailed` error message indicates that the AKS cluster didn't start and doesn't have an associated control plane. Therefore, calls to the API server are failing. In this case, you have to retry the Start operation.
 
@@ -50,11 +40,11 @@ This approach might not be feasible if you already have existing resources in th
 
 ### Solution 2: Try deploying a cluster that has different settings
 
-The infrastructure that hosts AKS managed clusters have different allocation reservations. Therefore, AKS might have more capacity for public clusters than for private clusters. If you encounter the `AKSCapacityError` error when you try to create a private cluster, try to create a public cluster instead or vice versa.
+The infrastructure that hosts AKS managed clusters have different allocation reservations. Therefore, AKS might have more capacity for public clusters than for private clusters. If you encounter the `AksCapacityHeavyUsage` error when you try to create a private cluster, try to create a public cluster instead or vice versa.
 
 ### Solution 3: Use an Azure Enterprise subscription
 
-When capacity is running low, we limit free tier AKS clusters for customers who don't have an Enterprise Agreement (EA) subscription first in order to reserve resources for real production scenarios. Make sure that you use an EA subscription to create your AKS cluster.
+When capacity is running low, we limit AKS cluster creates for customers who don't have an Enterprise Agreement (EA) subscription first in order to reserve resources for real production scenarios. Make sure that you use an EA subscription to create your AKS cluster.
 
 ### Solution 4: Retry the operation