Merge pull request #8593 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/SupportArticles-docs (branch main)

Author: Simonx Xu

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 message:
 
-> **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.
 
@@ -48,23 +38,23 @@ The easiest and quickest solution is to try to deploy to a different region (for
 
 This approach might not be feasible if you already have existing resources in the requested region, but it's the preferred solution in a dev/test scenario.
 
-### Solution 2: Try deploying a cluster that has different settings
+### Solution 2: Deploy 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 it has for private clusters. If you experience 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, non-Enterprise Agreement (EA) subscriptions are limited first in AKS cluster creation to reserve resources for real production scenarios. If you have an EA subscription, make sure that you use the EA subscription to create the AKS cluster.
 
 ### Solution 4: Retry the operation
 
 Capacity is often reclaimed when other users stop or delete their AKS clusters. Therefore, the operation might succeed if you retry it later.
 
 ## More information
 
-- Ensuring capacity for users is a top priority for Microsoft, and we're working around the clock to reach this goal. The increasing popularity of Azure services emphasizes the need for us to scale up our infrastructure even more rapidly. With that in mind, we're expediting expansions and improving our resource deployment process to respond to strong customer demand. We're also adding a large amount of compute infrastructure monthly.
+- Ensuring capacity for users is a top priority for Microsoft, and we're working to scale up our infrastructure to accommodate the increasing popularity of Azure services.
 
-   We have identified several methods to improve how we load-balance under a high-resource-usage situation, and how to trigger the timely deployment of needed resources. Additionally, we're significantly increasing our capacity, and will continue to plan for strong demand across all regions. [This September 2021 Azure Blog article](https://azure.microsoft.com/blog/advancing-reliability-through-a-resilient-cloud-supply-chain/) discusses improvements that we're making toward delivering a resilient cloud supply chain.
+    For more information about improvements that we're making toward delivering a resilient cloud supply chain, see [this September 2021 Azure Blog article](https://azure.microsoft.com/blog/advancing-reliability-through-a-resilient-cloud-supply-chain/).
 
 - [General troubleshooting of AKS cluster creation issues](troubleshoot-aks-cluster-creation-issues.md)
 

support/azure/azure-kubernetes/create-upgrade-delete/error-code-inuseroutetablecannotbedeleted.md

@@ -1,9 +1,9 @@
 ---
 title: Troubleshoot the InUseRouteTableCannotBeDeleted error code
 description: Learn how to troubleshoot the InUseRouteTableCannotBeDeleted error when you try to delete an Azure Kubernetes Service (AKS) cluster.
-ms.date: 11/12/2024
+ms.date: 03/28/2025
 editor: v-jsitser
-ms.reviewer: rissing, chiragpa, edneto, v-leedennis
+ms.reviewer: rissing, chiragpa, edneto, wonkilee, v-leedennis
 ms.service: azure-kubernetes-service
 #Customer intent: As an Azure Kubernetes user, I want to troubleshoot the InUseRouteTableCannotBeDeleted error code so that I can successfully delete an Azure Kubernetes Service (AKS) cluster.
 ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
@@ -30,6 +30,6 @@ You tried to delete the AKS cluster while its associated route table was still i
 
 ## Solution
 
-Remove the associated subnet in the route table. For instructions, see [Dissociate a route table from a subnet](/azure/virtual-network/manage-route-table#dissociate-a-route-table-from-a-subnet). Then, try again to delete the AKS cluster.
+Remove the associated route table from the subnet. For instructions, see [Dissociate a route table from a subnet](/azure/virtual-network/manage-route-table#dissociate-a-route-table-from-a-subnet). Then, try again to delete the AKS cluster.
 
 [!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/windows-client/shell-experience/monitor-powers-off-when-pc-locked.md

@@ -34,9 +34,9 @@ This behavior is by design in Windows. By default, when the console is locked, W
 
 Using the PowerCfg.exe utility, you can configure the display timeout used when the PC is in an unlocked state as well as when it is at a locked screen. From an administrative command prompt, the following commands can be used to control the display timeout:
 
-- `powercfg.exe /setacvalueindex SCHEME_CURRENT SUB_VIDEO VIDEOIDLE \<time in seconds>`
+- `powercfg.exe /setacvalueindex SCHEME_CURRENT SUB_VIDEO VIDEOIDLE <time in seconds>`
 
-- `powercfg.exe /setacvalueindex SCHEME_CURRENT SUB_VIDEO VIDEOCONLOCK \<time in seconds>`
+- `powercfg.exe /setacvalueindex SCHEME_CURRENT SUB_VIDEO VIDEOCONLOCK <time in seconds>`
 
 - `powercfg.exe /setactive SCHEME_CURRENT`
 
@@ -56,5 +56,5 @@ powercfg.exe -attributes SUB_VIDEO 8EC4B3A5-6868-48c2-BE75-4F3044BE88A7 -ATTRIB_
 To hide the option, run the following command:
 
 ```console
-powercfg.exe -attributes SUB_VIDEO 8EC4B3A5-6868-48c2-BE75-4F3044BE88A7 +ATTRIB_HIDE`
+powercfg.exe -attributes SUB_VIDEO 8EC4B3A5-6868-48c2-BE75-4F3044BE88A7 +ATTRIB_HIDE
 ```

support/windows-server/remote/troubleshoot-rds-licensing-guidance.md

@@ -12,7 +12,7 @@ ms.custom:
 ---
 # RDS Licensing troubleshooting guidance
 
-<p class="alert is-flex is-primary"><span class="has-padding-left-medium has-padding-top-extra-small"><a class="button is-primary" href="https://vsa.services.microsoft.com/v1.0/?partnerId=7d74cf73-5217-4008-833f-87a1a278f2cb&flowId=DMC&initialQuery=31806373" target='_blank'><b>Try our Virtual Agent</b></a></span><span class="has-padding-small"> - It can help you quickly identify and fix common Active Directory replication issues</span>
+<p class="alert is-flex is-primary"><span class="has-padding-left-medium has-padding-top-extra-small"><a class="button is-primary" href="https://vsa.services.microsoft.com/v1.0/?partnerId=7d74cf73-5217-4008-833f-87a1a278f2cb&flowId=DMC&initialQuery=31806373" target='_blank'><b>Try our Virtual Agent</b></a></span><span class="has-padding-small"> - It can help you quickly identify and fix common Remote Desktop licensing problems </span>
 
 The listed resources in this article can help you resolve Remote Desktop Services (RDS) licensing issues.