Move VMs from one resource group to another

Microsoft Azure Resource Manager is a power-packed resource deployment and management system. One feature you may find quite useful as an Azure administrator studying for the AZ-104 exam, is the ability to move Virtual Machines (VMs) from one resource group to another. With Azure, you can move resources like VMs for better management reasons, changing business needs, or to reorganize your environment. The ability to shift VMs between resource groups offers immense flexibility and control, allowing you to align resource deployment with your operational and organizational requirements.

The Basics on Azure Resource Groups and VMs

Before we dive into the practical aspect, it’s crucial to understand what Azure resource groups and virtual machines are.

• Azure Resource Group: This is a logical container for Azure resources deployed within an Azure subscription. A Resource Group contains related resources for an Azure solution. It holds related resources for an Azure solution, and provides a way to uniformly manage them.
• Azure Virtual Machine (VM): VMs are on-demand, scalable computing resources that Azure offers. It’s like having a computer in the cloud where you have control over the OS and the configuration.

Moving VMs from One Resource Group to Another

There are a few ways to move a VM from one resource group to another. For example, you can move a VM using the Azure Portal, Azure PowerShell, or Azure CLI.

Note– While moving a VM, Azure recreates the VM in the new resource group, which leads to an Update of the VM rather than the creation of a new VM. Hence, there is no real downtime experienced during this process.

Moving a VM using Azure Portal

1. Log in to your Azure portal, and select the VM you want to move
2. Click on the ‘Move’ button at the top and select ‘Move to another resource group’
3. Follow the instructions on the screen to move the VM to the new resource group

Moving a VM using Azure PowerShell

Here’s an example of how you can leverage Azure PowerShell to move a VM from one resource group to another:

#Login into the Azure account
Login-AzAccount

#Move the VM to a new resource group
Move-AzResource -DestinationResourceGroupName 'destinationRG' -ResourceId (Get-AzResource -ResourceGroupName 'sourceRG' -Name 'myVM').ResourceId


Moving a VM using Azure CLI

You can also use the Azure CLI to move a VM from one resource group to another. It is quite similar to the PowerShell example:

#Login into the Azure account
az login

#Move the VM to a new resource group
az resource move --destination-group 'destinationRG' --ids $(az resource show --name 'myVM' --resource-group 'sourceRG' --query id --output tsv)


Considerations and Limitations

Before you move a VM to a new resource group, there are a few limitations and considerations to bear in mind:

1. The source and the destination resource groups must reside within the same Azure Subscription.
2. Some resources, like ExpressRoute, VPN Gateway, or Application Gateway v2 SKU instances, do not support the move operation.
3. The move operation includes the VM, its associated resources, and its dependencies.

In conclusion, the ability to move a VM from one resource group to another is a powerful capability within Azure. It not only helps in aligning your resource deployment as per organizational needs but also adds a layer of flexibility to your system’s architecture. When studying for the AZ-104 exam, understanding these concepts about Azure VMs and resource groups will be beneficial.

Practice Test

True or False: Virtual Machines can be moved from one resource group to another in Azure.

• True
• False

Answer: True

Explanation: Azure supports the ability to move resources like VMs from one group to another to manage and organize your infrastructure better.

What is the PowerShell cmdlet used to move a VM to a different resource group in Azure?

• a) Move-AzureRmResource
• b) Move-AzureResourceGroup
• c) Move-AzureVmResource
• d) Move-AzureVmGroup

Answer: a) Move-AzureRmResource

Explanation: The Move-AzureRmResource cmdlet is used to move a resource to a new resource group or subscription.

True or False: You can only move a VM to another resource group if the destination resource group is in the same region.

• True
• False

Answer: False

Explanation: VMs can be moved to any resource group regardless of its location. However, associated resources like disks and networking resources must also be moved together.

Which of the following must also be moved with a VM when changing resource groups to ensure the correct functioning of the VM?

• a) Disk
• b) Network interfaces
• c) Both a and b
• d) None of the above

Answer: c) Both a and b

Explanation: When moving a VM between resource groups, the associated resources like the disk and network interfaces should be moved as well as they are an integral part of the functioning of the VM.

