Tool Introduction / Summary

Firstly, Azure Migrate helps with the discovery by using a Collector Application. Currently, this only is available for VMware environments (Hyper-V is on the roadmap) and uses an Open Virtualization Appliance (.OVA) format to deploy the Virtual Machine. The Collector Appliance then connects to your on-premises vCenter Server and collects data (agentless-ly) from the systems.

Next, after discovering your on-premises systems, the service assesses migration suitability and performance-based sizing and provides cost estimations for running your on-premises machines in Azure. For further details on what’s in an assessment, see the Microsoft documentation here.

Azure Migrate – Overview Diagram

But what about the migrate part?

Currently, Azure Migrate does not have a migration component. Right now, it directs us to use either the Azure Site Recovery (ASR) or Azure Database Migration tools.

According to the Azure Migrate team…

In future, we will integrate the migration capabilities of ASR in Azure Migrate to provide a single streamlined experience for both planning and performing migrations.

The tool also will include dependency visualizations by leveraging the Operations Management Suite (OMS) Service Map solution.

What Is It Used For?

The tool combines discovery and assessment activities, with the “migrate” action to be released in the future.

It’s best used when you are just starting on your Azure migration journey.

Pro’s vs Con’s

Here is a quick list of what we deem as Pro’s/Con’s of this tool.

Pro’s

Includes the use of the Operations Management Suite (OMS) Service Map solution to provide a full application topology map (at no additional cost)

Assessment includes calculations for Software Assurance, Azure Hybrid Use Benefits, and subscription-specific discounts

Performance evaluation is based on a month of history

The comfort factor accounts for issues such as seasonal usage, short performance history, and likely increases in future usage

Con’s

No support currently for Hyper-V (on the roadmap), physical servers, or non-vCenter servers (i.e. ESXi standalone)

Azure Migrate Projects can only (currently) be created in the West Central US

Azure Migrate only supports managed disks for migration assessment

Limited up to 1,000 VMs in a single discovery, and 1,500 in a single Project

Assessments are limited up to 400 VMs at a time

Dependency visualization requires the installation of 2 Agents (the OMS Agent and the Service Map Dependency Agent); whereas all other components are agentless

During the preview phase/timeframe, use of Service Map incurs costs

Other Thoughts

This tool will become the one-stop-shop for Azure migrations. As the tool is enhanced (with the inclusion of Service Map) and expanded (to include Hyper-V), it will become the default starting point for everything migration related.

It’s important that you understand how Azure Migrate differs from the Azure Site Recovery (ASR) Deployment Planner.

Azure Migrate performs right-sizing considering performance history for compute, storage, as well as networking. It also estimates the ongoing costs of running the machines in Azure, post-migration.

So, ASR Deployment Planner and Azure Migrate have different features that complement each other. Over time, the plan is for Azure Migrate to subsume the ASR Deployment Planner functionality, so you get both high level and detailed assessments.

As the following picture depicts, if you are contemplating migrations, start with Azure Migrate. If you are at the stage of implementing migrations, use the ASR Deployment Planner, and if you are performing migrations, use Azure Site Recovery (ASR).