Share via

Migrate AWS VM to azure VM using azure migrtate

Neeraj Sharma 1 Reputation point
2026-02-13T07:05:29.13+00:00

Hi,

I am created a new VM in AWS for discovery and added my all the appliance in that and can see the discovered VM in azure migrate.

After that, i created the assessment , then wave planning for lift and shift , not I am not able to replicate it as its not showing any VM in replicate.

on wave execution, it ask me to install DRappliance.zip on appliance VM and when i go each server for installing it, it shows me that service is already running.

Please guide me the further steps for the same.

Azure Migrate
Azure Migrate

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

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Siva shunmugam Nadessin 5,950 Reputation points Microsoft External Staff Moderator
    2026-02-13T11:24:01.99+00:00

    Hello Neeraj Sharma,

    Thank you for reaching out to the Microsoft Q&A forum.

    It sounds like you’re facing some challenges with the replication process in Azure Migrate after discovering your AWS VM. Here’s a step-by-step guide that might help you move forward:

    Check Installation of the Mobility Service: Ensure that the Mobility service agent is correctly installed on your AWS VM. It seems like the installation is detecting that the service is already running, which might indicate that it's already installed but perhaps not set up correctly.

    Verify Project Configuration: Go to your Azure Migrate project settings and double-check that everything is configured properly. Ensure that the necessary permissions are set and the project is correctly associated with the Azure resources you intend to use.

    Remove and Re-Register: If you're still having issues, try uninstalling the Mobility service from the appliance VM and reinstalling it. This could clear up any inconsistencies. After reinstallation, make sure to register it again with your Azure Migrate project.

    Group Replication: Remember that you can only replicate up to 10 machines at once. If you have more than that, try grouping them and replicating in smaller batches.

    Troubleshoot Connectivity Issues: Ensure that there are no connectivity issues between your AWS VM and the Azure Migrate services. Sometimes firewall settings or network configurations can create obstacles.

    Review Logs: Check the logs generated by the Azure Migrate appliance for any specific errors or warnings. They can provide valuable insights into what might be going wrong.

    Hope this helps you get your migration on track! If you run into more issues, feel free to provide additional details, and we can dig deeper into it.

    References:

     

  2. Q&A Assist
    2026-02-13T07:05:43.08+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    To troubleshoot the issue with replicating your AWS VM to Azure using Azure Migrate, consider the following steps:

    1. Check Replication Appliance Status: Since it indicates that the service is already running, ensure that the replication appliance is correctly configured and that it meets all requirements. Verify that the Mobility Agent is installed on the source VM and is registered to the Configuration Server.
    2. Network Configuration: Ensure that the network settings and firewall rules allow communication between the replication appliance and the source AWS VMs. Check that the necessary ports (TCP port 9443 and HTTPS port 443) are open for data transport.
    3. Review the Assessment: Ensure that the assessment you created is correctly configured and that it includes the VMs you intend to replicate. If the VMs are not showing up in the replication list, it could be due to issues with the assessment or discovery process.
    4. Reinstall the Replication Appliance: If you continue to face issues, consider reinstalling the replication appliance to ensure that it is functioning correctly. Sometimes, a fresh installation can resolve underlying issues.
    5. Check for Duplicate Appliances: Ensure that there are no stale or duplicate versions of the replication appliance connected to the same project, as this can cause conflicts.
    6. Consult Logs: Review the logs for any error messages or warnings that could provide more context on why the VMs are not appearing for replication.

    If these steps do not resolve the issue, you may want to consult the Azure documentation or reach out to Azure support for further assistance.

    References:

    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.