About Azure Migrate
The Azure Migrate service assesses on-premises workloads for migration to Azure. The service assesses the migration suitability of on-premises machines, performance-based sizing, and provides cost estimations for running your on-premises machines in Azure. If you're contemplating lift-and-shift migrations, or are in the early assessment stages of migration, this service is for you. After the assessment, you can use services such as Azure Site Recovery and Azure Database Migration Service, to migrate the machines to Azure.
Why use Azure Migrate?
Azure Migrate helps you to:
- Assess Azure readiness: Assess whether your on-premises machines are suitable for running in Azure.
- Get size recommendations: Get size recommendations for Azure VMs based on the performance history of on-premises VMs.
- Estimate monthly costs: Get estimated costs for running on-premises machines in Azure.
- Migrate with high confidence: Visualize dependencies of on-premises machines to create groups of machines that you will assess and migrate together.
- Currently, you can only assess on-premises VMware virtual machines (VMs) for migration to Azure VMs. The VMware VMs must be managed by vCenter Server (version 5.5, 6.0, or 6.5).
- Support for Hyper-V is on our roadmap. In the interim, we recommend that you use Azure Site Recovery Deployment Planner to plan migration of Hyper-V workloads.
- You can discover up to 1500 VMs in a single discovery and up to 1500 VMs in a single project. Additionally, you can assess up to 1500 VMs in a single assessment.
- You can only create an Azure Migrate project in West Central US or East US region. However, this does not impact your ability to plan your migration for a different target Azure location. The location of the migration project is used only to store the metadata discovered from the on-premises environment.
- Azure Migrate only supports managed disks for migration assessment.
What do I need to pay for?
Learn more about Azure Migrate pricing here.
What's in an assessment?
An assessment helps you identify the Azure suitability of on-premises VMs, get right-sizing recommendations and cost estimates for running the VMs in Azure. Assessments can be customized based on your needs by changing the properties of the assessment. Below are the properties that are considered while creating an assessment.
|Target location||The Azure location to which you want to migrate.
Azure Migrate currently supports 30 regions including Australia East, Australia Southeast, Brazil South, Canada Central, Canada East, Central India, Central US, China East, China North, East Asia, East US, Germany Central, Germany Northeast, East US 2, Japan East, Japan West, Korea Central, Korea South, North Central US, North Europe, South Central US, Southeast Asia, South India, UK South, UK West, US Gov Arizona, US Gov Texas, US Gov Virginia, West Central US, West Europe, West India, West US, and West US2. By default, the target location is set to West US 2.
|Storage redundancy||The type of storage redundancy that the Azure VMs will use after migration. Locally Redundant Storage (LRS) is the default. Note that Azure Migrate only supports managed disks-based assessments and managed disks only support LRS, hence the property currently only has the LRS option.|
|Sizing Criterion||The criterion to be used by Azure Migrate to right-size VMs for Azure. You can do sizing either based on performance history of the on-premises VMs or size the VMs as on-premises for Azure without considering the performance history. The default value is performance-based sizing.|
|Pricing plans||For cost calculations, an assessment considers whether you have software assurance, and are eligible for Azure Hybrid Benefit. It also considers Azure Offers that you might be enrolled to, and allows you to specify any subscription-specific discounts (%), that you may get on top of the offer.|
|Pricing tier||You can specify the pricing tier (Basic/Standard) for the target Azure VMs. For example, if you are planning to migrate a production environment, you would like to consider the Standard tier, which provides VMs with low latency but may cost more. On the other hand, if you have a Dev-Test environment, you may want to consider the Basic tier that has VMs with higher latency and lower costs. By default the Standard tier is used.|
|Performance history||By default, Azure Migrate evaluates the performance of on-premises machines using the performance history of the last one day, with a 95% percentile value. You can modify these values in the assessment properties.|
|VM series||You can specify the VM series that you would like to consider for right-sizing. For example, if you have a production environment that you do not plan to migrate to A-series VMs in Azure, you can exclude A-series from the list or series and the right-sizing will be done only in the selected series.|
|Comfort factor||Azure Migrate considers a buffer (comfort factor) during assessment. This buffer is applied on top of machine utilization data for VMs (CPU, memory, disk, and network). The comfort factor accounts for issues such as seasonal usage, short performance history, and likely increases in future usage.
For example, 10-core VM with 20% utilization normally results in a 2-core VM. However, with a comfort factor of 2.0x, the result is a 4-core VM instead. The default comfort setting is 1.3x.
How does Azure Migrate work?
- You create an Azure Migrate project.
- Azure Migrate uses an on-premises VM called the collector appliance, to discover information about your on-premises machines. To create the appliance, you download a setup file in Open Virtualization Appliance (.ova) format, and import it as a VM on your on-premises vCenter Server.
- You connect to the VM using console connection in vCenter Server, specify a new password for the VM while connecting and then run the collector application in the VM to initiate discovery.
- The collector collects VM metadata using VMware PowerCLI cmdlets. Discovery is agentless, and doesn't install anything on VMware hosts or VMs. The collected metadata includes VM information (cores, memory, disks, disk sizes, and network adapters). It also collects performance data for VMs, including CPU and memory usage, disk IOPS, disk throughput (MBps), and network output (MBps).
- The metadata is pushed to the Azure Migrate project. You can view it in the Azure portal.
- For the purposes of assessment, you gather the discovered VMs into groups. For example, you might group VMs that run the same application. For more precise grouping, you can use dependency visualization to view dependencies of a specific machine, or for all machines in a group and refine the group.
- Once your group is formed, you create an assessment for the group.
- After the assessment finishes, you can view it in the portal, or download it in Excel format.
What are the port requirements?
The table summarizes the ports needed for Azure Migrate communications.
|Component||To communicate with||Port required||Reason|
|Collector||Azure Migrate service||TCP 443||The collector connects to the service over SSL port 443|
|Collector||vCenter Server||Default 443||By default the collector connects to the vCenter Server on port 443. If the server listens on a different port, it should be configured as an outgoing port on the collector VM.|
|On-premises VM||Log Analytics Workspace||TCP 443||The MMA agent uses TCP 443 to connect to Log Analytics. You only need this port if you're using the dependency visualization feature, and are installing the Microsoft Monitoring Agent (MMA).|
What happens after assessment?
After you've assessed on-premises machines for migration with the Azure Migrate service, you can use a couple of tools to perform the migration:
Azure Site Recovery: You can use Azure Site Recovery to migrate to Azure, as follows:
- Prepare Azure resources, including an Azure subscription, an Azure virtual network, and a storage account.
- Prepare your on-premises VMware servers for migration. You verify VMware support requirements for Site Recovery, prepare VMware servers for discovery, and prepare to install the Site Recovery Mobility service on VMs that you want to migrate.
- Set up migration. You set up a Recovery Services vault, configure source and target migration settings, set up a replication policy, and enable replication. You can run a disaster recovery drill to check that migration of a VM to Azure is working correctly.
- Run a failover to migrate on-premises machines to Azure.
- Learn more in the Site Recovery migration tutorial.
Azure Database Migration: If your on-premises machines are running a database such as SQL Server, MySQL, or Oracle, you can use the Azure Database Migration Service to migrate them to Azure. Learn more.
Follow a tutorial to create an assessment for an on-premises VMware VM.