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

Question

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: PII removed
Status: Failed
Event Timestamp: 2026-07-07T03:44:39Z

Replication could not be enabled. (代码: 322009)

Lakshma Reddy Vattijonnala 1,005 Reputation points Microsoft External Staff Moderator

2026-07-07T06:59:25.3233333+00:00

Hi @Bingxue Zhang Thank you for reaching out to Microsoft Q&A. We are looking into the issue and we will get back to you shortly with an update

1 answer

Your answer

Lakshma Reddy Vattijonnala 1,005 Reputation points Microsoft External Staff Moderator

2026-07-07T06:59:25.3233333+00:00

Hi @Bingxue Zhang Thank you for reaching out to Microsoft Q&A. We are looking into the issue and we will get back to you shortly with an update

Answer 1

Hi Bingxue Zhang& thx for join me here at Q&A portal,

This error is too high-level to find the real cause.

Create Deployment only says the ARM deployment failed. It doesn’t tell why replication failed. The real error is usually inside the deployment operation details or the Azure Migrate job details.

Ask them to check

Azure Portal > Resource group rg-team-5027 > Deployments > Microsoft.MigrateV2-ExecuteMigrate-InMageRcm-20266711747 > Operation details

That should show the actual failed resource and message. For GCP Linux agent-based migration, common causes are missing permissions, unsupported Linux/kernel config, agent install issues, appliance connectivity, target region/quota, or disk/network settings. https://learn.microsoft.com/azure/migrate/tutorial-migrate-physical-virtual-machines & https://learn.microsoft.com/azure/migrate/troubleshoot-changed-block-tracking-replication may help u.

If the inner deployment error only shows code 322009 with no useful details, this needs Azure Migrate support. Include the migration project, machine name, job ID, deployment name, timestamp, and correlation ID.

rgds,

Alex &

pls if my answer was helpfull mark it as an answer & follow me here and at my blog https://ctrlaltdel.blog/