Merge pull request #8522 from MicrosoftDocs/main

Auto push to live 2025-03-20 02:00:02

Author: Deland-Han

support/azure/.openpublishing.redirection.azure.json

@@ -6299,6 +6299,10 @@
       {
         "source_path": "virtual-machines/linux/linux-vm-no-boot-hyper-v-driver-issues.md",
         "redirect_url": "/troubleshoot/azure/virtual-machines/linux/troubleshoot-lis-driver-issues-on-linux-vms"
+      },
+      {
+        "source_path": "azure-kubernetes/create-upgrade-delete/error-using-feature-requiring-virtual-machine-scale-set.md",
+        "redirect_url": "/troubleshoot/azure/azure-kubernetes/welcome-azure-kubernetes"
       }
   ]
 }

support/azure/azure-kubernetes/connectivity/error-from-server-error-dialing-backend-dial-tcp.md

@@ -1,8 +1,8 @@
 ---
 title: 'Error from server: error dialing backend: dial tcp'
 description: 'Troubleshoot the error dialing backend: dial tcp error that blocks you from using kubectl commands or other tools when you connect to the API server.'
-ms.date: 10/21/2024
-ms.reviewer: chiragpa, nickoman, v-leedennis, pihe
+ms.date: 03/05/2025
+ms.reviewer: chiragpa, nickoman, v-leedennis, pihe, mariusbutuc
 ms.service: azure-kubernetes-service
 keywords:
 #Customer intent: As an Azure Kubernetes user, I want to troubleshoot the "Error from server: error dialing backend: dial tcp" error so that I can connect to the API server or use the `kubectl logs` command to get logs.

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

@@ -1,8 +1,8 @@
 ---
 title: Troubleshoot the K8SAPIServerConnFailVMExtensionError error code (51)
 description: Learn how to troubleshoot the K8SAPIServerConnFailVMExtensionError error (51) when you try to start or create and deploy an Azure Kubernetes Service (AKS) cluster.
-ms.date: 01/24/2024
-ms.reviewer: rissing, chiragpa, erbookbi, v-leedennis, jovieir
+ms.date: 03/12/2025
+ms.reviewer: rissing, chiragpa, erbookbi, v-leedennis, jovieir, mariusbutuc
 ms.service: azure-kubernetes-service
 #Customer intent: As an Azure Kubernetes user, I want to troubleshoot the K8SAPIServerConnFailVMExtensionError error code (or error code ERR_K8S_API_SERVER_CONN_FAIL, error number 51) so that I can successfully start or create and deploy an Azure Kubernetes Service (AKS) cluster.
 ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
@@ -50,4 +50,4 @@ In rare cases, the firewall's outbound IP address can be blocked if you've autho
 
 - [General troubleshooting of AKS cluster creation issues](troubleshoot-aks-cluster-creation-issues.md)
 
