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 discovery and replication phase for VMware virtual machine (VM) migration to Azure Local using Azure Catalyst.
For more information about appliances for Azure Catalyst and how to manage them, see Azure Migrate appliance.
If your Azure Local instance is in Azure Government, see Migrate VMs to Azure Local in Azure Government for the steps that differ. To replicate and migrate VMs by using PowerShell, Azure CLI, or Terraform instead of the Azure portal, see Migrate VMs to Azure Local using PowerShell, Azure CLI, or Terraform.
Before you begin
For both the source VMware vCenter Server and target Azure Local appliances, make sure that the underlying hardware has sufficient resources to support the creation of a Windows Server 2022 VM with a minimum of 16 GB RAM, 80 GB of disk storage (HDD), 8 vCPUs, and an external virtual switch.
Ensure all VMs that you wish to migrate are powered on and have VMware tools installed. Migration fails if the VMs aren't powered on and don't have VMware tools installed.
Step 1: Create and configure the source VMware appliance
Generate the project key
In the Azure portal, go to Azure Migrate > All projects and select your project from the list.
On the project Overview, under Inventory, select Start discovery.
On Start discovery, for How do you want to discover?, select Using appliance, and then select Continue. Azure Local migrations support only appliance-based discovery.
On Discover, under Are your servers virtualized?, select Yes, with VMware vSphere Hypervisor.
Under 1: Generate project key, enter a name for your source appliance, and then select Generate key.
Copy the Project key to a text editor such as Notepad and save it for later use. You can also find the key later by selecting Manage existing appliances.
Under 2: Download Azure Migrate appliance, download the source appliance by using either an .ova file or a .zip file. The detailed steps are provided in the subsequent sections.
Create the source appliance
You can install the appliance by using either an .ova file or a .zip file that you download to your VMware host server.
Install using an .OVA file
This step applies only if you are deploying the source VMware appliance using an .OVA file.
- After you download the .OVA file, verify that the file is secure.
- Create the source VMware appliance.
- Verify that the appliance can access Azure.
Install using a .zip file
This step applies only if you downloaded the .zip file. Use the AzureMigrateInstaller.ps1 PowerShell script to install the source appliance. For specific information, see Set up an appliance with a script.
Create a VM in the VMware vCenter with the following configuration:
- Operating system: Windows Server 2022 or Windows Server 2025
- vCPU: 8
- Disk: >80 GB
- Memory: 16 GB
After you create the VM, sign in to the VM as an administrator.
Copy the downloaded zip file to the new VM that you created in the vCenter. Extract the zip to a folder and go to where the
AzureMigrateInstaller.ps1PowerShell script resides in the extracted folder.Open a PowerShell window as an administrator and run the following command:
Set-ExecutionPolicy -ExecutionPolicy Unrestricted .\AzureMigrateInstaller.ps1 -Scenario VMware -Cloud Public -PrivateEndpoint:$falseSelect option 1 as the desired configuration: Primary appliance to discover, assess and migrate servers.
Follow the rest of the onscreen instructions to install the source appliance and uninstall Internet Explorer.
Restart the VM after the installation is complete. Sign in to the VM.
Configure the source appliance and discover VMs
After you install the source appliance, configure the source appliance by completing these steps:
Set up the prerequisites and register the source appliance.
If needed, use a preconfigured Microsoft Entra ID application to register the source appliance. See Register an Azure Migrate appliance with a preconfigured Microsoft Entra ID application for detailed instructions.
Note
Each preconfigured application can only be used with a single appliance. You must create a separate preconfigured application for the target appliance and for any additional appliances in other projects.
Make sure that the VMware Virtual Disk Development Kit (VDDK) is installed. Download and extract the VMware Virtual Disk Development Kit in zip format to the provided folder path. Versions 8.0.0, 8.0.1, and 8.0.2 are currently supported. Version 6.7.0 is also supported but the package is deprecated, so new deployments can't use this version. Don't use VDDK 7.0.X. These versions have known problems and result in errors during migration.
Important
Azure Catalyst doesn't provide VDDK packages, and access to them might be restricted. If a supported VDDK package isn't available to your organization, use a third-party migration option to migrate your VMware VMs to Azure Local.
Select Verify to make sure that the VMware VDDK is successfully installed.
Provide vCenter server credentials for the discovery of VMware VMs.
- Select Add credentials.
- Select the Source type as vCenter Server.
- Provide a Friendly name for the credentials.
- Enter the Username and the Password for the vCenter server.
- Save the credentials.
Add discovery sources.
- Add the vCenter discovery source.
- Enter the IP address or FQDN of the vCenter server.
- Enter the friendly name for the credentials used when discovering the VMware VMs.
- Select Save. Select Add more to repeat this step for each vCenter server. The discovery source table is updated.
Disable the slider under the Applications discovery and agentless dependency analysis section. This feature isn't currently supported in VMware to Azure Local migrations.
Onboard to Azure Local
After you add the discovery sources, onboard to the target Azure Local instance. This step validates connectivity between the source appliance and the target Azure Local instance, and provides the information needed about the target system for migration.
Toggle the slider to Enable credentials for Azure Local.
Select Add information to provide the necessary information and credentials for the target Azure Local instance.
Select Save.
The information table is updated and the status changes to Validated.
Start discovery
Once the source appliance is configured and onboarded to Azure Local, you can start the discovery of VMware VMs.
Select Start Discovery. The discovery might take several minutes to finish.
Wait until you see a green checkmark that indicates the discovery is finished. This mark also means the migration readiness checks are successful. After the discovery finishes, go to the Azure portal to review the VM inventory.
Ensure that all VMs you want to migrate are powered on and have VMware tools installed before or during the discovery process.
Step 2: Create and configure the target appliance
Generate target appliance key
Generate the target appliance key from the Replicate wizard. Open the wizard from Server replication, the page in your project where you replicate, migrate, and track the VMs that you move to Azure Local.
In the Azure portal, go to your project and select Overview. Under Inventory summary, verify that Workloads shows a value greater than zero.
In the left pane, under Manage, select Server replication.
Until you replicate VMs to Azure Local, the page shows No replicating items found and columns that don't apply to Azure Local, such as Test migration status. After you replicate VMs, the page shows the Azure Local columns, and Start replication changes to Replicate.
Select Start replication.
On Specify intent:
- The What do you want to migrate? field automatically shows Servers or Virtual machines (VM).
- For Where do you want to migrate to?, select Azure Local (formerly Azure Stack HCI). How will you select workloads? is set to From all inventory.
- For Discovery method, select the source appliance that you used for discovery. Migration mode is set to Agentless migration.
- When finished, select Continue.
On the Basics tab of the Replicate wizard, select the subscription, resource group, and target system for your Azure Local instance. Verify that the system shows a green check, and then select Next.
On the Appliances tab, select Deploy and configure target appliance.
On the Deploy and configure the target appliance pane, provide a name for the target appliance and then select Generate key.
Copy the Project key (to a text editor such as Notepad) and save it for later use. You can close the Replicate wizard. You start replication after you register the target appliance.
Create the target appliance
Install using a template (.vhd file)
This step applies only if you downloaded the .vhd zipped file.
Check that the zipped file is secure before you deploy it.
On the machine where you downloaded the file, open PowerShell as an administrator.
Run the following command to generate the hash for the VHD.
C:\>Get-FileHash -Path <Path to downloaded VHD zip> -Algorithm SHA256Verify the latest appliance versions and hash values:
Scenario Download SHA256 Azure Local appliance Latest version: https://go.microsoft.com/fwlink/?linkid=21918476ae1144b026efb2650f5e11c007a457c351a752f942c2db827dd2903f468dccb Extract the zipped file to a folder.
Now you can install the appliance using the .vhd file.
Using local tools, such as Hyper-V Manager or Failover Cluster, install the target appliance from the downloaded .vhd file on your Azure Local instance.
After the VM finishes provisioning and boots, open the Azure Migrate Target Appliance Configuration Manager shortcut from the desktop.
Install using a script (.zip file)
This step applies to using a .zip file.
Create a VM in Azure Local with the following configuration:
- Operating system: Windows Server 2022 or Windows Server 2025
- vCPU: 8
- Disk: >80 GB
- Memory: 16 GB
After you create the VM, sign in to the VM as an administrator.
You can download the appliance from a .zip file. Under Step 2: Download and install the target appliance, select .zip, and then select Download.
Copy the downloaded zip file to the new VM that you created on the Azure Local instance. Extract the zip to a folder and go where the
AzureMigrateInstaller.ps1PowerShell script is located.Open PowerShell as an administrator and run the following command:
Set-ExecutionPolicy -ExecutionPolicy Unrestricted .\AzureMigrateInstaller.ps1 -Scenario AzureLocalTarget -Cloud Public -PrivateEndpoint:$falseRestart the VM after the installation is complete. Sign in to the VM.
Register the target appliance
Sign in to the target appliance VM.
Open Azure Migrate Target Appliance Configuration Manager from the desktop shortcut. Read and accept the Terms of Use.
Locate the target key that you previously generated, paste it in the field under Verification of Azure Migrate project key, and then select Verify.
After the verification is complete, select Log in and sign in to your Azure account.
- If needed, you can use a preconfigured Microsoft Entra ID application to register the target appliance. See Register an Azure Migrate appliance with a preconfigured Microsoft Entra ID application for detailed instructions.
Note
Each preconfigured application can only be used with a single appliance. You must create a separate preconfigured application for each appliance.
Enter the code that is displayed in your Authenticator (or similar) app for MFA authentication.
Wait until you see The appliance has been successfully registered message.
Sign in to Microsoft Azure PowerShell using the code displayed in your Authenticator app. It can take up to 10 minutes for the appliance to be registered.
After the appliance is registered, under Manage Azure Local instance information, select Add system information.
For your target Azure Local instance, enter the system FQDN (example format is systemname.domain.com), domain name, username, and password, and then select Save.
After the credentials are accepted, the status changes to Validated. Select Configure.
Wait until the configuration is complete and you see this message: Successfully configured Azure Migrate project.
Step 3: Start replication
After you register the target appliance, return to Server replication to start replication.
In the Azure portal, go to your project. In the left pane, under Manage, select Server replication, and then select Start replication. If the project already has replicated VMs, select Replicate instead.
On Specify intent, select the same values that you used in Generate target appliance key, and then select Continue.
On Replicate, on the Basics tab:
- The subscription field is automatically populated. If this subscription isn't the one that has your target Azure Local instance, choose the Azure subscription that has the system.
- Select the resource group associated with your target system.
- For Target system, select the Azure Local resource.
- Verify there's a green check for the system. A green check indicates that all the prerequisites such as Azure Arc resource bridge are configured on this system.
- When finished, select Next.
On the Appliances tab:
- Source appliance shows the appliance that you selected on Specify intent.
- For Target appliance, select the target appliance on your Azure Local instance.
- Verify that both appliances show a green checkmark. The message confirms that the appliance is connected and shows when its Azure Local credentials for the selected system were last verified.
- When finished, select Next.
Note
If an appliance is disconnected, or its Azure Local credentials are missing, no longer valid, or don't match the selected system, fix the issue on the appliance and then select the refresh button next to it. To update credentials, see Onboard to Azure Local for the source appliance and Register the target appliance for the target appliance. If no target appliance is registered for the system, select Deploy and configure target appliance to set one up.
On the Virtual machines tab:
For Do you want to retain the Azure Arc-enabled server connected machine agents during migration?, select Yes or No. You must select an option to continue.
- Yes: Reuse the existing Azure Arc resources of Arc-enabled source VMs. After you select the VMs, select Configure Arc-enabled server reuse, choose the VMs to reuse, and then select Save. Next stays unavailable until you save this configuration.
- No: Azure Catalyst creates a new Azure Local VM resource for every migrated VM. If any source VMs are Arc-enabled servers, uninstall the Azure Connected Machine agent on them before you migrate.
Select up to 10 VMs to replicate. Use the search box to filter the list. VMs that can't be replicated are unavailable and show the reason next to the name, such as already in replication or VM powered off. After you fix the issue, it can take up to 30 minutes for the VM to become available.
To review your selection or remove VMs from it, select Selected virtual machines.
When finished, select Next.
Note
Arc reuse preserves each resource's tags, role assignments, Azure Policy assignments, and extensions, but locks the target resource group and VM name for every VM in the batch. You can't change the setting after replication starts. For more information, see Reuse Azure Arc-enabled server resources when you migrate VMs to Azure Local.
On the Security tab, choose the security settings for the migrated VMs. Only Generation 2 (UEFI) VMs, shown with a Boot type of efi, support Secure Boot and the Trusted launch security type. Generation 1 (BIOS) VMs are migrated with the Standard security type, and Secure Boot shows Not available.
For each Generation 2 VM, select a Security type:
- Standard: Migrates the VM with the basic level of security.
- Trusted Launch: Creates the Azure Local VM with Secure Boot and a virtual Trusted Platform Module (vTPM) enabled. Trusted launch requires Secure Boot, so Enable Secure Boot is selected automatically and can't be cleared. For more information, see Trusted launch for Azure Local VMs.
To enable Secure Boot on a Generation 2 VM that doesn't use it on the source, select Enable Secure Boot for that VM. To enable it on all of them at once, turn on Enable Secure Boot on all Generation 2 VMs that don't currently use it. Before you enable Secure Boot, make sure the guest OS supports it.
If Secure Boot is enabled on the source VM, it shows Enabled at source and stays enabled after migration.
When finished, select Next.
Important
- Choose the security type before you start replication. There's no supported way to convert a migrated Standard VM to Trusted launch later.
- Azure Catalyst doesn't migrate vTPM state or keys from the source VM. A Trusted launch VM gets a new vTPM on Azure Local. Guest attestation isn't enabled during migration.
On the Target settings tab, complete these tasks:
The Storage account subscription is automatically populated. If this subscription isn't where you want to create the storage account, select a different subscription.
Select the Resource group to associate with your storage account.
For your storage account, you can select an existing storage account from the dropdown list or create a new one by selecting Create new. The storage account is only used for storing metadata during replication and migration. All migrated VM data and disks remain completely on-premises.
Note
If you use an existing storage account, ensure the following conditions are true:
- The storage account is Standard Performance tier and uses Azure Blob storage. Premium storage accounts aren't supported.
- The storage account has Public network access enabled. If public network access is disabled, replication fails.
Select a resource group to associate with your migrated VMs. This resource group can be different than the resource group associated with your storage account.
Select the logical network that you created as a prerequisite. The VMs are connected to this network.
If you don't see a logical network in the dropdown list, Create a logical network and select Reload logical network.
Select the storage path that you created as a prerequisite. The VMs are created at this storage path. Ensure that the storage path has sufficient space to accommodate the VMs being migrated.
If you don't see a storage path in the dropdown list, Create a storage path and select Reload storage path.
When finished, select Next.
On the Compute tab:
Rename target VMs as needed. Make sure that the VM names conform to the Azure naming conventions.
Select the OS disk for each VM from the dropdown lists.
Configure the number of vCPUs and RAM, including selecting dynamic RAM for each VM, as needed.
When finished, select Next.
On the Disks tab, select which disks you want to replicate.
Note
Once selected, the OS disks can't be unselected.
Change the disk type if needed and select Next.
- It is recommended to use VHDX format for the disks to ensure future expand and disk operations compatibility.
On the Review + Start replication tab, make sure that all the values are correct and then select Replicate.
Stay on this page until the process is complete (this might take 5-10 minutes). If you move away from this page, the replication artifacts won't be created fully leading to a failure in replication and eventually migration.
When the process finishes, go to your project and select Server replication. Review the replication status. Select Refresh to see the replicated VMs appear.
As the replication continues, the replication status shows progress. Continue refreshing periodically. After the initial replication finishes, hourly delta replications begin. The Migration status changes to Ready to migrate. The VMs can be migrated.
To track replication operations, select Jobs in your project. Failed scheduled replication cycles appear on Events. For more information, see Troubleshoot.
Important
During initial replication, Azure Catalyst creates a temporary seed disk for each source disk on the selected Azure Local storage path. It writes the replicated source data and subsequent changes to the seed disk. During migration, Azure Catalyst uses the seed disk to create the final disk attached to the migrated VM.
Don't rename, modify, or delete a seed disk. It remains part of the active replication and can be reused if migration is retried. Deleting it can cause replication or migration to fail and might require you to stop and enable replication again, which restarts initial replication. After you verify the migrated VM, use Complete migration to remove the protected item and its replication artifacts, including the seed disk. For more information, see the Azure Catalyst FAQ.
Next steps
- Complete VMware VM Migration.