Sync release-local-2506 with main

Sync release-local-2506 with main

Author: sethmanheim

azure-local/TOC.yml

@@ -186,17 +186,21 @@ items:
   items:
   - name: About Azure Local upgrades
     href: upgrade/about-upgrades-23h2.md
-  - name: 1. Upgrade to version 23H2 OS
+  - name: 1. Select upgrade path
     items: 
-    - name: Via PowerShell (recommended)
-      href: upgrade/upgrade-22h2-to-23h2-powershell.md
-    - name: Via Windows Admin Center
-      href: upgrade/upgrade-22h2-to-23h2-windows-admin-center.md
-    - name: Via other methods
-      href: upgrade/upgrade-22h2-to-23h2-other-methods.md
+    - name: Upgrade to 26100.xxxx
+      href: upgrade/upgrade-to-24h2-powershell.md
+    - name: Upgrade to 25398.xxxx
+      items: 
+      - name: Via PowerShell (recommended)
+        href: upgrade/upgrade-22h2-to-23h2-powershell.md
+      - name: Via Windows Admin Center
+        href: upgrade/upgrade-22h2-to-23h2-windows-admin-center.md
+      - name: Via other methods
+        href: upgrade/upgrade-22h2-to-23h2-other-methods.md
   - name: 2. Perform post-OS upgrade tasks
     href: upgrade/post-upgrade-steps.md
-  - name: 3. Install, enable Network ATC
+  - name: 3. Configure Network ATC
     href: upgrade/install-enable-network-atc.md
   - name: 4. Validate solution upgrade readiness
     href: upgrade/validate-solution-upgrade-readiness.md

azure-local/includes/azure-local-verify-update.md

@@ -6,33 +6,57 @@ ms.topic: include
 ms.date: 05/13/2024
 ---
 
-## Step 3: Check the status of an update
-
-To get the summary information about an update in progress, run the `Get-CauRun` cmdlet:
-
-```PowerShell
-Get-CauRun -ClusterName <SystemName>
-```
-
-Here's a sample output: <!--ASK-->
-
-```output
-RunId                   : <Run ID> 
-RunStartTime            : 10/13/2024 1:35:39 PM 
-CurrentOrchestrator     : NODE1 
-NodeStatusNotifications : { 
-Node      : NODE1 
-Status    : Waiting 
-Timestamp : 10/13/2024 1:35:49 PM 
-} 
-NodeResults             : { 
-Node                     : NODE2 
-Status                   : Succeeded 
-ErrorRecordData          : 
-NumberOfSucceededUpdates : 0 
-NumberOfFailedUpdates    : 0 
-InstallResults           : Microsoft.ClusterAwareUpdating.UpdateInstallResult[] 
-}
-```
+1. To get the summary information about an update in progress, run the `Get-CauRun` cmdlet:
+
+    ```PowerShell
+    Get-CauRun -ClusterName <SystemName>
+    ```
+
+    Here's a sample output: <!--ASK-->
+
+    ```output
+    RunId                   : <Run ID> 
+    RunStartTime            : 10/13/2024 1:35:39 PM 
+    CurrentOrchestrator     : NODE1 
+    NodeStatusNotifications : { 
+    Node      : NODE1 
+    Status    : Waiting 
+    Timestamp : 10/13/2024 1:35:49 PM 
+    } 
+    NodeResults             : { 
+    Node                     : NODE2 
+    Status                   : Succeeded 
+    ErrorRecordData          : 
+    NumberOfSucceededUpdates : 0 
+    NumberOfFailedUpdates    : 0 
+    InstallResults           : Microsoft.ClusterAwareUpdating.UpdateInstallResult[] 
+    }
+    ```
+
+1. Validate the health of your system by running the `Test-Cluster` cmdlet on one of the machines in the system. If any of the condition checks fail, resolve them before proceeding to the next step.
+
+    ```powershell
+    Test-Cluster
+    ```
+
+1. Verify that the registry keys are still applied on each machine in the system before moving to the next step.
+
+    To check if the registry key exists:
+   
+    ```powershell
+    Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" -Name "RefsEnableMetadataValidation" 
+    ```
+   
+    To reapply the registry keys if needed and reboot each machine for the changes to take effect:
+
+    ```powershell
+    Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" -Name "RefsEnableMetadataValidation" -Value 0 -Type DWord  -ErrorAction Stop
+    ```
+
+    If the OS upgrade fails, run the following command to recover the CAU run:
+
+    ```powershell
+    Invoke-CauRun –ForceRecovery -Force
+    ```
 
 You're now ready to perform the post-OS upgrade steps for your system.

