Share via

Is it possible to Move Identities, Infrastructure, apps and client PCs from one Entra ID tenant to another?

Rizwan Assad 321 Reputation points
2024-02-09T09:18:45.5366667+00:00

Is it possible to Move Identities, Infrastructure (vms etc) apps and client PCs from one Entra ID tenant to another. Both the tenants are under same subscription. If it is possible, approximately how much work is involved in achieving this? the idea is to move resource from abc.onmicrosoft.com to xyz.onmicrosoft.com

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
20,631 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. James Hamil 23,216 Reputation points Microsoft Employee
    2024-02-09T21:32:42.94+00:00

    Hi @RSahi , yes, it is possible to move identities, infrastructure (VMs, etc.), apps, and client PCs from one Azure AD tenant to another, even if both tenants are under the same subscription. However, the process can be complex and requires careful planning and execution to ensure that all resources are moved successfully and without disruption to users. Here are some general steps to consider when planning a migration:

    1. Assess your current environment: Before you begin the migration process, you should assess your current environment to identify all the resources that need to be moved. This includes identities, infrastructure, apps, and client PCs.
    2. Plan the migration: Once you have identified the resources that need to be moved, you should create a detailed migration plan that outlines the steps required to move each resource. This plan should include timelines, resource dependencies, and any potential risks or issues that may arise during the migration.
    3. Test the migration: Before you begin the actual migration, you should test the process to ensure that it works as expected. This may involve setting up a test environment to simulate the migration process and identify any potential issues.
    4. Execute the migration: Once you have tested the migration process and are confident that it will work as expected, you can begin the actual migration. This may involve moving identities, infrastructure, apps, and client PCs in stages to minimize disruption to users.
    5. Monitor and troubleshoot: During the migration process, you should monitor the progress of the migration and be prepared to troubleshoot any issues that arise. This may involve working with your IT team or Microsoft support to resolve any issues that arise.

    The amount of work involved in achieving this will depend on the specific requirements of your organization and the resources being moved. For example, moving VMs may require additional steps such as exporting and importing VM images, configuring network settings, and updating DNS records. Some more information can be found here. If you begin this process and have any questions please let me know and I can help you further. If this answer helps you please mark "Accept Answer" so other users can reference it.

    Thank you,

    James

    0 comments