Azure Migrate - Create Deployment failed during Execute Migration (Microsoft.MigrateV2-ExecuteMigrate-InMageRcm)

Question

Azure Migrate - Create Deployment failed during Execute Migration (Microsoft.MigrateV2-ExecuteMigrate-InMageRcm)

Bingxue Zhang 0

Migration execution fails with "Create Deployment" error when starting replication for GCP Linux servers. The ARM deployment Microsoft.MigrateV2-ExecuteMigrate-InMageRcm-20266711747 fails with status "Failed".

Problem Description:

I am performing a migration from GCP Linux VMs to Azure using Azure Migrate (agent-based physical server migration).

Discovery and Replication Appliance have been configured successfully.
When starting the migration (Enable Replication / Execute Migration), the operation fails at the ARM deployment stage.

Error Details:

Operation Name: Microsoft.Resources/deployments/write (Create Deployment)
Deployment Name: Microsoft.MigrateV2-ExecuteMigrate-InMageRcm-20266711747
Resource Group: rg-team-5027
Subscription ID: 12db6123-271d-410c-b072-c765def73661
Status: Failed
Event Timestamp: 2026-07-07T03:44:39ZMigration execution fails with "Create Deployment" error when starting replication for GCP Linux servers. The ARM deployment Microsoft.MigrateV2-ExecuteMigrate-InMageRcm-20266711747 fails with status "Failed". Problem Description: I am performing a migration from GCP Linux VMs to Azure using Azure Migrate (agent-based physical server migration).
- Discovery and Replication Appliance have been configured successfully.
- When starting the migration (Enable Replication / Execute Migration), the operation fails at the ARM deployment stage.
Error Details:
- Operation Name: Microsoft.Resources/deployments/write (Create Deployment)
- Deployment Name: Microsoft.MigrateV2-ExecuteMigrate-InMageRcm-20266711747
- Resource Group: rg-team-5027
- Subscription ID: 12db6123-271d-410c-b072-c765def73661
- Status: Failed
- Event Timestamp: 2026-07-07T03:44:39Z

The only error message from the deployment:


{
  "code": "322009",
  "message": "Replication could not be enabled."
}

I require support for Azure Migrate; further information can be found in the attachment below:

deployment_operations.txt

deployment.txt

Ravi Varma Mudduluru 12,535 Reputation points Microsoft External Staff Moderator

2026-07-08T01:34:36.08+00:00

Hello @Bingxue Zhang

Thank you for contacting us about the Azure Migrate issue. We have begun looking into it and will share our suggestions with you as soon as possible.

1 answer

Your answer

Ravi Varma Mudduluru 12,535 Reputation points Microsoft External Staff Moderator

2026-07-08T01:34:36.08+00:00

Hello @Bingxue Zhang

Thank you for contacting us about the Azure Migrate issue. We have begun looking into it and will share our suggestions with you as soon as possible.

Answer 1

Hello @Bingxue Zhang ,

Thank you for reaching out to Microsoft Q&A.

I understand you're hitting a "Create Deployment" failure with error code 322009 ("Replication could not be enabled") when trying to start replication for your GCP Linux VMs using the agent-based method in Azure Migrate.

This error is fairly common in agent-based (InMageRcm) flows for GCP/physical servers. It usually means the ARM deployment that creates the target Azure resources (VM, disks, NIC, etc.) is failing for a specific reason, even though discovery and the replication appliance look healthy.

Please check the inner deployment error. In the Azure portal:

Go to your target Resource Group (rg-team-5027) → Deployments → open the failed deployment (Microsoft.MigrateV2-ExecuteMigrate-InMageRcm-20266711747).
Review the Operation details for the exact failed resource and message (e.g., permissions, quota, policy, VM SKU, or network issues).

You can also run this Azure CLI command for a quick summary:

az deployment operation group list --resource-group your RG name --name Microsoft.MigrateV2-ExecuteMigrate-InMageRcm-20266711747 --query "[?properties.provisioningState=='Failed']" -o table

Common Fixes to try:

Permissions: Ensure your account (and the Azure Migrate service) has Contributor on the target RG, plus Virtual Machine Contributor + Network Contributor on the target VNet.
Quotas & SKU Availability: Check vCPU, disk, and NIC quotas in the target region. Confirm the selected target VM size is available.
Azure Policy: Look for any deny policies affecting the target RG (regions, SKUs, tags, disk types, etc.).
Target Settings: In the Azure Migrate project, double-check the Compute + Network settings match your source (disk layout, VNet/Subnet in the same region, supported OS disk type).
Source Agent Health: Verify the Mobility service on the GCP Linux VMs shows a healthy heartbeat and the replication appliance is Connected.

Once you apply the fix from the detailed error, retry Enable Replication.

Reference Document:

Migrate physical servers / GCP VMs as physical servers

If the inner error isn't clear or the issue continues after these checks, feel free to check the private message and share the requested details there to investigate further.

If the answer is helpful, please click "Accept Answer" it. If you have extra questions about this answer, please click "Comment".