Sync release-local-disconnectednew with main

Sync release-local-disconnectednew with main

Author: sethmanheim

AKS-Arc/aks-vmware-quickstart-deploy.md

@@ -5,7 +5,7 @@ author: sethmanheim
 ms.author: sethm
 ms.topic: quickstart
 ms.custom: devx-track-azurecli
-ms.date: 03/19/2025
+ms.date: 06/13/2025
 ms.lastreviewed: 03/19/2025
 ms.reviewer: leslielin
 ---
@@ -94,8 +94,8 @@ Run the following command to create the cluster.
 az aksarc create -n '<name of your cluster>' -g $resource_group --kubernetes-version '<Kubernetes version from the Arc Resource Bridge>' --custom-location $custom_location --aad-admin-group-object-ids $aad_group_id --vnet-ids $vnet_id --control-plane-ip $control_plane_ip --generate-ssh-keys --debug
 ```
 
-   > [!NOTE]
-   > In this preview release, you can only deploy the same Kubernetes version that the Arc Resource Bridge supports. The Kubernetes version you provide in the command must align with the Arc Resource Bridge version. You can find the Arc Resource Bridge version in the Azure portal under **Azure Arc > Management > Resource Bridge**. To determine the corresponding Kubernetes version, see [What's new with Azure Arc resource bridge](/azure/azure-arc/resource-bridge/release-notes).
+> [!NOTE]
+> In this preview release, you can only deploy the same Kubernetes version that the Arc Resource Bridge supports. Currently, this preview only supports Arc Resource Bridge version 1.2.0 and earlier. The Kubernetes version you provide in the command must align with the Arc Resource Bridge version. You can find the Arc Resource Bridge version in the Azure portal under **Azure Arc > Management > Resource Bridge**. To determine the corresponding Kubernetes version, see [What's new with Azure Arc resource bridge](/azure/azure-arc/resource-bridge/release-notes#version-120-july-2024).
 
 ## Delete the cluster
 

AKS-Arc/aks-vmware-system-requirements.md

@@ -1,12 +1,12 @@
 ---
 title: System requirements and support matrix for AKS enabled by Azure Arc on VMware (preview)
 description: Learn about system requirements and the support matrix for AKS enabled by Azure Arc on VMware.
-ms.date: 09/16/2024
-ms.topic: article
+ms.date: 06/13/2025
+ms.topic: concept-article
 author: sethmanheim
 ms.author: sethm
 ms.reviewer: leslielin
-ms.lastreviewed: 09/16/2024
+ms.lastreviewed: 06/13/2025
 
 ms.custom: references_regions
 
@@ -70,7 +70,7 @@ You should create a folder for VM templates, to store the Arc Resource Bridge an
 
 ## Supported Kubernetes version
 
-In this preview release, you can only deploy the same Kubernetes version that the Arc Resource Bridge supports. You can find the Arc Resource Bridge version in the Azure portal under **Azure Arc > Management > Resource Bridge**. To determine the corresponding Kubernetes version, see [What's new with Azure Arc resource bridge](/azure/azure-arc/resource-bridge/release-notes).
+In this preview release, you can only deploy the Kubernetes version that matches what Arc Resource Bridge supports. Currently, this preview only supports Arc Resource Bridge version 1.2.0 and earlier. You can find the Arc Resource Bridge version in the Azure portal under **Azure Arc > Management > Resource Bridge**. To determine the corresponding Kubernetes version, see [What's new with Azure Arc resource bridge](/azure/azure-arc/resource-bridge/release-notes#version-120-july-2024).
 
 ## Custom location
 

azure-local/manage/health-service-settings.md

@@ -4,7 +4,7 @@ title: Modify Health Service settings
 ms.author: alkohli
 ms.topic: how-to
 author: alkohli
-ms.date: 01/16/2025
+ms.date: 07/28/2025
 ---
 
 # Modify Health Service settings
@@ -15,6 +15,8 @@ The Health Service, first released in Windows Server 2016, improves the day-to-d
 
 Many of the parameters which govern the behavior of the Health Service are exposed as settings. You can modify these to tune the aggressiveness of faults or actions, turn certain behaviors on/off, and more.
 
+For a detailed overview of health faults, including fault severity mappings, health settings (data types, fault associations, default values, and descriptions), and the list of collected metrics, download the [Health Service faults](https://github.com/Azure-Samples/AzureLocal/blob/main/health-service-faults/health-service-faults.xlsx) spreadsheet.
+
 Use the following PowerShell cmdlet to set or modify settings.
 
 ## Usage

azure-local/migrate/migrate-troubleshoot.md

@@ -3,7 +3,7 @@ title: Troubleshoot issues when migrating VMs to Azure Local using Azure Migrate
 description: Learn about how to troubleshoot issues when migrating Windows VMs to your Azure Local instance using Azure Migrate (preview).
 author: alkohli
 ms.topic: how-to
-ms.date: 06/04/2025
+ms.date: 07/10/2025
 ms.author: alkohli
 ms.reviewer: alkohli
 ms.custom: linux-related-content
@@ -417,6 +417,21 @@ Task failures listed below the red line (**Preparing protected entities** task a
 
     These resources will be reused automatically by Azure Migrate during subsequent migration attempts.
 
+### Migrated VM data disks show as 1GB in Azure Portal
+
+When you migrate a VM with one or more data disks attached, Azure Portal may incorrectly display the total data disk size as **1 GB**.
+
+**Root cause**
+
+This is a display issue only and doesn't affect the actual functionality or size of the VM's data disks.
+
+
+**Recommended resolution**
+
+To correct the display issue in Azure portal and reflect the true data disk size, follow the steps at [Expand a data disk](../manage/manage-arc-virtual-machine-resources.md?&tabs=azurecli#expand-a-data-disk) to reapply the same size as the current data disk (no actual size increase is required).
+
+This triggers a portal refresh and updates the UX to reflect the correct data disk size.
+
 
 ## Next steps
 

azure-local/migrate/migration-options-overview.md

@@ -1,64 +1,46 @@
 ---
 title: Options for migrating virtual machines to Azure Local (preview)
-description: Learn about how to choose a migration option to migrate VM workloads to your Azure Local (preview).
+description: Learn about the available migration options for migrating VM workloads to your Azure Local (preview).
 author: alkohli
 ms.topic: overview
-ms.date: 05/15/2025
+ms.date: 07/28/2025
 ms.author: alkohli
 ms.reviewer: alkohli
 ---
 
-# About options to migrate VM workloads to Azure Local (preview)
+# Options to migrate VM workloads to Azure Local (preview)
 
 [!INCLUDE [applies-to](../includes/hci-applies-to-23h2.md)]
 
 [!INCLUDE [azure-local-banner-23h2](../includes/azure-local-banner-23h2.md)]
 
-This article provides an overview of some of the common options available for migrating virtual machine (VM) workloads to your Azure Local instance.
+This article provides an overview of the options available for migrating virtual machine (VM) workloads to your Azure Local instance.
 
 [!INCLUDE [important](../includes/hci-preview.md)]
 
-
 ## Migration options
 
-To migrate VM workloads and their data to your Azure Local instance, several options are available. These options can be classified as first party, third party, and manual migration options. Each of these options is described in the following sections.
+To migrate VM workloads and their data to your Azure Local instance, several options are available. These options are classified either as first-party or third-party. Select the option that best suits your current infrastructure and migration goals.
 
-## First party migration options
+## First-party migration options
 
-First party migration options are provided by Microsoft. These options are built into the Azure Local platform and are available to you at no additional cost. The following first party migration options are available:
+First-party migration options are provided by Microsoft. These options are built into the Azure Local platform and are available to you at no additional cost.
 
-- [Azure Migrate](./migration-azure-migrate-overview.md). This option is only available on systems running Azure Local.
-    - [For Hyper-V VMs](./migration-azure-migrate-overview.md).
-    - [For VMware VMs](./migration-azure-migrate-vmware-overview.md).
+The primary first-party migration option is [Azure Migrate](./migration-azure-migrate-overview.md), which is available on systems running Azure Local. Azure Migrate is a central hub for tools to discover, assess, and migrate on-premises servers, apps, and data to the Microsoft Azure cloud.
 
-- System Center Virtual Machine Manager (SCVMM). These options are only available on systems running Azure Stack HCI, version 22H2.
-    - [For Hyper-V VMs](/system-center/vmm/deploy-manage-azure-stack-hci?view=sc-vmm-2022&preserve-view=true#step-8-migrate-vms-from-windows-server-to-azure-stack-hci-cluster)
-    - [For VMware VMs](/system-center/vmm/deploy-manage-azure-stack-hci?view=sc-vmm-2022&preserve-view=true#step-9-migrate-vmware-workloads-to-azure-stack-hci-cluster-using-scvmm)
+You can use Azure Migrate to migrate the following types of VMs to Azure Local:
 
+   - [Hyper-V VMs](./migration-azure-migrate-overview.md)
+   - [VMware VMs](./migration-azure-migrate-vmware-overview.md)
 
-## Third party migration options
+## Third-party migration options
 
 The following third-party migration options are offered by Microsoft partners.
 
 - [Carbonite](https://www.carbonite.com/business/products/migration/)  
 - [Commvault](https://www.commvault.com/)  
 - [Veeam](https://www.veeam.com/)  
 
-
-## Manual migration options
-
-Manual migration options are provided by Microsoft. These options are available to you at no additional cost. These options are available only on systems running Azure Stack HCI, version 22H2.
-
-The following manual migration options are available:
-
-- [Migrate VMs manually to same hardware](migrate-cluster-same-hardware.md): This option is used when you want to migrate a Windows Server failover cluster to Azure Local using your existing hardware. This process installs the new operating system for Azure Local and retains your existing cluster settings and storage, and imports your VMs.
-
-- [Migrate VMs manually to new hardware](migrate-cluster-new-hardware.md): This option is used when you want to migrate VMs from an existing Windows Server 2016 or later cluster to a new Azure Local instance. You migrate the VMs to the same hardware using PowerShell and Robocopy.
-
-    If you have VMs on Windows 2012 R2 or older that you want to migrate, see [Migrating older VMs](migrate-cluster-new-hardware.md#migrating-older-vms).
-
-
-
 ## Next steps
 
 To learn more about migration using Azure Migrate, see:

azure-local/upgrade/troubleshoot-upgrade-to-23h2.md

@@ -3,7 +3,7 @@ title: Troubleshoot Azure Local upgrade
 description: Learn how to troubleshoot upgrades on your Azure Local. 
 author: alkohli
 ms.topic: how-to
-ms.date: 02/28/2025
+ms.date: 05/28/2025
 ms.author: alkohli
 ms.reviewer: alkohli
 ms.service: azure-local
@@ -153,9 +153,10 @@ When you [Install the solution upgrade](./install-solution-upgrade.md), you may
 
 ## Next steps
 
-For detailed remediation for common known issues, check out:
-> [!div class="nextstepaction"]
-> [Azure Local Supportability repository](https://github.com/Azure/AzureStackHCI-Supportability)
+- For detailed remediation for common known issues, check out:
+    > [!div class="nextstepaction"]
+    > [Azure Local Supportability repository](https://github.com/Azure/AzureStackHCI-Supportability)
 
-Alternatively, you can:
-- [Open a Support ticket](../manage/get-support.md)
+- For a detailed overview of health faults, including fault severity mappings, health settings (data types, fault associations, default values, and descriptions), and the list of collected metrics, download the [Health Service faults](https://github.com/Azure-Samples/AzureLocal/blob/main/health-service-faults/health-service-faults.xlsx) spreadsheet.
+
+- [Open a Support ticket](../manage/get-support.md) if you need more help.

azure-stack/ruggedized/operator/azure-stack-commvault-offer-tzl.md

@@ -38,7 +38,7 @@ You can deploy Commvault on an external machine and protect resources on Azure S
 
 ## Deploy from Azure Stack Hub Marketplace
 
-Commvault publishes a BYOL image in the Azure Marketplace and enables the image for syndication to Azure Stack Hub. The minimum version required to back up VMs on Azure Stack is SP16. If you plan to use a virtual appliance, make sure to update to at SP16 (the latest [long-term supported release](https://documentation.commvault.com/2023e/essential/platform_release_schedule_and_lifecycles.html)) or SP17 (the latest mainstream release available).
+Commvault publishes a BYOL image in the Azure Marketplace and enables the image for syndication to Azure Stack Hub. The minimum version required to back up VMs on Azure Stack is SP16. If you plan to use a virtual appliance, make sure to update to at SP16 (the latest [long-term supported release](https://www.cdw.com/content/cdw/en/brand/commvault.html)) or SP17 (the latest mainstream release available).
 
 | Cloud        | Version | Available for syndication | Next update |
 |--------------|---------|---------------------------|-------------|