Azure Migrate Error 110099 – Migration couldn't be enabled for the virtual machine

Question

Azure Migrate Error 110099 – Migration couldn't be enabled for the virtual machine

Cristian Admin 0

Migration couldn't be enabled for the virtual machine. (Code: 110099)

I am migrating VMware VMs to Azure using Azure Migrate (agentless migration).

Issue: When I select a discovered VMware VM and start replication, Azure Migrate fails with the following error:

Migration couldn't be enabled for the virtual machine. (Code: 110099)

Environment:

Source: VMware vSphere
Migration method: Azure Migrate (agentless)
Azure Migrate appliance deployed and discovery is working
VM appears under discovered servers
VDDK 8.0 installed on the appliance
Site-to-Site VPN connectivity in place
Recovery Services Vault and storage account permissions have been reviewed
Previous vault permission error (28143) was resolved by recreating the storage account and reassigning permissions

Current behavior:

Discovery succeeds and the VM can be added for migration.
After starting replication, the VM does not appear under Replicating Machines.
The Azure portal shows Migration couldn't be enabled for the virtual machine (Code: 110099).
No migration progress is shown under Migration Status.

Troubleshooting completed:

Verified appliance connectivity and health.
Confirmed VDDK is installed.
Verified Recovery Services Vault access to the storage account.
Recreated the storage account and reassigned required RBAC roles.
VM is visible in Discovery but replication does not start.

Has anyone encountered Error 110099 and identified the root cause? Are there any logs or specific VMware VM configuration settings I should check?I am migrating VMware VMs to Azure using Azure Migrate (agentless migration).

Issue: When I select a discovered VMware VM and start replication, Azure Migrate fails with the following error:

Migration couldn't be enabled for the virtual machine. (Code: 110099)

Environment:

Source: VMware vSphere
Migration method: Azure Migrate (agentless)
Azure Migrate appliance deployed and discovery is working
VM appears under discovered servers
VDDK 8.0 installed on the appliance
Site-to-Site VPN connectivity in place
Recovery Services Vault and storage account permissions have been reviewed
Previous vault permission error (28143) was resolved by recreating the storage account and reassigning permissions

Current behavior:

Discovery succeeds and the VM can be added for migration.
After starting replication, the VM does not appear under Replicating Machines.
The Azure portal shows Migration couldn't be enabled for the virtual machine (Code: 110099).
No migration progress is shown under Migration Status.

Troubleshooting completed:

Verified appliance connectivity and health.
Confirmed VDDK is installed.
Verified Recovery Services Vault access to the storage account.
Recreated the storage account and reassigned required RBAC roles.
VM is visible in Discovery but replication does not start.

Has anyone encountered Error 110099 and identified the root cause? Are there any logs or specific VMware VM configuration settings I should check?

VEMULA SRISAI 14,065 Reputation points Microsoft External Staff Moderator

2026-08-29T01:55:11.63+00:00
Hello Cristian Admin,

Based on the information provided, the issue is likely not related to discovery, storage account access, or appliance health, as those validations have already been completed successfully. The error 110099 typically occurs when Azure Migrate is unable to create the replication item for the selected VM during the enable-replication phase.

Recommended Resolution:

Verify that the source VMware VM does not have:

Independent disks

Raw Device Mapping (RDM) disks

Invalid or orphaned snapshots

Unsupported disk configurations

Remove any existing failed migration entries for the VM (if present) and re-attempt replication. Revalidate VMware connectivity from the Azure Migrate appliance and ensure the appliance can access all VMDK files associated with the VM.

Review the Recovery Services Vault jobs and Azure Migrate appliance logs for detailed replication enablement errors. The underlying failure is often logged there even when the portal only displays Error 110099.

If the issue persists, collect the Azure Migrate appliance logs and review the failed operation corresponding to: Microsoft.RecoveryServices/vaults/replicationFabrics/replicationProtectionContainers/replicationMigrationItems/write as this is the operation currently failing during replication enablement.

