Azure Migrate - Replication Enablement Failure (Error ID 322009 & 539) - Connectivity Issue with Internal IPs despite Public IP Configuration

Question

Azure Migrate - Replication Enablement Failure (Error ID 322009 & 539) - Connectivity Issue with Internal IPs despite Public IP Configuration

Bingxue Zhang 0

I am encountering an issue while using Azure Migrate to migrate GCP Compute Engine to Azure VM. Replication cannot be enabled, and I receive the following errors:

Error ID: 322009 Error Message: Replication could not be enabled.

Possible causes: The source machine is not reachable due to network connectivity issues between the process server (replication-070, IP: 10.0.0.5) and the source machine. Push installation of the Mobility Service failed with error code EP0866.

Error ID: 539 Error Message: The requested action couldn't be performed by the Replication Provider.

Key Details & What I Have Configured:

Source Environment: GCP Compute Engine
Azure Migrate Appliance: Configured and running
In the Azure Migrate appliance, under Physical server information, I explicitly provided the public IP address of the source GCP VM: 34.xx.xx.xx

However, the error message shows that the process server is attempting to connect to the GCP internal/private IPs of the source machine:

10.138.0.4
172.18.0.1
172.17.0.1

This mismatch appears to be the root cause — the replication service is ignoring/discarding the public IP I configured and is instead resolving or using the internal GCP network interfaces.

Error ID
Error Message
Possible causes
Recommendation
Related links
https://aka.ms/manualinstall
https://aka.ms/install-mobility-service-using-sccm
First Seen At
Error ID
Error Message
Possible causes
Recommendation
First Seen At

Bingxue Zhang 0

Error Message


Error ID
322009
Error Message
Replication could not be enabled.
Possible causes
      The source machine is not reachable due to network connectivity issues between process server (replication-070) and source machine (Name:  IP: 10.138.0.4,172.18.0.1,172.17.0.1).
      Push installation of the mobility service to the source machine (Name:  IP: 10.138.0.4,172.18.0.1,172.17.0.1) failed with error code EP0866. Either the source machine is not running, or there are network connectivity issues between the process server replication-070 (10.0.0.5) and the source machine.
