Merge pull request #3539 from MicrosoftDocs/main638763805227194846sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

.openpublishing.redirection.aks.json

@@ -144,7 +144,7 @@
             href: kubernetes-monitor-metrics.md
   - name: Troubleshooting
     items:
-    - name: Troubleshoot & known issues
+    - name: Troubleshoot and known issues
       href: aks-troubleshoot.md
     - name: Control plane configuration validation errors
       href: control-plane-validation-errors.md
@@ -157,11 +157,15 @@
     - name: KubeAPIServer unreachable error
       href: kube-api-server-unreachable.md
     - name: Can't see VM SKUs on Azure portal
-      href: tsg-check-vm-sku.md
+      href: check-vm-sku.md
     - name: Deleted AKS Arc cluster still visible on Azure portal
       href: deleted-cluster-visible.md
     - name: Can't fully delete AKS Arc cluster with PodDisruptionBudget (PDB) resources
       href: delete-cluster-pdb.md
+    - name: Azure Advisor upgrade recommendation
+      href: azure-advisor-upgrade.md
+    - name: Issues after deleting storage volumes
+      href: delete-storage-volume.md
   - name: Reference
     items:
     - name: Azure CLI

AKS-Arc/TOC.yml

@@ -3,7 +3,7 @@ title: Troubleshoot common issues in AKS enabled by Azure Arc
 description: Learn about common issues and workarounds in AKS enabled by Arc.
 ms.topic: how-to
 author: sethmanheim
-ms.date: 11/22/2024
+ms.date: 02/28/2025
 ms.author: sethm 
 ms.lastreviewed: 02/27/2024
 ms.reviewer: guanghu
@@ -12,22 +12,27 @@ ms.reviewer: guanghu
 
 # Troubleshoot common issues in AKS enabled by Azure Arc
 
-This article describes how to find solutions for issues you encounter when using AKS enabled by Azure Arc. Known issues and errors are organized by functional area. You can use the links provided in this article to find solutions and workarounds to resolve them.
+This section describes how to find solutions for issues you encounter when using AKS enabled by Azure Arc.
 
 ## Open a support request
 
-See the [Get support](/azure/aks/hybrid/help-support?tabs=aksee) article for information about how to use the Azure portal to get support or open a support request for AKS Arc.
+To open a support request, see the [Get support](/azure/aks/hybrid/help-support) article for information about how to use the Azure portal to get support or open a support request for AKS Arc.
 
-## Upgrade
+## Known issues
 
-### Azure Advisor upgrade recommendation
+The following sections describe known issues and workarounds for AKS enabled by Azure Arc:
 
-If you continually see an [Azure Advisor](/azure/advisor/) upgrade recommendation that says "Upgrade to the latest version of AKS enabled by Azure Arc," follow these steps to disable the recommendation:
-
-- Ensure that you update your Azure Local solution to the latest version. For more information, see [About updates for Azure Local, version 23H2](/azure-stack/hci/update/about-updates-23h2).
-- If you use any of the Azure SDKs, ensure that you're using the latest version of that SDK. You can find the Azure SDKs by searching for "HybridContainerService" on the [Azure SDK releases](https://azure.github.io/azure-sdk/) page.
+- [Control plane configuration validation errors](control-plane-validation-errors.md)
+- [Connectivity issues with MetalLB](load-balancer-issues.md)
+- [K8sVersionValidation error](cluster-k8s-version.md)
+- [Use diagnostic checker](aks-arc-diagnostic-checker.md)
+- [KubeAPIServer unreachable error](kube-api-server-unreachable.md)
+- [Can't see VM SKUs on Azure portal](check-vm-sku.md)
+- [Deleted AKS Arc cluster still visible on Azure portal](deleted-cluster-visible.md)
+- [Can't fully delete AKS Arc cluster with PodDisruptionBudget (PDB) resources](delete-cluster-pdb.md)
+- [Azure Advisor upgrade recommendation message](azure-advisor-upgrade.md)
+- [Issues after deleting storage volume](delete-storage-volume.md)
 
 ## Next steps
 
-- [Troubleshoot K8sVersionValidation error](cluster-k8s-version.md)
-- [Use diagnostic checker](aks-arc-diagnostic-checker.md)
+[What is AKS enabled by Azure Arc?](aks-overview.md)

AKS-Arc/aks-troubleshoot.md

@@ -0,0 +1,28 @@
+---
+title: Azure Advisor upgrade recommendation
+description: Learn how to disable Azure Advisor upgrade recommendation alerts.
+author: sethmanheim
+ms.author: sethm
+ms.topic: troubleshooting
+ms.date: 02/28/2025
+
+---
+
+# Azure Advisor upgrade recommendation
+
+This article describes how to disable recurring Azure Advisor upgrade recommendation alerts for AKS enabled by Azure Arc.
+
+## Symptoms
+
+You continually see an Azure Advisor upgrade recommendation that says **Upgrade to the latest version of AKS enabled by Azure Arc**.
+
+## Workaround
+
+Follow these steps to disable the recommendation:
+
+- Ensure that you update your Azure Local solution to the latest version. For more information, see [About updates for Azure Local, version 23H2](/azure-stack/hci/update/about-updates-23h2).
+- If you use any of the Azure SDKs, ensure that you're using the latest version of that SDK. You can find the Azure SDKs by searching for "HybridContainerService" on the [Azure SDK releases](https://azure.github.io/azure-sdk/) page.
+
+## Next steps
+
+[Troubleshoot issues in AKS enabled by Azure Arc](aks-troubleshoot.md)

AKS-Arc/azure-advisor-upgrade.md

@@ -1,6 +1,6 @@
 ---
 title: Troubleshoot no VM sizes listed on Azure portal
-description: Learn how to troubleshoot no VM sizes listed on Azure portal when you create an AKS Arc cluster
+description: Learn how to troubleshoot no VM sizes listed on Azure portal when you create an AKS Arc cluster.
 ms.topic: troubleshooting
 author: sethmanheim
 ms.author: sethm
@@ -9,7 +9,7 @@ ms.reviewer: sumsmith
 
 ---
 
-# Troubleshoot no VM sizes listed on Azure portal when you create an AKS Arc cluster
+# No VM sizes listed on Azure portal when you create an AKS Arc cluster
 
 When you try to create an AKS Arc cluster from the Azure portal, you can see that there are no VM sizes listed. This can happen if the **skus/default** resource in Azure is not yet created, or was deleted for some reason. This scenario can happen in Azure Local releases 2408 or older, when the default resource was not created as a part of the Azure Local deployment.
 

AKS-Arc/tsg-check-vm-sku.md renamed to AKS-Arc/check-vm-sku.md

@@ -3,7 +3,7 @@ title: Control plane configuration validation errors
 description: Learn details about each control plane configuration validation error.
 author: sethmanheim
 ms.author: sethm
-ms.topic: concept-article
+ms.topic: troubleshooting
 ms.date: 02/26/2025
 
 ---

AKS-Arc/control-plane-validation-errors.md

@@ -0,0 +1,28 @@
+---
+title: AKS on Azure Local issues after deleting storage volumes
+description: Learn how to mitigate issues after deleting storage volumes.
+author: sethmanheim
+ms.author: sethm
+ms.topic: troubleshooting
+ms.date: 02/28/2025
+
+---
+
+# AKS on Azure Local issues after deleting storage volumes
+
+This article describes how to mitigate cluster issues if a storage volume is deleted.
+
+## Symptoms
+
+AKS Arc workload data is stored on Azure Local storage volumes, including the AKS Arc node disks and persistent volumes of data disks. If the storage volume is accidentally deleted, the AKS Arc cluster doesn't work properly, as its data is removed as well.
+
+## Workaround
+
+To manage storage volumes on Azure Local, follow these steps:
+
+- Ensure that you deleted all the storage path(s) that are created on that storage volume. Deleting storage paths raises an alert to indicate the workload that was stored on it. To delete the storage path, see [Delete a storage path](/azure/azure-local/manage/create-storage-path?view=azloc-24112&preserve-view=true&tabs=azurecli#delete-a-storage-path).
+- If you have an AKS Arc cluster that must be deleted, see [Delete the AKS Arc cluster](aks-create-clusters-cli.md#delete-the-cluster).
+
+## Next steps
+
+[Troubleshoot issues in AKS enabled by Azure Arc](aks-troubleshoot.md)

AKS-Arc/delete-storage-volume.md

@@ -3,7 +3,7 @@ title: Intermittent connectivity issues with MetalLB or Kubernetes services of t
 description: Learn how to mitigate connection issues with MetalLB or Kubernetes services of type Load Balancer.
 author: sethmanheim
 ms.author: sethm
-ms.topic: concept-article
+ms.topic: troubleshooting
 ms.date: 02/26/2025
 
 ---

AKS-Arc/load-balancer-issues.md

@@ -44,6 +44,7 @@
       "breadcrumb_path": "/azure/adaptive-cloud/breadcrumb/toc.json",
       "feedback_system": "Standard",
       "permissioned-type": "public",
+      "manager":"lizross",
       "ms.service": "azure-stack",
       "tittleSuffix": "Azure Adaptive Cloud",
       "feedback_product_url": "https://feedback.azure.com/d365community/forum/5c778dec-0625-ec11-b6e6-000d3a4f0858",

adaptive-cloud/docfx.json

@@ -5,7 +5,7 @@ author: jasongerend
 ms.author: jgerend
 ms.topic: conceptual
 ms.service: azure-local
-ms.date: 04/24/2023
+ms.date: 02/27/2025
 ---
 
 # Azure Stack HCI data collection
@@ -14,20 +14,20 @@ ms.date: 04/24/2023
 
 [!INCLUDE [azure-local-banner-22h2](../includes/azure-local-banner-22h2.md)]
 
-This topic describes required data collected to keep Azure Stack HCI secure, up to date, and working as expected.
+This article describes required data collected to keep Azure Stack HCI secure, up to date, and working as expected.
 
-Customer data, including the names, metadata, configuration, and contents of your on-premises virtual machines (VMs) is never sent to the cloud unless you turn on additional services like Azure Backup or Azure Site Recovery, or unless you enroll those VMs individually into cloud management services like Azure Arc.
+Customer data, including the names, metadata, configuration, and contents of your on-premises virtual machines (VMs) is never sent to the cloud unless you turn on other services like Azure Backup or Azure Site Recovery, or unless you enroll those VMs individually into cloud management services like Azure Arc.
 
-We do collect diagnostic data. The data described below is required for Microsoft to provide Azure Stack HCI. This data is collected once a day, and data collection events can be viewed in the event logs. Azure Stack HCI collects the minimum data required to keep your clusters up to date, secure, and operating properly.
+We do collect diagnostic data. The data described in the following section is required for Microsoft to provide Azure Stack HCI. This data is collected once a day, and data collection events can be viewed in the event logs. Azure Stack HCI collects the minimum data required to keep your clusters up to date, secure, and operating properly.
 
    > [!IMPORTANT]
-   > The data described below that Azure Stack HCI collects is independent from Windows diagnostic data, which can be configured for various levels of collection. In Azure Stack HCI, the default setting for Windows diagnostic data collection is Security (off), meaning that no Windows diagnostic data is sent unless the administrator changes the diagnostic data settings. For more information, see [Configure Windows diagnostic data in your organization](/windows/privacy/configure-windows-diagnostic-data-in-your-organization). Microsoft is an independent controller of any Windows diagnostic data collected in connection with Azure Stack HCI. Microsoft will handle the Windows diagnostic data in accordance with the [Microsoft Privacy Statement](https://privacy.microsoft.com/privacystatement).
+   > The data described below that Azure Stack HCI collects is independent from Windows diagnostic data, which can be configured for various levels of collection. In Azure Stack HCI, the default setting for Windows diagnostic data collection is Security (off), meaning that no Windows diagnostic data is sent unless the administrator changes the diagnostic data settings. For more information, see [Configure Windows diagnostic data in your organization](/windows/privacy/configure-windows-diagnostic-data-in-your-organization). Microsoft is an independent controller of any Windows diagnostic data collected in connection with Azure Stack HCI. Microsoft handles the Windows diagnostic data in accordance with the [Microsoft Privacy Statement](https://privacy.microsoft.com/privacystatement).
 
 ## Data collection and residency
 
 This Azure Stack HCI data:
 
-- is not sent to Microsoft until the product is registered with Azure. When Azure Stack HCI is unregistered, this data collection stops.
+- isn't sent to Microsoft until the product is registered with Azure. When Azure Stack HCI is unregistered, this data collection stops.
 - is logged to the Microsoft-AzureStack-HCI/Analytic event channel.
 - is in JSON format, so that system administrators can examine and analyze the data being sent.
 
@@ -43,14 +43,14 @@ To learn about how Microsoft stores diagnostic data in Azure, see [Data residenc
 
 ## Data retention
 
-After Azure Stack HCI collects this data, it is retained for 90 days. Aggregated, de-identified data may be kept longer.
+After Azure Stack HCI collects this data, it's retained for 90 days. Aggregated, de-identified data may be kept longer.
 
 ## What data is collected?
 
 Azure Stack HCI collects:
 
 - Information about servers such as operating system version, processor model, number of processor cores, memory size, cluster identifier, and hash of hardware ID
-- List of installed Azure Stack HCI server features (e.g. BitLocker)
+- List of installed Azure Stack HCI server features (for example, BitLocker)
 - Information necessary to compute the reliability of the Azure Stack HCI operating system
 - Information necessary to compute the reliability of the health collection data
 - Information gathered from the event log for specific errors, such as update download failed
@@ -97,7 +97,7 @@ Azure Stack HCI collects:
        } 
    }
    ```
- 
+
 The output should look something like this:
 
 ```shell