Migration software

Azure Migrate

Suggested in 2 of our migration playbooks, mainly for Servers and cloud. Here is what it handles, how it treats key settings, and other tools for the same jobs.

Platform toolBy Microsoft2 playbooks6 limits handled

What does Azure Migrate handle?

The limits of the built-in tools that Azure Migrate gets around, as covered in our playbooks.

Azure migration

  • Check disks before choosing a replication methodMicrosoft lists independent disks, passthrough disks and iSCSI targets as supported. Needs a replication appliance and the Mobility service on each VM.
  • Azure Migrate agentless replication (VMware) does not copy RDM, passthrough or independent disks, or in-guest iSCSI targets.Supports independent disks, passthrough disks and iSCSI targets. Needs a replication appliance and the Mobility service on each VM.

VMware to Azure migration with Azure Migrate

  • Batch replications in groups of 10Get-AzMigrateDiscoveredServer lists every discovered VM and New-AzMigrateServerReplication starts each one; Microsoft says up to 500 replications can run at once. You write the loop yourself.
  • Find RDM, independent and iSCSI disks before you choose agentlessMicrosoft lists independent disks, passthrough disks and iSCSI targets as supported for agent-based migration. Needs the replication appliance and the Mobility service on each VM.
  • Agentless replication does not copy RDM (raw device) or passthrough disks, and does not support independent disks or iSCSI targets.Supports independent disks, passthrough disks and iSCSI targets. Needs the replication appliance and the Mobility service on each VM.
  • The Azure Migrate portal lets you select only 10 machines at a time for replication.Starts replication for a whole wave from one script. Up to 500 replications can run at once. You write the loop yourself.

How does Azure Migrate handle key settings?

From the settings checklists in our playbooks: what Azure Migrate carries across.

SettingHow it handles itPlaybook
Disks Azure Migrate cannot copySupports independent disks, passthrough disks and iSCSI targets, up to 63 disks per VM. Needs a replication appliance and the Mobility service on each VM.Azure migration
Disk sizes and typesSame OS and data disk size limits, up to 63 disks per VM, onto Standard HDD, Standard SSD or Premium SSD managed disks.VMware to Azure migration with Azure Migrate
Disks agentless cannot copySupports independent disks, passthrough disks and iSCSI targets. Needs the replication appliance and the Mobility service on each VM.VMware to Azure migration with Azure Migrate
VMware snapshots and backup jobsWhether existing snapshots affect it: not stated in Microsoft's documentation: test it in your pilot.VMware to Azure migration with Azure Migrate
Boot type, Secure Boot and virtual TPMUEFI VMs become Generation 2 VMs. Secure Boot is not supported for migration.VMware to Azure migration with Azure Migrate
Drivers and changes made to the guestNeeds the Mobility service installed in each VM. Which guest changes it makes: not stated in Microsoft's support matrix: test it in your pilot.VMware to Azure migration with Azure Migrate
VMware Tools and the Azure VM agentNot stated in Microsoft's documentation: test it in your pilot.VMware to Azure migration with Azure Migrate
IP addresses, network adapters and DNSTeamed network cards and IPv6 are not supported.VMware to Azure migration with Azure Migrate
Windows Server licensingWhether it offers the same choice: not stated in Microsoft's support matrix: check it when you start replication.VMware to Azure migration with Azure Migrate
How many at once and appliance healthStarts replication for a whole wave from one script. Up to 500 replications can run at once. You write the loop yourself.VMware to Azure migration with Azure Migrate
Replication cycles, test migration and cutoverReplication timing: not stated in Microsoft's support matrix: test it in your pilot.VMware to Azure migration with Azure Migrate

Which tools do the same jobs as Azure Migrate?

Other tools our playbooks suggest for the same migrations.

We write these notes from the vendor documentation cited in each playbook. Tools cannot pay to be included or to change them. Check the vendor's current documentation and terms before you buy.