azure-local/manage/manage-arc-virtual-machine-resources.md

@@ -5,7 +5,7 @@ author: alkohli
 ms.author: alkohli
 ms.topic: how-to
 ms.service: azure-local
-ms.date: 03/18/2025
+ms.date: 06/06/2025
 ---
 
 # Manage resources for Azure Local VMs enabled by Azure Arc
@@ -78,6 +78,7 @@ You can expand an existing data disk to your desired size using Azure CLI.
 
 >[!NOTE]
 >
+>- This feature is available only in Azure Local version 2504 and later.
 >- The size you're changing the data disk to can't be the same or less than the original size of the data disk.
 >- The maximum size the disk can expand to depends on the storage capacity of the cluster. Hyper-V also imposes a VHD max of 2TB and VHDx max of 64TB.
 

azure-local/migrate/media/migrate-troubleshoot/after-vm-creation.png

@@ -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: 05/14/2025
+ms.date: 06/04/2025
 ms.author: alkohli
 ms.reviewer: alkohli
 ms.custom: linux-related-content
@@ -375,6 +375,49 @@ Complete the following steps:
 1. Verify that the intended IP address isn't currently assigned to another network interface.
 1. Update the logical network configuration as needed to ensure no IP conflicts exist before retrying the migration.
 
+### Clean up resources from failed migrations
+
+**Root cause**
+
+In some cases, migrations to Azure Local may fail during the migration phase, such as during planned failover, not during initial replication. When this occurs, manual cleanup of partially created resources may be required to ensure future migration attempts are successful.
+
+**Recommended resolution**
+
+To determine where the failure occurred, open the Planned failover job in the Azure Migrate portal. Use the job details to identify whether the failure occurred before or after VM creation on the Azure Local instance.
+
+*If the failure occurred before VM creation*
+
+Task failures listed above the red line (above the **Preparing protected entities** task) indicate that no target VM was created. No cleanup is required and you can retry migration directly.
+
+:::image type="content" source="./media/migrate-troubleshoot/before-vm-creation.png" alt-text="Screenshot of Planned failover page before creation." lightbox="./media/migrate-troubleshoot/before-vm-creation.png":::
+
+*If the failure occurred during or after VM creation*
+
+Task failures listed below the red line (**Preparing protected entities** task and below) indicate that a target VM was partially or fully created. Manual cleanup is required before retrying migration.
+
+:::image type="content" source="./media/migrate-troubleshoot/after-vm-creation.png" alt-text="Screenshot of Planned failover page after creation." lightbox="./media/migrate-troubleshoot/after-vm-creation.png":::
+
+1. In Azure portal, navigate to the target Azure Local instance.
+
+1. Locate and verify if a VM corresponding to the failed migration exists.
+
+1. If found, delete the VM from the portal.
+
+    :::image type="content" source="./media/migrate-troubleshoot/delete-vm.png" alt-text="Screenshot showing Delete button for selected virtual machine." lightbox="./media/migrate-troubleshoot/delete-vm.png":::
+
+1. Connect to the Azure Local instance directly (via Hyper-V Manager) and confirm that the associated VM was also removed from the local Hyper-V host. If it wasn't removed, manually delete the VM resource.
+
+1. Don't delete any of the following resources that may have been created:
+
+    - Migrated (target) disk.
+
+    - Seed disk.
+
+    - Network interfaces.
+
+    These resources will be reused automatically by Azure Migrate during subsequent migration attempts.
+
+
 ## Next steps
 
 Depending upon the phase of migration you are in, you may need to review one of the following articles to troubleshoot issues: