Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
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 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, 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 |
| 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 Migrate 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. |
| Uninstall Azure Connected Machine Agent on source VMs (if present) | source | If the source VM is Arc-enabled, ensure that you uninstall the Azure Connected Machine Agent before initiating replication. See Azure Migrate 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 Migrate 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. |
| 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 the Azure portal by using the following procedure. For more information, see Create and manage projects.
On the Azure portal home page, select Azure Migrate.
On Get started, select Create project.
On Create project:
- Enter your subscription. Make sure that the chosen subscription is associated with the same Azure tenant as the Azure Local instance.
- Enter the resource group, or select it if it already exists.
- Enter the new project name.
- Select a supported geography region that you previously created. For more information, see Supported geographies.
When finished, select Create.