Recommendation
      1. Ensure that the source machine (10.138.0.4,172.18.0.1,172.17.0.1) is running and has not been powered off.
      2. Ensure you are able to reach your source machine (10.138.0.4,172.18.0.1,172.17.0.1) from the appliance.
      3. In addition, the following is needed for push installation to complete successfully:
      a. Root credentials should be provided.
      b. SSH and SFTP services should be running.
      c. /etc/hosts on the source machine must contain entries for all IP addresses of the source machine.
      d. Ensure the source machine Linux variant is supported.
      
      OR You can install mobility service on the source machine through simple manual installation process (https://aka.ms/manualinstall) or by using Software deployment tools like SCCM (https://aka.ms/install-mobility-service-using-sccm)
Related links
https://aka.ms/manualinstall
https://aka.ms/install-mobility-service-using-sccm
First Seen At
2026/7/8 15:39:13
Error ID
539
Error Message
The requested action couldn't be performed by the Replication Provider.
Possible causes
The Provider action failed. Check other errors for more information.
Recommendation
Resolve the issue and retry the operation.
First Seen At
2026/7/8 15:39:14

Suchitra Suregaunkar 16,620 Reputation points Microsoft External Staff Moderator

2026-07-08T11:35:40.76+00:00

Hello Bingxue Zhang

Thank you for posting your query on Microsoft Q&A platform.

We are looking into this issue and will keep you posted updates.

Thanks,

Suchitra.
Suchitra Suregaunkar 16,620 Reputation points Microsoft External Staff Moderator

2026-07-08T11:44:03.99+00:00

Hello Bingxue Zhang

Could you confirm whether the source GCP VM is Linux or Windows?

Thanks,

Suchitra.
Suchitra Suregaunkar 16,620 Reputation points Microsoft External Staff Moderator

2026-07-08T12:15:01.0366667+00:00
Hello Bingxue Zhang

Based on the error message the Azure Migrate replication appliance (replication-070, 10.0.0.5) is attempting to reach the source GCP VM on the IPs the VM itself reports to the appliance the GCP internal NIC (10.138.0.4) and Docker bridges (172.17.0.1, 172.18.0.1).

Once the initial handshake is made, the appliance validates connectivity to all IPs the source machine advertises, which is why Recommendation 3(c) in your error requires /etc/hosts on the source machine to contain entries for all its IP addresses.

Because your appliance sits at 10.0.0.5 and has no L3 route to 10.138.x.x or 172.17/18.x.x, the push installer cannot reach the source, so replication fails with 322009, wrapped as 539.

The public IP (34.x.x.x) you provided is only used to initiate the SSH/SFTP session, it is not substituted for the private IPs during push-install validation.

As a resolution, Install the Mobility Service manually on the GCP VM:

For GCP → Azure agent-based migration, the supported path is manual Mobility Service installation. This skips the failing push-install validation completely.

Step 1 — Generate the passphrase on the replication appliance

On the appliance, open Command Prompt as Administrator:

cd %ProgramData%\ASR\home\svsystems\bin genpassphrase.exe -v > MobSvc.passphrase

Step 2 — Copy the installer + passphrase to the GCP VM

The Linux installers are under C:\ProgramData\ASR\home\svsystems\pushinstallsvc\repository on the appliance.

Copy the tarball matching your source OS along with MobSvc.passphrase to the GCP VM (SCP over the public IP is fine):

scp Microsoft-ASR_UA_Linux.tar.gz ******@34.xx.xx.xx:/tmp/ scp MobSvc.passphrase ******@34.xx.xx.xx:/tmp/

Step 3 — Install the Mobility Service on the source VM (as root)

cd /tmp tar -xvf Microsoft-ASR_UA_Linux.tar.gz sudo ./install -r MS -q

Step 4 — Register the agent to the appliance

/usr/local/ASR/Vx/bin/UnifiedAgentConfigurator.sh </span> -i <Replication_Appliance_IP> </span> -P /tmp/MobSvc.passphrase </span> -c CSLegacy

The source VM must be able to reach the appliance on TCP 443 and 9443 for registration to succeed. Please open outbound HTTPS from the GCP VPC to your appliance (via VPN, Interconnect, or a NAT'd public IP for the appliance).

Step 5 — Enable replication from the Azure portal

Go to Azure Migrate → Migration and modernization → Replicate, select the replication appliance, pick the GCP VM (it will appear as discovered), and enable replication. The portal will skip the push step since the agent is already registered.

Official references

Migrate GCP VMs to Azure [learn.microsoft.com]

About the Mobility Service — manual install via command prompt [learn.microsoft.com]

Troubleshoot Mobility Service push installation [learn.microsoft.com]

Migrate machines as physical servers to Azure [learn.microsoft.com]

Manual install shortlink — https://aka.ms/manualinstall

If the source VM is Windows instead of Linux, let me know and I'll share the equivalent UnifiedAgent.exe / UnifiedAgentConfigurator.exe commands.

Thanks,

Suchitra.
Suchitra Suregaunkar 16,620 Reputation points Microsoft External Staff Moderator

2026-07-09T06:53:24.5333333+00:00

Hello Bingxue Zhang

Please let us know if the suggested resolution helped/ addressed your concern. If it did, we’d appreciate your feedback on the proposed resolution as it helps others with similar issues.

If the resolution did not help, feel free to share more details about the challenge you’re still facing. Any additional information such as your current issue or specific errors will help us perform a deeper analysis and provide more targeted guidance.

We’re happy to continue assisting and work with you toward the right solution.

Thanks,

Suchitra.

1 answer

Your answer

Bingxue Zhang 0 Reputation points

2026-07-08T10:28:44.5766667+00:00

Error Message

Error ID 322009 Error Message Replication could not be enabled. Possible causes The source machine is not reachable due to network connectivity issues between process server (replication-070) and source machine (Name: IP: 10.138.0.4,172.18.0.1,172.17.0.1). Push installation of the mobility service to the source machine (Name: IP: 10.138.0.4,172.18.0.1,172.17.0.1) failed with error code EP0866. Either the source machine is not running, or there are network connectivity issues between the process server replication-070 (10.0.0.5) and the source machine. Recommendation 1. Ensure that the source machine (10.138.0.4,172.18.0.1,172.17.0.1) is running and has not been powered off. 2. Ensure you are able to reach your source machine (10.138.0.4,172.18.0.1,172.17.0.1) from the appliance. 3. In addition, the following is needed for push installation to complete successfully: a. Root credentials should be provided. b. SSH and SFTP services should be running. c. /etc/hosts on the source machine must contain entries for all IP addresses of the source machine. d. Ensure the source machine Linux variant is supported. OR You can install mobility service on the source machine through simple manual installation process (https://aka.ms/manualinstall) or by using Software deployment tools like SCCM (https://aka.ms/install-mobility-service-using-sccm) Related links https://aka.ms/manualinstall https://aka.ms/install-mobility-service-using-sccm First Seen At 2026/7/8 15:39:13 Error ID 539 Error Message The requested action couldn't be performed by the Replication Provider. Possible causes The Provider action failed. Check other errors for more information. Recommendation Resolve the issue and retry the operation. First Seen At 2026/7/8 15:39:14
Suchitra Suregaunkar 16,620 Reputation points Microsoft External Staff Moderator

2026-07-08T11:35:40.76+00:00

Hello Bingxue Zhang

Thank you for posting your query on Microsoft Q&A platform.

We are looking into this issue and will keep you posted updates.

Thanks,

Suchitra.
Suchitra Suregaunkar 16,620 Reputation points Microsoft External Staff Moderator

2026-07-08T11:44:03.99+00:00

Hello Bingxue Zhang

Could you confirm whether the source GCP VM is Linux or Windows?

Thanks,

Suchitra.
Suchitra Suregaunkar 16,620 Reputation points Microsoft External Staff Moderator

2026-07-09T06:53:24.5333333+00:00

Hello Bingxue Zhang

Please let us know if the suggested resolution helped/ addressed your concern. If it did, we’d appreciate your feedback on the proposed resolution as it helps others with similar issues.

If the resolution did not help, feel free to share more details about the challenge you’re still facing. Any additional information such as your current issue or specific errors will help us perform a deeper analysis and provide more targeted guidance.

We’re happy to continue assisting and work with you toward the right solution.

Thanks,

Suchitra.

Answer 1

hi Bingxue Zhang & thx for sharing urs issue here at Q&A portal,

The important part is that 322009 is just the top-level replication failure. The real issue is EP0866, which means the Mobility Service push installation couldn't reach the source machine. From ur description, it sounds like Azure Migrate is discovering multiple NICs on the GCP VM and selecting one of the private addresses (10.138.x.x, 172.17.x.x, 172.18.x.x) instead of the public IP for the push installation.

I'd verify what IP Azure Migrate has actually inventoried for the machine. If the discovered machine still shows the private IP as its primary address, changing the "Physical server information" afterward may not change what the replication provider uses. One workaround is to install the Mobility Service manually instead of relying on push installation https://aka.ms/manualinstall

If the appliance still tries to use the private IP after a fresh discovery or manual Mobility Service installation, this starts looking like a product issue rather than a configuration problem. I'd open a support case and include the appliance logs, the discovered machine inventory, the configured public IP, and the timestamps of the failed enable-replication operation. The Azure Migrate team can verify why the replication provider is resolving the internal GCP addresses instead of the public endpoint.

rgds,

Alex

&

If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal

and at my blog https://ctrlaltdel.blog/

Azure Migrate - Replication Enablement Failure (Error ID 322009 & 539) - Connectivity Issue with Internal IPs despite Public IP Configuration

Official references

1 answer

Your answer