Share via

Azure Migrate – Discovery Failed (Error 60001) Blocking Replication in Cross-Tenant Migration

Fatimaezzahra A. MobiArchitects 0 Reputation points
2026-02-03T08:49:09.18+00:00

Hello everyone,

I am currently working on the migration of virtual machines (Linux and Windows) from Azure tenant A to Azure tenant B, using Azure Migrate (this approach was recommended by a Microsoft expert).

Here is the situation:

  • I deployed an Assessment and Replication Appliance VM in the source tenant.

I added the VMs to be migrated in the discovery phase.

On the appliance VM, the VM discovery completes successfully.

However, in Azure Migrate, the discovery status always shows Failed with error code 60001.

Microsoft support advised us that, in our case, the assessment step and error 60001 can be ignored, since the source workloads are already Azure virtual machines, and recommended proceeding directly to the replication phase.

Based on this guidance:

We deployed a Replication Appliance VM.

However, the discovery for replication also fails, and as a result, we are unable to start the VM replication.

Has anyone encountered a similar issue or worked on a cross-tenant Azure-to-Azure migration using Azure Migrate in this context? Any guidance, experience, or suggestions would be greatly appreciated.

Thank you in advance for your help.

Azure Migrate
Azure Migrate

A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2026-02-03T09:56:19.7933333+00:00

    Hi @Fatimaezzahra A. MobiArchitects

    Error 60001 in Azure Migrate indicates that the appliance-based discovery handshake did not complete successfully. While Microsoft Support is correct that assessment is not required when the source workloads are already Azure virtual machines, replication cannot bypass discovery, and this is where the confusion commonly arises in Azure-to-Azure cross-tenant scenarios.

    It is important to clarify a key architectural point:

    Azure Migrate appliances are designed primarily for on-premises VMware and Hyper-V discovery and migration. They are not the recommended or supported mechanism for Azure-to-Azure cross-tenant VM migrations. In cross-tenant Azure scenarios, persistent discovery failures (including error 60001) are frequently expected behavior, not misconfiguration.

    Although Azure Migrate can register Azure VMs for assessment, the replication workflow still depends on appliance-based infrastructure discovery, which assumes on-premises connectivity models (guest-based WinRM/SSH access, credential validation, and local runspace creation). These assumptions often do not hold true for Azure-to-Azure and especially cross-tenant environments, even when basic VM connectivity is confirmed.

    As a result:

    Skipping assessment does not remove the replication discovery requirement.

    Repairing or redeploying the appliance does not address the underlying design limitation.

    Error 60001 in this context does not reliably indicate a networking or credential issue.

    For Azure-to-Azure cross-tenant virtual machine migration, Microsoft’s supported solution is:

    Azure Site Recovery (ASR)–based replication, configured directly between the source and target tenants.

    With Azure Site Recovery:

    No Azure Migrate appliance discovery is required.

    Replication operates at the Azure platform level.

    Cross-tenant scenarios are supported through appropriate role assignments in the target tenant.

    Appliance discovery errors such as 60001 are avoided entirely.

    Summary

    • Error 60001 occurs because Azure Migrate appliance discovery is not designed for Azure-to-Azure cross-tenant replication.
    • Assessment can be skipped, but replication discovery cannot.
    • This behavior is expected and not a configuration defect.
    • Azure Site Recovery is the supported and recommended solution for cross-tenant Azure VM migrations.

    Reference

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.