Prerequisites for VMware migration to Azure Local using Azure Migrate (preview)

Applies to: Azure Local, version 23H2

This article describes the prerequisite tasks you need to complete before you begin the process to migrate VMware virtual machines (VMs) to Azure Local. Make sure to review the requirements for migration if you haven't already.

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.

Prerequisites

The following list contains the prerequisites that must be met to migrate VMware VMs to Azure Local. Some prerequisites apply to the source VMware server, some to the target Azure Local instance, and others to both.

Prerequisite	Applies to	More information
Open required VMware firewall ports.	source	3389 – Inbound connections on port 3389 to allow remote desktop connections to the appliance. 44368 – Inbound connections on port 44368 to remotely access the appliance management app by using the URL: https://<appliance-ip-or-name>:44368. 443 – Inbound and outbound connections on port 443 to communicate with Azure Migrate services orchestrating replication and migration, and to allow the appliance to communicate with vCenter Server. 902 – Inbound and outbound connections on port 902 for the appliance to replicate data from snapshots of ESXi hosts and send heartbeat traffic to vCenter. 445 – Inbound and outbound connections on port 445 (SMB) to communicate between source and target appliance.
Open required Hyper-V firewall ports.	target	3389 – Inbound connections on port 3389 to allow remote desktop connections to the appliance. 44368 – Inbound connections on port 44368 to remotely access the appliance management app by using the URL: https://<appliance-ip-or-name>:44368. 445 – Inbound and outbound connections on port 445 (SMB) to communicate between source and target appliance. 5985 – Inbound and outbound connections on port 5985 (WinRM) to communicate from appliance to host.
Allow required URLs	source, target	URL access and *.siterecovery.azure.com
Configure SAN policy on VMware VMs.	source	Configure SAN policy.
Deploy, configure, and register an Azure Local instance.	target	Create and register an Azure Local instance.
Verify a successful deployment.	target	Verify a successful deployment.
Verify and make a note of the custom location created during deployment on the Azure Local system.	target	Verify a successful deployment.
Create a custom storage path for the Arc Resource Bridge for storing VM configuration and OS disks.	target	Create storage path.
Create a logical network for the Arc Resource Bridge for VMs to use.	target	Create a logical network.
Enable contributor and user administrator access on the subscription for the Azure Migrate project.	both	Assign Azure roles using the Azure portal.
Create an Azure Migrate project	source, target	Create an Azure Migrate project.

Create an Azure Migrate project

Before you can migrate, create an Azure Migrate project in Azure portal using the following procedure. For more information, see Create and manage projects.

1. On the Azure portal home page, select Azure Migrate.

2. On the Get started page, under Servers, databases and web apps, select Discover, assess and migrate.

   

3. On the Servers, databases and web apps page, select Create project.

4. On the Create project page:

   1. Enter your subscription. Make sure that the chosen subscription is associated with the same Azure tenant as the Azure Local instance.
   2. Enter the resource group, or select it if it already exists.
   3. Enter the new project name.
   4. Select a supported geography region that you previously created. For more information, see Supported geographies.

   

5. When finished, select Create.

Next steps

• Discover and replicate VMware VMs.