Prerequisite and Support Matrix – Microsoft Migration Accelerator (for Azure)
This post provides prerequisites and support requirements for using Microsoft Migration Accelerator (for Azure) to migrate your workloads to Azure.
Prerequisite
- Azure Account subscription is required to migrate your source Enterprise servers to Azure. If you do not have Azure Account, get a free trial account.
- Sign Up for MA preview.
- After approval, you will receive an email user name and password for MA portal, with links to documentation.
Support Matrix
Area |
Limits |
| What Operating Systems can I migrate to Azure? |
For more information on Windows Servers roles and features not supported in Azure, refer KB 2721672. |
| What source enterprise platforms are supported? |
Note: Migration of Linux instances from on AWS is not supported |
| OS Disk | The OS disk is limited to 1TB (Azure limit). If you tried to protect size greater than 1023 GB using MA you will get “The VM(s) <your VM name> could not be protected as their system volume is greater than 1023 GB.” Shrinking the OS disk will not resolve the issue because it shrinks the volume not the disk. |
| No. of data disks | Azure limits the number of disks a virtual machine can mount to 16. This limits the number of data disks the MT can support depending the size of the VM. We recommend your MT VM to be of A4 size. With this you will able to support up to 15 data drives per MT. One is reserved by MT for storing Retention Points. If you tried to migrate VMs to single MT with greater than or equal to 15 data disks then you will get "Cannot attach more than disks for MT mtvm." error message. |
| Size of Data disk | Azure limits the size of the data disk to 1 TB. You cannot migrate source VMs with non OS disks great than 1 TB. |
| CPU Cores | Azure has a default limit of 20 cores per subscription. Ensure SUM of CPU Cores for CS, MT and migrated target VMs to be within the default of cores for your subscription. For example, if you want to protect 3 source VMs having 8GB RAM with dual core, then best match on Azure VM for all three VMs is A3 size (4 cores). To create 3 VMs of A3 size you will need 24 cores. For ex: 3 VMs * 4 cores for A3 = 12 cores 1 A3 size VM for CS = 4 cores1 A4 size VM for MT = 8 cores ========== 24 cores If your requirements exceeds 20 cores, then contact support to increase the quota. |
| Network | Azure recently added supports for creating VM with multiple NIC, currently this feature is not supported in MA. Windows NLB is not supported in Windows Azure. |
| Generation 2 VM | Azure doesn’t support Gen 2 VM. As a result the following Gen 2 new functionality is not supported: PXE boot by using a standard network adapter, Boot from a SCSI virtual hard disk, Boot from a SCSI virtual DVD, Secure Boot, and UEFI firmware support. For more information refer, Generation 2 Virtual Machine Overview. |
| Cluster | Azure doesn’t support Cluster. |
| Linux migration Limitations | No support for Distributed Application consistency. Root file system with multiple disks is not supported; however, multiple data disks is supported. Migration of Linux instances from AWS to Azure is not supported. Linux VMs installed on Hyper-V must be discovered as Physical machines. |
Additional Resources:
Migration Accelerator FAQ and Known Issues
Troubleshooting Migration Accelerator Deployment
Comments
- Anonymous
January 01, 2003
I take it VHDX disks are not supported as well.. - Anonymous
September 18, 2014
Microsoft Migration Accelerator (MA) provides the ability to migrate workloads running in your enterprise - Anonymous
January 19, 2015
The comment has been removed - Anonymous
August 12, 2015
Do you support UEFI boot type? - Anonymous
December 10, 2015
When will you support Red Hat workload migration?