Please check the VMware VM disk configuration and appliance logs first, as these are the most common causes when discovery succeeds but replication cannot be enabled. If you can provide the detailed failure message from the Recovery Services Vault job or appliance logs, we can help identify the exact root cause.
Cristian Admin 0 Reputation points

2026-08-31T13:06:33.0066667+00:00

Hi @VEMULA SRISAI please see attached json file. appliance.txt

2 answers

Your answer

VEMULA SRISAI 14,065 Reputation points Microsoft External Staff Moderator

2026-08-29T01:55:11.63+00:00

Hello Cristian Admin,

Based on the information provided, the issue is likely not related to discovery, storage account access, or appliance health, as those validations have already been completed successfully. The error 110099 typically occurs when Azure Migrate is unable to create the replication item for the selected VM during the enable-replication phase.

Recommended Resolution:

Verify that the source VMware VM does not have:

Independent disks

Raw Device Mapping (RDM) disks

Invalid or orphaned snapshots

Unsupported disk configurations

Remove any existing failed migration entries for the VM (if present) and re-attempt replication. Revalidate VMware connectivity from the Azure Migrate appliance and ensure the appliance can access all VMDK files associated with the VM.

Review the Recovery Services Vault jobs and Azure Migrate appliance logs for detailed replication enablement errors. The underlying failure is often logged there even when the portal only displays Error 110099.

If the issue persists, collect the Azure Migrate appliance logs and review the failed operation corresponding to: Microsoft.RecoveryServices/vaults/replicationFabrics/replicationProtectionContainers/replicationMigrationItems/write as this is the operation currently failing during replication enablement.

Please check the VMware VM disk configuration and appliance logs first, as these are the most common causes when discovery succeeds but replication cannot be enabled. If you can provide the detailed failure message from the Recovery Services Vault job or appliance logs, we can help identify the exact root cause.
Cristian Admin 0 Reputation points

2026-08-31T13:06:33.0066667+00:00

Hi @VEMULA SRISAI please see attached json file. appliance.txt

Answer 1

Stephen Normandin 1

@Cristian Admin @VEMULA SRISAI @Vinodh247-1375 I am having this same issue. What was the resolution in this case?

0 comments

Answer 2

Vinodh247-1375 44,801 Volunteer Moderator

Hi ,

Thanks for reaching out to Microsoft Q&A.

Error 110099 is typically a failure during the replication enablement stage, rather than VM discovery. Since the VM is discovered successfully but never appears under Replicating Machines, the issue is most likely occurring when Azure Migrate attempts to configure replication.

I recommend checking the Azure Migrate appliance logs immediately after reproducing the error to identify the underlying failure. Also verify that the VMware VM does not use any unsupported configurations such as:

Independent or non-persistent disks
Raw Device Mappings (RDMs)
Unsupported disk controllers
Existing snapshots or other unsupported storage configurations

As an isolation test, try enabling replication for a different small VMware VM with a standard configuration. If that VM replicates successfully, the issue is likely specific to the original VM. If multiple VMs fail with the same error, review appliance health, vCenter permissions, VMware connectivity, and the Azure Migrate target configuration.

Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution.

Cristian Admin 0 Reputation points

2026-08-26T12:54:36.0066667+00:00
Cristian Admin 0 Reputation points

2026-08-26T12:56:18.8633333+00:00

I verified everything you stated please see above screenshot. Also i tried to execute 1 standard VM and it's same issue.
Vinodh247-1375 44,801 Reputation points Volunteer Moderator

2026-08-31T16:23:33.8466667+00:00

Because multiple unrelated VMs fail at the exact moment replication is enabled, I would investigate:

Azure Migrate appliance -> replication service -> Recovery Services Vault/backend communication

rather than VMDK configuration.

If you can paste the Activity Log entry for the 110099 failure (especially the Status reason/details) and the relevant appliance log entry immediately after clicking Start replication, I can try to narrow down the issue.
Cristian Admin 0 Reputation points

2026-09-02T14:51:30.66+00:00

Please see below text file contains the log.

Errortxt.txt