True or False: Availability is affected during a VM move operation.

• True
• False

Answer: True

Explanation: During the VM move operation, there might be a short period of downtime, affecting availability.

Which of these Azure services is not necessary when moving a VM from one resource group to another?

• a) Azure StrongMove
• b) Azure Resource Manager
• c) PowerShell
• d) None of the above

Answer: a) Azure StrongMove

Explanation: Azure Resource Manager and PowerShell are the tools used to move VMs from one resource group to another. Azure StrongMove does not exist.

True or False: You can move a VM to a new resource group and change its size at the same time.

• True
• False

Answer: False

Explanation: The size of a VM cannot be changed during the move operation. It must be done separately.

Does moving a VM to a different resource group incur any extra costs?

• a) Yes
• b) No

Answer: b) No

Explanation: Azure does not charge any fees for moving resources between groups or subscriptions. However, standard rates apply for outgoing data transfers.

What is the maximum number of VMs that can be moved at one time?

• a) 10
• b) 25
• c) 50
• d) 100

Answer: c) 50

Explanation: The limit set by Azure is 50 virtual machines that a single move operation can contain.

True or False: It is possible to undo a VM move once it’s initiated.

• True
• False

Answer: False

Explanation: Once initiated, a VM move operation cannot be reversed. The resource can, however, be moved back to the original resource group after the operation completes.

Interview Questions

What is a resource group in Microsoft Azure?

A resource group in Microsoft Azure is a container that holds related resources for an Azure solution. The resource group includes those resources that you want to manage as a group.

What is the purpose of moving VMs from one resource group to another in Azure?

The primary purpose of moving VMs from one resource group to another is to efficiently manage and organize resources. You may also want to move resources to consolidate your infrastructure and to optimize resource usage charges.

Can you move a VM from one resource group to another without downtime?

Yes, moving a VM from one resource group to another doesn’t impact the running operation of the VM, so there’s no downtime associated with the move.

Which Azure service is used for moving VMs from one resource group to another?

The Azure Resource Manager service is used to move VMs from one resource group to another in Azure.

How long does it typically take to move a VM from one resource group to another in Azure?

The time it takes to move a VM in Azure depends on a variety of factors such as the size of the VM and the current load on the Azure infrastructure. However, it typically takes a few minutes.

Can a VM be moved to a new resource group in a different region?

Yes, you can move a VM to a new resource group in a different region. However, the move involves moving all the resources related to the VM, and there could be downtime during this process.

What things should be considered before moving a VM to a new resource group?

Before moving a VM to a new resource group, you should consider the dependencies of the VM, the potential impact on other resources, and any settings or policies currently applied to the resource group.

What PowerShell command is used to move a resource to a new group?

The “Move-AzResource” command is used in PowerShell to move resources to a new resource group in Azure.

What happens to the resources dependent on the VM which is being moved to a different resource group?

When the VM is moved to a different resource group, all dependent resources, such as disks and networking components, are also moved along.

What are the necessary permissions required to perform the move operation in Azure?

The necessary permissions to perform the move operation in Azure are ‘Microsoft.Resources/subscriptions/resourcegroups/write’ on the target resource group and ‘Microsoft.Resources/subscriptions/resourcegroups/delete’ on the source resource group.

Can a VM be moved directly between subscriptions?

Yes, a VM can be moved directly between subscriptions as long as you have the appropriate permissions for both the source and target subscriptions.

Can I move a VM to a resource group that already contains resources?

Yes, you can move a VM to a resource group that already contains resources, provided there are no conflicts with resource names and types.

Are there any instances when a VM can’t be moved?

Yes, there are certain instances. For example, a VM using managed disks cannot be moved across subscriptions if the source or target subscription has a policy that doesn’t allow the creation of VM disk storage.

Is it possible to undo a VM move operation in Azure?

No, once a VM move operation is performed, it cannot be undone in Azure. The VM would need to be moved back to the original resource group manually if required.

What is the first step you should take before moving a VM in Azure?

The first step before moving a VM in Azure is to plan the move, taking into account all dependencies and potential impacts, and to ensure you have the necessary permissions.