Azure Migrate — Replication cycle failed with “No disk snapshots were found” (Snapshot ID)
Azure Migrate — Replication cycle failed with “No disk snapshots were found” (Snapshot ID)
Symptoms / Error Seen
During agentless VMware → Azure replication (Azure Migrate: Migration & modernization), the replication cycle failed with the following message in Events:
The last replication cycle for the virtual machine failed.
No disk snapshots were found for the snapshot replication with Snapshot Id: '<GUID>'.
Tip: You can review these messages in Azure portal → Azure Migrate project → Migration & modernization → Replications → select VM → Events.
What Happened in Our Case:
- On VMware, a data disk had been removed from the VM earlier.
- Later, while configuring replication in Azure Migrate, that previously removed disk was still selected under “Included disks.”
- When Azure Migrate attempted the next replication cycle, it couldn’t find a corresponding snapshot/disk for the included (now non‑existent) VMDK, so the cycle aborted with “No disk snapshots were found …”.
Root Cause
A mismatch between disks selected in Azure Migrate and the actual disks attached to the VM in vSphere.
Azure Migrate expected to snapshot & export a disk that no longer existed on the source VM, resulting in “No disk snapshots were found …” and a failed cycle.
Solution (What fixed it)
- Validated current disk layout on vCenter (Edit Settings → confirm which VMDKs are actually attached).
- In Azure Migrate, reinitiated replication (project → Migration & modernization → Replications → select VM → Compute and disks):
- Unselect the disk that had been removed on VMware (so the include list matches the real VM).
- Saved the settings and let the next replication cycle run — status turned healthy and cycles resumed.
Verification
- Portal → Azure Migrate → Replications → VM → Replication health = Health