Today, the Azure Migrate team launched an update to the Azure Migrate service, which can help you discover, assess, and migrate applications, infrastructure, and data from your on-prem environment to Microsoft Azure. This is excellent timing since we all know that Windows Server 2008 and Windows Server 2008 R2 are soon out of support and you get free extended security updates if you migrate your VMs to Azure. With Azure Migrate, you can now centrally track the progress of your migration journey across multiple thrid-party and Microsoft tools. In addition, Azure Migrate can now assess and migrate your Hyper-V virtual machines (VMs).
With the latest release of Azure Migrate you can now:
- Extensible approach with choice across Microsoft and popular ISV assessment and migration tools
- Integrated experience for discovery, assessment, and migration with end-to-end progress tracking for servers and databases
- Server Assessment and Server Migration for large-scale VMware, Hyper-V, and physical server migrations
- Database Assessment and Database Migration across various database targets including Azure SQL Database and Managed Instance
You can find more about the Azure Migrate capabilities on Microsoft Docs. For more information on Azure Migration, check out my blog post about Azure Migration on the Nigel Frank International blog. In this post, I am going to show you how you can step-by-step assess and migrate Hyper-V VMs to Azure using Azure Migrate.
First, you need to prepare your Azure to set the right permissions and prepare the on-premises Hyper-V hosts and VMs for server assessment and migration. You can find more about the details for permissions and host preparations on Microsoft Docs.
Next, you will need to create a new Migration project for servers. Click on Asses and migrate servers.
Now you will need to add the tools you want to use for the assessment as well as for the migration, click on “add tools”.
You will need to create a new Azure Migrate project. Enter the details for your subscription, resource group, and a name for the project. You will also need to choose a region where your project is going to be deployed. No worries, this will only store the assessment data, you can still select another region for the migration.