Azure migrate error (Gcp to azure )

Question

Azure migrate error (Gcp to azure )

Niveditha Manjegowda 0

Hello team.

we are trying to migrate GCP servers to azure VM. agent based migration
we have successfully created project
we have successfully installed replication appliance and registered

we have installed mobility agent on gcp (source) servers which needs to be migrated. while the agent is getting installed successfully. during replication the VM discovered with below error.
**"Machine not discovered with selected appliance "
PFA, screenshot . error.png
if anyone have experienced or aware of this pls do comment **

Bharath Y P 10,450 Reputation points Microsoft External Staff Moderator

2026-06-24T14:22:11.0133333+00:00
Hello Niveditha Manjegowda, It sounds like you’ve got the Azure Migrate project created the replication appliance deployed/registered, and the Mobility Agent installed on your GCP source VMs, but during replication the system reports: “Machine not discovered with selected appliance”

For GCP-to-Azure migrations, this specific symptom typically means the VM the Migration service is trying to replicate isn’t being seen/associated with the configuration/appliance that’s registered in the Azure Migrate project. Based on the troubleshooting guidance for GCP migrations, here are the most relevant checks:

This error is almost always an association/registration mismatch, not an agent install failure. The VM's Mobility Agent must be registered to the exact same replication appliance that you select in the Migration and modernization → Replicate wizard. Common triggers:

Wrong / mismatched passphrase — the Mobility Agent was registered using a passphrase that doesn't match the replication appliance currently selected (e.g., appliance was reinstalled, or you have more than one appliance).

Multiple / stale replication appliances in the same project — you pick appliance A in the portal, but the agent registered to appliance B.

Agent registered to the appliance but the appliance hasn't pushed the machine up to the project yet (registration to the appliance's CS process didn't complete), so the portal's machine list doesn't contain it.

Connectivity gap between the GCP VM and the appliance on the required ports, so the heartbeat/registration never reaches the appliance.

Key context for your case (Windows + GCP)

Internal guidance clearly distinguishes between:

Azure Migrate Discovery & Assessment appliance (inventory/discovery)

Replication Appliance (ASR-based / classic flow) used for agent-based migration

Mixing these leads to issues like your error (machine not discovered)

Two things to verify first for GCP:

GCP (and AWS) use the classic Replication Appliance (MicrosoftAzureSiteRecoveryUnifiedSetup.exe), not the modern Azure Migrate appliance — confirm you're in Migration and modernization → Replicate → "Machines are not virtualized / Other (AWS, GCP…)".

The passphrase used to register the agent must match the appliance. On the appliance run: C:\ProgramData\ASR\home\svsystems\bin\genpassphrase.exe -v and re-register the agent with that passphrase: UnifiedAgentConfigurator.exe /CSEndPoint <ApplianceIP> /PassphraseFilePath <passphrase.txt>

Then confirm there are no duplicate/stale replication appliances in the project, and that TCP 443 + 9443 are open from the GCP VM to the appliance (check GCP VPC firewall). Re-run Replicate afterward. If it still fails, share the registration error from %ProgramData%\Microsoft Azure\Logs on the appliance.

To pinpoint it, could you confirm:

Exactly how many replication appliances exist in this project, and are you selecting the one the agent registered to?

Did you retrieve and use the passphrase from genpassphrase.exe -v on that specific appliance?

Are 443 and 9443 open from the GCP Windows VM to the appliance (GCP VPC firewall + any NVA)?

What does the Mobility Agent registration log (%ProgramData%\ASR\Agent\) show success or a CS-endpoint/connection error?

Windows Server version of the source VM (to confirm a supported OS and correct installer).

Hope this helps! If you encounter still facing issues, please do us let us know. Thanks.
Suchitra Suregaunkar 16,620 Reputation points Microsoft External Staff Moderator

2026-06-30T01:20:30.26+00:00

Hello Niveditha Manjegowda,

Could you please let us know if the comment above resolved your issue? If you need any further assistance, feel free to reach out—we're always here to support you.

If you found the comment helpful, please consider clicking "Upvote it."

Thanks,
Suchitra.
Niveditha Manjegowda 0 Reputation points

2026-06-30T05:39:44.4266667+00:00

its a bug from Microsoft end , post raising a ticket Microsoft engineer confirmed PG team is fixing it
Suchitra Suregaunkar 16,620 Reputation points Microsoft External Staff Moderator

2026-07-03T00:13:58.8833333+00:00

Hello Niveditha Manjegowda,

Could you please let us know if your issue has been resolved?

3 answers

Your answer

Suchitra Suregaunkar 16,620 Reputation points Microsoft External Staff Moderator

2026-06-30T01:20:30.26+00:00

Hello Niveditha Manjegowda,

Could you please let us know if the comment above resolved your issue? If you need any further assistance, feel free to reach out—we're always here to support you.

If you found the comment helpful, please consider clicking "Upvote it."

Thanks,
Suchitra.
Niveditha Manjegowda 0 Reputation points

2026-06-30T05:39:44.4266667+00:00

its a bug from Microsoft end , post raising a ticket Microsoft engineer confirmed PG team is fixing it
Suchitra Suregaunkar 16,620 Reputation points Microsoft External Staff Moderator

2026-07-03T00:13:58.8833333+00:00

Hello Niveditha Manjegowda,

Could you please let us know if your issue has been resolved?

Answer 1

Welcome to Microsoft Q&A

Hello @Niveditha Manjegowda I hope you are doing well,

Azure Migrate requires the appliance to send a heartbeat to Azure confirming that the specific VM is tied to it. If the portal does not receive this association telemetry, it throws the "Machine not discovered with selected appliance" error.

Check please the following things:

Manually re-register the Windows agent: The silent or GUI installer sometimes fails the final registration step without throwing a hard error. On your GCP Windows server, open an elevated Command Prompt, navigate to the agent installation path (usually C:\Program Files (x86)\Microsoft Azure Site Recovery\agent), and manually run the configuration tool: UnifiedAgentConfigurator.exe -i <Appliance_IP> -P <Passphrase_File_Path>

Verify internal communications: Ensure that the Windows Defender Firewall on the guest OS, as well as your GCP VPC Firewall rules, are explicitly allowing outbound traffic on ports 443 and 9443 from the source VM directly to the Replication Appliance's IP address.

Inspect the Configurator Log: If manual registration fails, check the logs located at C:\ProgramData\ASRSetupLogs\ASRUnifiedAgentConfigurator.log. Look specifically for time synchronization errors (the VM and appliance must have matched clocks) or TLS/certificate rejections.

Allow Cloud Sync Time: Once the agent is successfully registered to the appliance, it can take 15 to 30 minutes for the appliance to push that discovery data up to the Azure portal. Wait at least 15 minutes after a successful registration before trying to enable replication.

References

If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find solutions more easily.

Niveditha Manjegowda 0 Reputation points

2026-06-23T15:14:41.2666667+00:00

Hi , thank you for the update! Is it possible to connect with me quickly. so, i can show you the environment
Jose Benjamin Solis Nolasco 10,891 Reputation points Volunteer Moderator

2026-06-23T15:31:23.2733333+00:00

@Niveditha Manjegowda Hey I hope you are doing well, I'm not allow to connect to customer enviroment, however is posible someone from support will write you via private message if you need futher help.
Niveditha Manjegowda 0 Reputation points

2026-06-23T15:34:08.61+00:00

Hi Jose , yes please we need someone to help us practically. we been stuck for a week now . we will not show customer environment . we can just give brief of the problem

Answer 2

Niveditha Manjegowda 0

we have already tried the above still not working
its windows server

0 comments

Answer 3

The error "Machine not discovered with selected appliance" during GCP→Azure agent-based migration indicates that Azure Migrate doesn’t see the source VM as correctly associated with the replication appliance.

Check the following in order:

Mobility agent installation and registration
- Confirm the Mobility service agent is installed on each GCP VM using one of the supported methods (SCCM, Azure Arc + custom script, manual install).
- On Linux, verify the install and registration commands completed successfully, for example:
  - Extract installer tarball and run:
```
       mkdir /tmp/MobSvcInstaller
       tar -C /tmp/MobSvcInstaller -xvf <Installer tarball>
       cd /tmp/MobSvcInstaller
       sudo ./install -r MS -v VmWare -q -c CSLegacy
```
  - Register the agent with the replication appliance:
```
       /usr/local/ASR/Vx/bin/UnifiedAgentConfigurator.sh -i <replication appliance IP address> -P <Passphrase File Path>
```
- Ensure the agent is registered to the same replication appliance that is selected in the Azure Migrate project.
Replication appliance health and configuration
- Verify the replication appliance meets requirements (OS version, MySQL installed, URLs reachable).
- Confirm the appliance was set up from the correct Azure Migrate project and region:
  - In the Azure Migrate project: Servers, databases, and web apps → Migration and modernization → Discover → Not virtualized/Other → correct Target region → Create resources → Install a replication appliance.
- Make sure there are no stale or duplicate replication appliances connected to the same project, as this can cause discovery/association issues.
Network connectivity and firewall rules
- Ensure there is a network path between each GCP VM and the replication appliance.
- Open required ports on the appliance and any intervening firewalls:
  - TCP 9443 and HTTPS 443 for data transport and control traffic.
- Verify that private endpoints (if used) are reachable from the appliance.
Azure Migrate appliance and project association
- Confirm that the appliance used for migration is the one selected in the Azure Migrate portal for these machines. If the VM was registered to a different appliance or project, it will show as "Machine not discovered with selected appliance".
Re‑validate discovery
- After confirming agent registration and connectivity, re-run discovery/refresh in the Azure Migrate portal for Replicating servers.
- If the issue persists, check appliance logs under %ProgramData%\Microsoft Azure\Logs for registration or connectivity errors.

If any of the above checks fail (agent not registered, wrong appliance, blocked ports, duplicate appliances), correct that configuration and then retry replication; the VM should then be discovered correctly with the selected appliance.

References: