Consider the subscription transfer approach described in https://learn.microsoft.com/en-us/answers/questions/1163849/best-way-to-do-a-phased-tenant-to-tenant-migration
This is the simplest way to accomplish your objective.
In particular, a subscription transfer allows you to move an entire Azure subscription from Tenant A to Tenant B while keeping all associated resources intact. This is the simplest approach if you only need to transfer a single subscription and its resources without restructuring workloads.
When a subscription is transferred:
- All resources under that subscription move to the new tenant.
- Billing and ownership shift to the new tenant.
- User access in the original tenant is revoked, meaning administrators from Tenant A will no longer manage it.
- Resource locks, policies, and RBAC assignments are removed, requiring reconfiguration in Tenant B.
Before proceeding with a subscription transfer, consider the following:
- The subscription must be in the same billing account as the destination tenant.
- The subscription must not be suspended or deleted.
- All resources should be in a supported region for the destination tenant.
- Some services and configurations do not transfer, requiring manual reconfiguration in the new tenant.
You can initiate a subscription transfer via:
- Azure Portal – Using the Billing Management section.
- Azure PowerShell – With the
New-AzSubscriptionTransfer
command. - Azure CLI – Using
az account subscription transfer
.
The process involves:
- Requesting the transfer from the source tenant.
- Accepting the transfer in the target tenant.
- Reapplying policies, role assignments, and access controls in the new tenant.
This method is recommended if you want a quick and direct way to move an entire subscription while avoiding a more complex tenant-to-tenant migration.
If you need to move multiple subscriptions, specific resources, or services that are not covered by a subscription transfer, a tenant-to-tenant migration is required. This approach provides more flexibility but requires careful planning and additional migration tools, including
- Assessing resources & dependencies to determine what needs to be moved.
- Backing up critical data before starting the migration.
- Reviewing networking and identity configurations to avoid disruptions.
Depending on the resource types, different tools can be used:
- Azure Resource Mover – Best for infrastructure resources like VMs, storage, and networking.
- Azure Migrate – Ideal for large-scale workloads, databases, and applications.
- Azure Site Recovery – Useful for disaster recovery-based migrations with minimal downtime.
After the migration, it is crucial to:
- Verify that all resources are accessible and operational.
- Reconfigure security settings and access policies.
- Update DNS settings and application dependencies as needed.
If the comment is helpful, please click "Upvote it".