Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
Azure Migrate VMware Migration Fails with Error 110099 Even After Fixing Recovery Services Vault Storage Permissions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(73.60000000000001, 5%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECA%3C/text%3E%3C/svg%3E)
Cristian Admin
0
Reputation points
Hello,
I am attempting to migrate a VMware VM (ADMINSVR) to Azure using Azure Migrate (agentless VMware migration).
Environment:
- Azure Migrate project created successfully.
- VM is discovered successfully in Azure Migrate.
- Azure Migrate appliance diagnostics show all prerequisite, service health, Azure-specific, and appliance-specific checks as passed.
- Recovery Services Vault managed identity is enabled.
- Storage account networking is configured to allow public access from all networks.
- The Recovery Services Vault managed identity has been granted:
- Contributor
- Storage Blob Data Contributor
Error 28143
Recovery Services vault does not have permission to access storage account migrationtest4800
To troubleshoot:
- Deleted the original storage account.
- Recreated the storage account with the same name.
- Assigned the Recovery Services Vault managed identity:
- Contributor
- Storage Blob Data Contributor
- Verified storage account creation completed successfully.
- Contributor
- Verified appliance diagnostics are healthy.
Current issue:
The migration still fails with:
Error Code: 110099
Migration couldn't be enabled for the virtual machine.
Activity Log details show:
Microsoft.RecoveryServices/vaults/replicationFabrics/
replicationProtectionContainers/
replicationMigrationItems/write
Status: Failed
Code: 110099
Message: Migration couldn't be enabled for the virtual machine.
Azure Migrate
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(233.6, 85%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVS%3C/text%3E%3C/svg%3E)
VEMULA SRISAI 13,895 Reputation points Microsoft External Staff Moderator2026-08-29T01:58:38.09+00:00 Hello Cristian Admin,
Thank you for the detailed information and troubleshooting steps provided.
Based on the information shared, the original storage access issue (Error 28143 - Recovery Services Vault does not have permission to access the storage account) appears to have been resolved after recreating the storage account and assigning the required permissions to the Recovery Services Vault managed identity.
Since the deployment creation now completes successfully and the failure occurs during the operation:
Microsoft.RecoveryServices/vaults/replicationFabrics/replicationProtectionContainers/replicationMigrationItems/writewith Error 110099, the issue is no longer related to storage account access. Instead, the failure is occurring during the replication enablement phase when Azure Migrate attempts to create the migration/replication item for the VMware VM.
We recommend the following:
- Stop and re-enable replication for the VM to ensure there is no stale migration metadata remaining from the previous failed attempt.
- Review Azure Activity Logs for any policy-related deployment failures or denied operations that may be preventing the migration item from being created.
- Validate the VMware VM configuration, including disk configuration, snapshots, and Changed Block Tracking (CBT) health.
- Review the Azure Migrate appliance logs for any underlying provider-level errors that may not be surfaced in the Azure portal.
- As a test, attempt to enable replication for another VMware VM discovered by the same appliance. If the test VM succeeds, the issue is likely specific to the ADMINSVR virtual machine.
If the issue persists after the above validation, please provide the Migration Project name, Recovery Services Vault name, Subscription ID, and the Correlation ID from the failed Activity Log operation so that further investigation can be performed.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(70.4, 19%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
CharlesP 61 Reputation points2026-09-02T17:38:08.04+00:00 I'm running into this problem as well. Did you find a solution to this?
Sign in to comment
1 answer
Sort by: Most helpful
-
Cristian Admin 0 Reputation points
2026-08-25T18:22:20.0966667+00:00 -
Cristian Admin 0 Reputation points
2026-08-25T18:26:39.1933333+00:00 Update: The original error 28143 (Recovery Services vault does not have permission to access storage account) appears to be resolved. Actions performed:
- Recreated storage account migrationtest4800.
- Assigned Recovery Services Vault managed identity:
- Contributor
- Storage Blob Data Contributor
- Verified storage account creation completed successfully.
- Azure Migrate Appliance Diagnostics Report shows all checks passed.
- Deployment creation now succeeds. Current failure: Operation: Microsoft.RecoveryServices/vaults/replicationFabrics/replicationProtectionContainers/replicationMigrationItems/write Status: Failed Error: 110099 Message: Migration couldn't be enabled for the virtual machine. No Replicated Items are created in the Recovery Services Vault and no additional provider-level error is exposed in Azure Migrate, Action Center, or Activity Log. What logs or provider diagnostics can be used to determine the underlying cause behind error 110099?
Sign in to comment -