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

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: