Move all my resources from my Personal Dev/Test Azure Subscription to another Azure Business Account

Question

Move all my resources from my Personal Dev/Test Azure Subscription to another Azure Business Account

Omar Barlas 0

I want to move all my resources from my Personal Dev/Test Azure Subscription to another Azure Business Account. What is the most efficient way to port these services and resources, with minimal downtime?

0 comments

2 answers

Your answer

Answer 1

Hello @Omar Barlas

Thank you for reaching out to Microsoft Q&A.

If your goal is to move resources from a Personal Dev/Test Azure subscription to a Business Azure subscription with minimal downtime, the recommended approach depends on the relationship between the two subscriptions.

If both subscriptions belong to the same Microsoft Entra ID (Azure AD) tenant, many Azure resources can be moved directly between subscriptions using Azure Resource Manager (ARM) move operations. During the move, Azure places a temporary lock on the source and destination resource groups, but the resources themselves generally remain operational, which helps minimize downtime.

Before proceeding, we recommend:

Verify that the source and destination subscriptions are under the same Microsoft Entra tenant.
Review the supported resource types and any move limitations, as not all Azure resources support cross-subscription moves.
Ensure that dependent resources (such as VNets, NICs, disks, and load balancers) are included in the move where required. Azure validates these dependencies during the move process.
For larger environments with multiple interconnected resources, consider using Azure Resource Mover, which provides dependency validation and orchestrates the migration workflow.

You can follow the below 1st document to move the resources from one subscription to another subscription.

Microsoft documentation:

If the answer is helpful, please click "Accept Answer" it. If you have extra questions about this answer, please click "Comment".

Answer 2

The most efficient path depends on whether the destination subscription is in the same Microsoft Entra tenant.

If both subscriptions are in the same tenant: use an in-place Azure resource move to the target subscription or resource group.
If the business account is in a different tenant: Azure resource move does not support moving resources across tenants. In that case, the practical options are to transfer the subscription to the business tenant, or keep the subscription where it is and delegate access to the business account.

For minimal downtime, the best option is:

Check whether both subscriptions are in the same Microsoft Entra tenant. Use:

   az account show --subscription <your-source-subscription> --query tenantId
   az account show --subscription <your-destination-subscription> --query tenantId

If the tenant IDs match, move the resources directly. In Azure portal:
- Open the source resource group.
- Select the resources.
- Select Move.
- Choose Move to a new subscription or Move to a new resource group.
- Select the destination.
- Wait for validation to complete.
- Acknowledge the update requirement for tools/scripts.
- Select Move.
If moving across subscriptions, move dependent resources together. For example, a VM and its managed disks and other dependencies must be in the same resource group and moved in one operation.
Validate before moving. Azure validates the move in the portal automatically. CLI and PowerShell validation are also available if a dry run is needed.

What to expect during the move:

Existing resources remain operational during the move.
Source and destination resource groups are locked while the move is in progress, so create/update/delete operations are blocked temporarily.
The lock can last up to four hours, though many moves finish sooner.
Resource IDs change after the move, so scripts, templates, dashboards, and any tooling that references resource IDs must be updated.
Child resources move automatically with their parent, but child resources cannot be moved independently.
If a read-only lock exists on the source or destination resource group or subscription, the move is blocked.
Role assignments do not move with the resource and must be recreated after the move; existing active role assignments can become orphaned.

If the personal Dev/Test subscription and the business account are in different tenants:

Azure resource move between subscriptions will not work directly.
The supported direction is to either:
- Transfer billing ownership / move the subscription tenant so the subscription lands in the business tenant, or
- Delegate access to the business account if the goal is management rather than relocation.

For a full move with minimal service interruption, the preferred sequence is:

Verify both subscriptions are active.
Verify both subscriptions are in the same tenant.
Confirm the resource types support move operations.
Consolidate dependent resources into one resource group if needed.
Run validation.
Perform one move operation for each dependency set.
Recreate RBAC assignments and update scripts/tools that use resource IDs.

If the target is a different tenant and the goal is to fully relocate ownership, transferring the subscription is the efficient option. If the goal is only to let the business account manage the resources, delegating access is faster and avoids moving resources.