I'm trying to migrate on-premises VMware virtual machines to Azure with Azure Migrate, but the migration workflow reports: "The virtual machine is running under a VMware fabric which isn't configured for migration."
Microsoft support hasn't been able to identify the cause. So far, I've confirmed that vMotion is enabled, the Azure account has Owner access to the resource group containing the Azure Migrate project and appliance, the vSphere account has full administrative access to the VM, and the appliance can discover the complete VMware inventory. Connectivity from the appliance to Azure also shows as healthy.
Has anyone encountered this error or figured out what Azure Migrate means by an unconfigured VMware fabric?
2 Answers
That message usually means Azure Migrate has discovered the VM but hasn’t associated it with a properly configured VMware fabric. I’d check the project’s VMware fabric and the VM-to-fabric mapping first, rather than focusing only on permissions or vMotion.
We had poor results with agentless replication. VMware consolidation activity kept interfering with replication and eventually corrupted the replicated data. Switching to agent-based replication was much more reliable. In Azure Migrate, configure the project for migrating physical or other servers and use the agent-based workflow for the VMware machines.
Microsoft support told me the agent-based approach probably wouldn’t change anything, but this sounds different enough that I’m going to test it anyway.
What specifically should I verify in the mapping? The appliance can see the VM, but I’m not sure where Azure Migrate shows whether it has been associated with the fabric.