Merge pull request #3769 from MicrosoftDocs/main638895098027604136sync_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]

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/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