Support matrix for Hyper-V migration
This article summarizes support settings and limitations for migrating Hyper-V VMs with Azure Migrate: Server Migration . If you're looking for information about assessing Hyper-V VMs for migration to Azure, review the assessment support matrix.
You can select up to 10 VMs at once for replication. If you want to migrate more machines, replicate in groups of 10.
|Deployment||The Hyper-V host can be standalone or deployed in a cluster.
Azure Migrate replication software (Hyper-V Replication provider) needs to be installed on the Hyper-V hosts.
|Permissions||You need administrator permissions on the Hyper-V host.|
|Host operating system||Windows Server 2019, Windows Server 2016, or Windows Server 2012 R2.|
|URL access||The replication provider software on the Hyper-V hosts will need access to these URLS:
- login.microsoftonline.com: Access control and identity management using Active Directory.
- *.backup.windowsazure.com: Replication data transfer and coordination. Migrate service URLs.
- *.blob.core.windows.net: Upload data to storage accounts.
- dc.services.visualstudio.com: Upload app logs used for internal monitoring.
- time.windows.com: Verifies time synchronization between system and global time.
|Port access||Outbound connections on HTTPS port 443 to send VM replication data.|
|Operating system||All Windows and Linux operating systems that are supported by Azure.|
|Required changes for Azure||Some VMs might require changes so that they can run in Azure. You need to make adjustments manually before migration. The relevant articles contain instructions about how to do this.|
|Linux boot||If /boot is on a dedicated partition, it should reside on the OS disk, and not be spread across multiple disks.
If /boot is part of the root (/) partition, then the ‘/’ partition should be on the OS disk, and not span other disks.
|UEFI boot||The migrated VM in Azure will be automatically converted to a BIOS boot VM. The VM should be running Windows Server 2012 and later only. The OS disk should have up to five partitions or fewer and the size of OS disk should be less than 300 GB.|
|Disk size||2 TB for the OS disk, 4 TB for data disks.|
|Disk number||A maximum of 16 disks per VM.|
|Encrypted disks/volumes||Not supported for migration.|
|RDM/passthrough disks||Not supported for migration.|
|Shared disk||VMs using shared disks aren't supported for migration.|
|NFS||NFS volumes mounted as volumes on the VMs won't be replicated.|
|ISCSI||VMs with iSCSI targets aren't supported for migration.|
|Target disk||You can migrate to Azure VMs with managed disks only.|
|NIC teaming||Not supported.|
|Azure Site Recovery||You can't replicate using Azure Migrate Server Migration if the VM is enabled for replication with Azure Site Recovery.|
|Ports||Outbound connections on HTTPS port 443 to send VM replication data.|
Azure VM requirements
All on-premises VMs replicated to Azure must meet the Azure VM requirements summarized in this table.
|Operating system disk size||Up to 2,048 GB.||Check fails if unsupported.|
|Operating system disk count||1||Check fails if unsupported.|
|Data disk count||16 or less.||Check fails if unsupported.|
|Data disk size||Up to 4,095 GB||Check fails if unsupported.|
|Network adapters||Multiple adapters are supported.|
|Shared VHD||Not supported.||Check fails if unsupported.|
|FC disk||Not supported.||Check fails if unsupported.|
|BitLocker||Not supported.||BitLocker must be disabled before you enable replication for a machine.|
|VM name||From 1 to 63 characters.
Restricted to letters, numbers, and hyphens.
The machine name must start and end with a letter or number.
|Update the value in the machine properties in Site Recovery.|
|Connect after migration-Windows||To connect to Azure VMs running Windows after migration:
- Before migration enables RDP on the on-premises VM. Make sure that TCP, and UDP rules are added for the Public profile, and that RDP is allowed in Windows Firewall > Allowed Apps, for all profiles.
For site-to-site VPN access, enable RDP and allow RDP in Windows Firewall -> Allowed apps and features for Domain and Private networks. In addition, check that the operating system's SAN policy is set to OnlineAll. Learn more.
|Connect after migration-Linux||To connect to Azure VMs after migration using SSH:
Before migration, on the on-premises machine, check that the Secure Shell service is set to Start, and that firewall rules allow an SSH connection.
After failover, on the Azure VM, allow incoming connections to the SSH port for the network security group rules on the failed over VM, and for the Azure subnet to which it's connected. In addition, add a public IP address for the VM.
Migrate Hyper-V VMs for migration.