Azure Migrate support matrix
You can use the Azure Migrate service to assess and migrate servers to the Microsoft Azure cloud. This article summarizes general support settings and limitations for Azure Migrate scenarios and deployments.
Supported assessment/migration scenarios
The table summarizes supported discovery, assessment, and migration scenarios.
|Discovery||You can discover server metadata, and dynamic performance data.|
|Software inventory||You can discover apps, roles, and features running on VMware VMs. Currently this feature is limited to discovery only. Assessment is currently at the server level. We don't yet offer app, role, or feature-based assessments.|
|Assessment||Assess on-premises workloads and data running on VMware VMs, Hyper-V VMs, and physical servers. Assess using Azure Migrate: Discovery and assessment, Microsoft Data Migration Assistant (DMA), as well as other tools and ISV offerings.|
|Migration||Migrate workloads and data running on physical servers, VMware VMs, Hyper-V VMs, physical servers, and cloud-based VMS to Azure. Migrate using Azure Migrate: Server Migration and Azure Database Migration Service (DMS), and well as other tools and ISV offerings.|
Currently, ISV tools can't send data to Azure Migrate in Azure Government. You can use integrated Microsoft tools, or use partner tools independently.
Specific tool support is summarized in the table.
|Azure Migrate: Discovery and assessment||Assess VMware VMs, Hyper-V VMs, and physical servers.||Not available (N/A)|
|Azure Migrate: Server Migration||N/A||Migrate VMware VMs, Hyper-V VMs, and physical servers.|
|Carbonite||N/A||Migrate VMware VMs, Hyper-V VMs, physical servers, and other cloud workloads.|
|Cloudamize||Assess VMware VMs, Hyper-V VMs, physical servers, and other cloud workloads.||N/A|
|Corent Technology||Assess VMware VMs, Hyper-V VMs, physical server sand other cloud workloads.||Migrate VMware VMs, Hyper-V VMs, physical servers, public cloud workloads.|
|Device 42||Assess VMware VMs, Hyper-V VMs, physical servers, and other cloud workloads.||N/A|
|DMA||Assess SQL Server databases.||N/A|
|DMS||N/A||Migrate SQL Server, Oracle, MySQL, PostgreSQL, MongoDB.|
|Lakeside||Assess virtual desktop infrastructure (VDI)||N/A|
|Movere||Assess VMware VMs, Hyper-V VMs, Xen VMs, physical servers, workstations (including VDI) and other cloud workloads.||N/A|
|RackWare||N/A||Migrate VMware VMs, Hyper-V VMs, Xen VMs, KVM VMs, physical servers, and other cloud workloads|
|Turbonomic||Assess VMware VMs, Hyper-V VMs, physical servers, and other cloud workloads.||N/A|
|UnifyCloud||Assess VMware VMs, Hyper-V VMs, physical servers and other cloud workloads, and SQL Server databases.||N/A|
|Webapp Migration Assistant||Assess web apps||Migrate web apps.|
|Zerto||N/A||Migrate VMware VMs, Hyper-V VMs, physical servers, and other cloud workloads.|
|Subscription||Can have multiple projects within a subscription.|
|Azure permissions||Users need Contributor or Owner permissions in the subscription to create a project.|
|VMware VMs||Assess up to 35,000 VMware VMs in a single project.|
|Hyper-V VMs||Assess up to 35,000 Hyper-V VMs in a single project.|
A project can include both VMware VMs and Hyper-V VMs, up to the assessment limits.
For Azure Migrate to work with Azure you need these permissions before you start assessing and migrating servers.
|Create a project||Your Azure account needs permissions to create a project.||Set up for VMware, Hyper-V, or physical servers.|
|Register the Azure Migrate appliance||Azure Migrate uses a lightweight Azure Migrate appliance to discover and assess servers with Azure Migrate: Discovery and assessment, and to run agentless migration of VMware VMs with Azure Migrate: Server Migration. This appliance discovers servers, and sends metadata and performance data to Azure Migrate.
During registration, register providers (Microsoft.OffAzure, Microsoft.Migrate, and Microsoft.KeyVault) are registered with the subscription chosen in the appliance, so that the subscription works with the resource provider. To register, you need Contributor or Owner access on the subscription.
VMware-During onboarding, Azure Migrate creates two Azure Active Directory (Azure AD) apps. The first app communicates between the appliance agents and the Azure Migrate service. The app doesn't have permissions to make Azure resource management calls or have Azure RBAC access for resources. The second app accesses an Azure Key Vault created in the user subscription for agentless VMware migration only. In agentless migration, Azure Migrate creates a Key Vault to manage access keys to the replication storage account in your subscription. It has Azure RBAC access on the Azure Key Vault (in the customer tenant) when discovery is initiated from the appliance.
Hyper-V-During onboarding. Azure Migrate creates one Azure AD app. The app communicates between the appliance agents and the Azure Migrate service. The app doesn't have permissions to make Azure resource management calls or have Azure RBAC access for resources.
|Set up for VMware, Hyper-V, or physical servers.|
|Create a key vault for VMware agentless migration||To migrate VMware VMs with agentless Azure Migrate: Server Migration, Azure Migrate creates a Key Vault to manage access keys to the replication storage account in your subscription. To create the vault, you set permissions (Owner, or Contributor and User Access Administrator) on the resource group where the project resides.||Set up permissions.|
Supported geographies (Public cloud)
You can create a project in many geographies in the public cloud.
- Although you can only create projects in these geographies, you can assess or migrate servers for other target locations.
- The project geography is only used to store the discovered metadata.
- When you create a project, you select a geography. The project and related resources are created in one of the regions in the geography. The region is allocated by the Azure Migrate service.
|Geography||Metadata storage location|
|Africa||South Africa or North Africa|
|Asia Pacific||East Asia or Southeast Asia|
|Australia||Australia East or Australia Southeast|
|Canada||Canada Central or Canada East|
|Europe||North Europe or West Europe|
|Germany||Germany West Central|
|India||Central India or South India|
|Japan||Japan East or Japan West|
|Korea||Korea Central or Korea South|
|United Arab Emirates||UAE North|
|United Kingdom||UK South or UK West|
|United States||Central US or West US 2|
For Switzerland geography, Switzerland West is only available for REST API users and need an approved subscription.
Supported geographies (Azure Government)
|Create project||United States||Metadata is stored in US Gov Arizona, US Gov Virginia|
|Target assessment||United States||Target regions: US Gov Arizona, US Gov Virginia, US Gov Texas|
|Target replication||United States||Target regions: US DoD Central, US DoD East, US Gov Arizona, US Gov Iowa, US Gov Texas, US Gov Virginia|
VMware assessment and migration
Review the Azure Migrate: Discovery and assessment and Azure Migrate: Server Migration support matrix for VMware VMs.
Hyper-V assessment and migration
Review the Azure Migrate: Discovery and assessment and Azure Migrate: Server Migration support matrix for Hyper-V VMs.
Azure Migrate versions
There are two versions of the Azure Migrate service:
- Current version: Using this version you can create new projects, discover on-premises assesses, and orchestrate assessments and migrations. Learn more.
- Previous version: For customer using the previous version of Azure Migrate (only assessment of on-premises VMware VMs was supported), you should now use the current version. In the previous version, you can't create new projects or perform new discoveries.