Review requirements for Hyper-V VM migration to Azure Local using Azure Migrate (preview)
Applies to: Azure Local 2311.2 and later
This article lists the system requirements for migrating Hyper-V virtual machines (VMs) to Azure Local using Azure Migrate.
Important
This feature is currently in PREVIEW. See the Supplemental Terms of Use for Microsoft Azure Previews for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
Supported configurations
The following operating systems (OS) are supported for the source appliance, target appliance, and for the guest VMs that your'e migrating.
| Component | Supported configurations |
|---|---|
| Source environment | Hyper-V on Windows Server 2022 Hyper-V on Windows Server 2019 Hyper-V on Windows Server 2016 Hyper-V on Windows Server 2012 R2 |
| Source appliance | Windows Server 2022 |
| Target environment | Azure Local 2311.2 or later |
| Target appliance | Windows Server 2022 |
| Guest VM (Windows) | Windows Server 2022 Windows Server 2019 Windows Server 2016 Windows Server 2012 R2 Windows Server 2008 R2* |
| Guest VM (Linux) | Red Hat Linux 6.x, 7.x Ubuntu Server and Pro. 18.x CentOS 7.x SUSE Linux Enterprise 12.x Debian 9.x |
*To migrate Windows Server 2008 R2 VMs, see the FAQ.
Supported geographies
You can create an Azure Migrate project in many geographies in the Azure public cloud. Here's a list of supported geographies for migration to Azure Local:
| Geography | Metadata storage locations |
|---|---|
| Asia-Pacific | South East Asia, East Asia |
| Europe | North Europe, West Europe |
| United States | East US, Central US, West Central US, West US2 |
Keep in mind the following information as you create a project:
- 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. Azure Migrate doesn't move or store customer data outside of the region allocated.
Azure portal requirements
For more information on Azure subscriptions and roles, see Azure roles, Azure AD roles, and classic subscription administrator roles.
| Level | Permissions |
|---|---|
| Tenant | Application administrator |
| Subscription | Contributor, User Access Administrator |
For any subscriptions hosting resources used in migration, such as Azure Migrate project subscriptions and target Azure Local instance subscriptions, the Microsoft.DataReplication resource provider must be registered. For more information, see register resource provider.
Source Hyper-V requirements
Hyper-V Server is supported for both standalone server and cluster configuration.
You can discover and migrate standalone (non highly available) VMs on standalone Hyper-V hosts. However, standalone VMs hosted on clustered Hyper-V hosts can't be discovered or migrated. To migrate these VMs, they need to be made highly available first.
The source server used for migration should have sufficient resources to create a Windows Server 2022 VM with this minimum of 16 GB memory, 80 GB disk, and 8 vCPUs.
In this release, you can only migrate VMs that have disks attached to the cluster shared volumes (CSV). If the VM disks aren't attached to the CSV, the disks can't be migrated.
DAS and SMB shares on source system are not supported for migrations to Azure Stack HCI.
Before you begin, for all Windows VMs, bring all the disks online and persist the drive letter. For more information, see how to configure a SAN policy to bring the disks online.
Verify that none of the VMs you plan to migrate have the Azure Connected Machine Agent installed. For more information, see FAQ.
Target Azure Local requirements
The target system must be running Azure Local.
An Arc Resource Bridge must exist on the Azure Local system for migration. The Arc Resource Bridge is automatically created during the deployment. To verify that an Arc Resource Bridge exists on your Azure Local system, see Deploy using Azure portal.
Ensure that a logical network is configured on your Arc Resource Bridge. For more information, see Create a logical network.
Ensure that a custom storage path is configured on your Arc Resource Bridge for migration. For more information, see Create a storage path.
Azure Migrate project requirements
Existing Azure Migrate customers that have done VM discovery need to create a new Azure Migrate project for migration to Azure Local. You can't use existing Azure Migrate projects for migration.