A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
Azure Migrate: Migration list not updating after restarting replication — Possible stale migration record
FYI, this was created by Microsoft AI from a support ticket I opened. What is going on with Microsoft Support? I still need help with this issue BTW:
Problem description
I am experiencing an issue with Azure Migrate where, after stopping and restarting replication for my VMware virtual machines following a rollback to vCenter, the affected machines do not appear in the migration list. The most recent migration attempt shows as completed successfully in the portal, but the machines are missing from the migration view, and no delta sync activity is observed. I have deleted the Azure VMs, disks, and NICs manually to perform a fresh sync from vCenter prior to starting the replication, but the problem persists.
Environment
Azure Migrate project for migrating five VMware VMs discovered via vCenter.
What I've already tried
I previously completed a migration cycle for these machines, rolled back to vCenter, and then initiated a new migration for the same VMs. The new jobs report success, but the machines do not appear in the migration list. I also verified that replication was stopped before deleting the Azure VM resources. I have reviewed self-help guidance suggesting stopping/disabling and re-enabling migration, but no further diagnostic logs or error messages have been captured.
Current status
I am seeking guidance to restart fresh migrations of the affected VMs