
To move a resource group to another subscription in Azure, you'll need to use the Azure portal. First, sign in to the Azure portal and navigate to the resource group you want to move.
To do this, click on the "Resource groups" link in the navigation menu, then select the resource group you want to move. Next, click on the three dots next to the resource group name and select "Move".
In the "Move resource group" pane, select the new subscription you want to move the resource group to from the dropdown menu. Make sure to choose the correct subscription, as this cannot be undone.
The move process may take a few minutes to complete, depending on the size of the resource group and the resources it contains.
Preparation
Before you start migrating Azure resources, it's essential to prepare for potential issues that may arise. Make sure to unlink automation accounts from workspaces if necessary, as moving them independently can prevent data loss.
Check that all dependent resources are included in the move request, especially for VMs with disks, storage accounts, virtual networks, and NSGs. The error code "DiskHasRestorePoints" often indicates missing restore points, which can be deleted to resolve the issue.
Don't try to move resources with plans in different subscriptions, as Microsoft doesn't support this by default. This includes resources like Network Watchers, Bing Keys, and Workspaces.
Terraform: Move Resource Group
Moving a resource group using Terraform can be a bit of a challenge, but it's doable with the right approach.
You'll need to manually move the resources on the Azure portal, then change the subscription on the CLI or for Terraform, and finally run Terraform commands like `terraform state rm` and `terraform import` for each resource.
Fortunately, Terraform can re-create resources that can't be moved, so you won't have to start from scratch.
Here's a step-by-step guide to help you through the process:
Consider reading: Terraform Azure Resource Group
1. Navigate to the resource group you want to move in the Azure portal.
2. Click on the "Move" button and select "Move to another subscription" option.
3. Review the resources to be moved and select the target subscription and resource group.
4. Click on the "OK" button to start the process.
5. Verify that all resources have been successfully moved to the new subscription.
6. Delete the original resource group in the source subscription once it's empty.
By following these steps, you'll be able to move your resource group using Terraform and keep your infrastructure organized.
Select Resources
Selecting the resources to move is a crucial step in the process. This is where you get to review and confirm which resources will be moved to the new subscription.
The resources to be moved are automatically selected, so you don't need to worry about manually selecting each one. However, it's a good idea to double-check and make sure everything that needs to be moved is included.

To finalize the resource selection, simply review the content that is to be moved. If the target resource group doesn't already exist, you can create it now in the target subscription.
Here's a quick rundown of the key steps:
- Review the resources that are automatically selected.
- Check that all necessary resources are included.
- Create the target resource group if it doesn't already exist.
By following these steps, you'll be able to ensure that all the necessary resources are moved to the new subscription.
Steps to Accomplish the Task
To accomplish the task of moving Azure resources, you'll need to follow these steps. First, navigate to the resource group you want to move, which can be found in the Azure portal's Resource groups blade.
You'll need to click on the Move button and select Move to another subscription option. Then, review the resources that are to be moved, which are automatically selected, and select the subscription and resource group you want to move to.
If the resource group is not already created, you can create it now by clicking on the link to create a new resource group. Click on the OK button to start the process, which will then be validated and followed by a success or failure notification.

Here's a summary of the steps:
- Navigate to the resource group you want to move.
- Click on the Move button and select Move to another subscription option.
- Review and select the target subscription and resource group.
- Click on the OK button to start the process.
The move process can take up to four hours to complete, but most moves are done in much less time. During this time, both the source and target groups are locked, preventing any write or delete operations. However, the resources themselves are not frozen and can still be used as usual.
The Move Process
The Move Process is a straightforward step-by-step process that can be completed in a few easy steps. You'll need to navigate to the resource group you want to move, which can be done by going to the Resource groups blade in the Azure portal.
To initiate the move, click on the Move button and select Move to another subscription option. This will take you to the resources to move screen, where you'll review the resources that are automatically selected for movement.
The resources to move screen is a critical step, where you'll select the subscription and resource group you want to move the resources to. If the resource group doesn't exist, you can create it by clicking on the link to create a new resource group.
Once you've selected the target subscription and resource group, click on the OK button to start the process. The job will be validated, and you'll receive a notification of the movement in progress, followed by a success or failure notification.
Here are the key steps to move a resource group to another subscription:
- Navigate to the resource group you want to move
- Click on the Move button and select Move to another subscription option
- Select the target subscription and resource group
- Click on the OK button to start the process
- Wait for the job to be validated and receive a notification of the movement in progress
Note that the lock on the source group and target group can last for a maximum of four hours, but most moves complete in much less time.
Migration Considerations
When migrating Azure resources, it's essential to be aware of potential issues that may arise during the process. One such issue is the error "Automation account is linked to a workspace so it cannot be moved." This is because unlinking the workspace would cause loss of all solutions created for the concerning automation account.
To overcome this, consider making the automation account an independent resource by unlinking its workspace. This may require careful planning to avoid data loss.
Expand your knowledge: How to Change Account Admin in Azure Subscription
Another common issue is the error "The move resources request does not contain all the dependent resources." This occurs when the move consists of some resources that are dependent on others missing in the move. To resolve this, ensure that all dependent resources are moved in one go before migrating Azure resources.
Here are some common error codes and their solutions:
It's also crucial to note that migrating Virtual Networks requires removing any peering done for them before attempting the move.
Validate the Move
You'll know the move is in progress when you see a notification.
The job will then be validated, and you'll see a success or failure notification. If the move fails, details will be provided on why the resources could not be moved.
In the event of a failure, you can usually try again after working through the issues.
Here are the steps to take when validating the move:
- Click on the OK button to start the process.
- Wait for the job to be validated.
- Check for a success or failure notification.
If the move is successful, you'll be able to verify all the resources are accounted for and functioning as intended.
Purpose of Achievement

Moving your Azure assets to another resource group or subscription is a common scenario, especially when it's time to reorganize for management or billing purposes.
You may need to move your Azure assets due to changing business needs or to simplify your setup.
It's essential to investigate the checklist before migrating your Azure resources to ensure a smooth transition.
Moving assets is easy to do in Azure, making it a helpful feature for administrators.
Explore further: Moving from Aws to Azure
Azure Resource Migration Issues
You may encounter errors during the migration process, but don't worry, I've got you covered. One common error is "Automation account is linked to a workspace so it cannot be moved", which can be frustrating, but it's not always a deal-breaker.
To resolve this, you can unlink the workspace, but be aware that this will cause the loss of all solutions created for the concerning automation account. In some cases, it's necessary to make the automation account an independent resource.
Another error you might see is "The move resources request does not contain all the dependent resources", which means you're missing some resources that are dependent on others. Make sure to move all dependent resources in one go before attempting to migrate Azure resources.
Check the error code, as it may provide a clear indication of the issue, such as "DiskHasRestorePoints", which requires you to delete the restore points before migrating.
Resource moves are not supported for resources with plans in different subscriptions, so you may need to let go of certain resources, like Network Watchers or Bing Keys.
Frequently Asked Questions
Can Azure resource group have multiple Azure subscriptions?
No, an Azure resource group can only belong to one Azure subscription. However, a subscription can contain multiple resource groups.
Featured Images: pexels.com