-[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
+[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/azure-kubernetes/create-upgrade-delete/error-using-feature-requiring-virtual-machine-scale-set.md

@@ -1,8 +1,8 @@
 ---
 title: QuotaExceeded or InsufficientVCPUQuota error during creation or upgrade
 description: Resolves a QuotaExceeded or InsufficientVCPUQuota error during a creation or upgrade operation in an Azure Kubernetes Service (AKS) cluster.
-ms.date: 11/25/2024
-ms.reviewer: chiragpa, nickoman, v-weizhu
+ms.date: 03/07/2025
+ms.reviewer: chiragpa, nickoman, v-weizhu, mariusbutuc
 ms.service: azure-kubernetes-service
 keywords:
 #Customer intent: As an Azure Kubernetes user, I want to avoid the "QuotaExceeded" or "InsufficientVCPUQuota" error for virtual CPU (vCPU) usage so that I can create or upgrade an AKS cluster successfully.

support/azure/azure-kubernetes/create-upgrade-delete/quota-exceeded-during-creation-upgrade.md

@@ -1,8 +1,8 @@
 ---
 title: Troubleshoot the VMExtensionError_K8SAPIServerDNSLookupFail error code 
 description: Learn how to troubleshoot the VMExtensionError_K8SAPIServerDNSLookupFail (52) when you try to start or create and deploy an Azure Kubernetes Service (AKS) cluster.
-ms.date: 01/24/2024
-ms.reviewer: rissing, chiragpa, erbookbi, v-leedennis, jovieir
+ms.date: 03/12/2025
+ms.reviewer: rissing, chiragpa, erbookbi, v-leedennis, jovieir, mariusbutuc
 ms.service: azure-kubernetes-service
 #Customer intent: As an Azure Kubernetes user, I want to troubleshoot the VMExtensionError_K8SAPIServerDNSLookupFail error code (or error code ERR_K8S_API_SERVER_DNS_LOOKUP_FAIL, error number 52) so that I can successfully start or create and deploy an Azure Kubernetes Service (AKS) cluster.
 ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)

support/azure/azure-kubernetes/error-codes/vmextensionerror-k8sapiserverdnslookupfail.md

@@ -1,8 +1,8 @@
 ---
 title: Failed to create file share on storage account
 description: Troubleshoot why you can't create a file share on a storage account for an Azure Kubernetes Service (AKS) cluster.
-ms.date: 11/20/2024
-ms.reviewer: chiragpa, nickoman, wonkilee, v-leedennis
+ms.date: 03/14/2025
+ms.reviewer: chiragpa, nickoman, wonkilee, v-leedennis, mariusbutuc
 ms.service: azure-kubernetes-service
 #Customer intent: As an Azure Kubernetes user, I want to troubleshoot why I can't create a file share on a storage account so that I can do dynamic provisioning on my Azure Kubernetes Service (AKS) cluster.
 ms.custom: sap:Storage

support/azure/azure-kubernetes/storage/create-file-share-failed-storage-account.md

@@ -109,8 +109,6 @@
       href: create-upgrade-delete/error-code-subnetisfull.md
     - name: Cluster upgrading and scaling errors
       href: create-upgrade-delete/upgrading-or-scaling-does-not-succeed.md
-    - name: Errors using features that require virtual machine scale sets
-      href: create-upgrade-delete/error-using-feature-requiring-virtual-machine-scale-set.md
     - name: Node count isn't in autoscaler min and max range
       href: create-upgrade-delete/node-count-is-not-in-autoscaler-min-max-range.md
   - name: Start operations

support/azure/azure-kubernetes/toc.yml

@@ -1,5 +1,5 @@
 ---
-title: Error AADSTS50000 - There was an error issuing a token or an issue with our sign-in service
+title: Error AADSTS50000 - There Was an Error Issuing a Token or an Issue with Our Sign-In Service
 description: Provides a solution to the AADSTS50000 error that occurs when you try to sign in to an Azure app by using Microsoft Entra ID.
 ms.service: entra-id
 ms.date: 03/12/2025
@@ -37,7 +37,7 @@ Make sure that the client ID is valid and that other required parameters are con
 
 This issue can occur in an OAuth2 Device code grant flow to the token endpoint. After the user signs in to a browser window and accepts the consent dialog, this error occurs.
 
-### Solution 3 for cause 3: Verify application consent settings
+### Solution for cause 3: Verify application consent settings
 
 1. In the [Azure portal](https://portal.azure.com), make sure that the client application (Service Principal) exists on the tenant's **Enterprise Applications** page. You can search for the application by App ID.
 2. Verify that the user can consent to the application. Check the user settings on the **Enterprise Applications** page or review relevant policies that affect user consent.
@@ -54,7 +54,7 @@ Microsoft Identity Platform (v2 endpoint) tokens must be signed by a certificate
 2. In the **Manage** section,  select **Manifest**.
 3. Check whether an entry exists in the `keyCredentials` section that includes `type=Symmetric` and `usage=Sign`.
 
-    :::image type="content" source="./media/error-code-aadsts50000-issuing-token-sign-in-service/manifest-sample.png" alt-text="Screenshot that shows the Application Manifest Key Credentials code" lightbox="./media/error-code-aadsts50000-issuing-token-sign-in-service/manifest-sample.png":::
+    :::image type="content" source="./media/error-code-aadsts50000-issuing-token-sign-in-service/manifest-sample.png" alt-text="Screenshot that shows the Application Manifest Key Credentials code." lightbox="./media/error-code-aadsts50000-issuing-token-sign-in-service/manifest-sample.png":::
 
 Alternatively, use the Microsoft Graph PowerShell cmdlet [Get-MgApplication](/powershell/module/azuread/get-azureadapplicationkeycredential) to retrieve key credentials.
 
@@ -83,4 +83,4 @@ This error might occur in the following scenario:
 
 ### Solution for cause 5
 
-Configure the resource application to expose the delegated permission, and then consent to that delegated permission in the client application.
+Configure the resource application to expose the delegated permission, and then consent to that delegated permission in the client application.