Edit

Prerequisites for VMware migration to Azure Local using Azure Catalyst

Applies to: Azure Local 2503 and later

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.

Prerequisites

The following list contains the prerequisites and considerations that you must meet 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 Catalyst 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, 5986 – 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

For Azure Government, see Migrate VMs to Azure Local in Azure Government.
Configure SAN/disks policy on VMs. source Configure SAN/disks policy.
Install Hyper-V Linux Integration Services on Linux VMs source Rebuild the Linux init image so it contains the necessary Hyper-V drivers.
Rebuilding the init image ensures that the VM boots on Azure Local. Most new versions of Linux distributions include this service.
Verify secure boot status of guest VMs source Secure Boot settings are preserved for UEFI (Generation 2) VMs during migration. Configure Secure Boot as intended on the source VM before migration. If you modify Secure Boot settings, allow up to 30 minutes for the Azure Catalyst discovery service to detect the change before initiating migration.
Disable BitLocker on Windows VMs. source BitLocker must be disabled on VMs before migration.
Encrypted disks/volumes aren't supported. source Decrypt any encrypted disks or volumes on VMs before migration.
Shared disks aren't supported. source Ensure that VMs don't have any shared disks attached before migration.
Decide how to handle Azure Connected Machine Agent on source VMs (if present) source If the source VM is Azure Arc-enabled, you can reuse its existing Azure Arc resource during migration and keep the agent installed. See Reuse Azure Arc-enabled server resources when you migrate VMs to Azure Local. If you don't reuse the resource, uninstall the Azure Connected Machine Agent before initiating replication. See Azure Catalyst FAQ for more information.
Review snapshot-based backup solutions source If you use snapshot-based backups on VMware VMs, make sure they don't run at the same time as Azure Catalyst replication cycles. Concurrent snapshot operations can interfere with replication cycles. See Replication Cycles for more information.
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 Azure Arc resource bridge for storing VM configuration and OS disks. target Create storage path.
Create a logical network for the Azure Arc resource bridge for VMs to use. target Create a logical network.
Configure Azure account permissions for project creation and appliance registration. both The account needs the Azure Local Migrate Owner role at the Azure subscription scope and the Application Developer role at the Microsoft Entra ID tenant scope. For more information, see Azure account permissions.
Create an Azure Catalyst project in the Azure portal source, target You must create the project in the Azure portal. Projects created by other methods can't replicate to Azure Local. See Create an Azure Catalyst project.

Create an Azure Catalyst project

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

Important

To migrate to Azure Local, you must create the Azure Catalyst project in the Azure portal. Azure Local migrations don't support projects that you create by using other methods - such as an Azure Resource Manager (ARM) template, the REST API, Azure CLI, Azure PowerShell, or the Create a project in a specific region quickstart. If you use one of these methods, you can't replicate VMs to Azure Local. You must create a new project in the Azure portal to continue.

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

  2. On Get started, select Start migration journey. To open a project that you already created, select View all projects instead.

    Screenshot of the Get started page in the Azure portal with Start migration journey highlighted.

  3. On Create project:

    1. Select your subscription. Ensure that the chosen subscription is associated with the same Azure tenant as the Azure Local instance.
    2. Select a resource group, or select Create new to create one.
    3. For Project, enter a name for the project.
    4. For Geography, select a supported geography. For more information, see Supported geographies.
    5. Under Artifact store details, select Use same subscription and resource group as project. The artifact store is a storage account that stores artifacts generated for the project. By default, a new storage account is created. To use a storage account that you already have, select Select an existing storage account.
    6. Under Advanced, keep Connectivity method set to Public endpoint. Private endpoint connectivity isn't supported for Azure Local migrations.

    Screenshot of the Create project page in the Azure portal with the artifact store details and connectivity method highlighted.

  4. When finished, select Create. Keep the page open until the project is created.

Next steps