Issue with Azure Resource Mover: Cannot Move VM Due to Public IP Dependency

Question

Issue with Azure Resource Mover: Cannot Move VM Due to Public IP Dependency

Brandon Lee 20

I’m currently using Azure Resource Mover to migrate a VM instance to a new subscription, but I'm unable to proceed due to the following issues:

Example:

When I try to move a VM instance, I receive a Validation Failed error with the following message:

(Code: ResourceMoveProviderValidationFailed)
The move resources request does not contain all the dependent resources.
Please check details for missing resource Ids.
(Code: MissingMoveDependentResources, Target: Microsoft.Network/networkInterfaces)
/subscriptions/[MY-SUBSCRIPTION-ID]/resourceGroups/[MY-COMPANY-NAME]/providers/Microsoft.Network/publicIPAddresses/ip

So I added the public IP to the move group and tried validating again, but then I received a different error:

(Code: CannotMoveResource, Target: Microsoft.Network/networkInterfaces)
Move for resource type publicIPAddresses is not supported.
Move request contains resource /subscriptions/[MY-SUBSCRIPTION-ID]/resourceGroups/[MY-COMPANY-NAME]/providers/Microsoft.Network/publicIPAddresses/ip of that type.

Because of this, I’m unable to proceed with the migration. What is the recommended solution in this case?

Naveena Patlolla 4,960 Reputation points Microsoft External Staff Moderator

2025-08-04T06:17:17.28+00:00
Hi Brandon Lee

Adding to TP points.

The public IP address is region-specific and won't be retained in the target region after the move.

Reference link: https://learn.microsoft.com/en-us/azure/resource-mover/support-matrix-move-region-azure-vm#supported-vm-networking-settings

If you're still unable to move the VM to the new subscription, consider the following approach: take a snapshot of the VM, and during snapshot creation, select the target subscription.

Capture a Snapshot of the OS Disk

• Go to your VM in the Azure Portal.

• In the left pane, select Disks.

• Click on the OS disk (it will be named like vmname_OsDisk_xxxx).

• At the top menu, click Create Snapshot.

• Fill in:

• Name (e.g., MySnapshot)

• Resource Group

• Snapshot type: Choose Full.

• Click Review + Create, then Create.

Create a Managed Disk from the Snapshot

• Go to the Snapshots page (find it via the left search bar).

• Select the snapshot you just created.

• Click Create Disk at the top.

• Fill in:

• Name (e.g., DiskFromSnapshot)

• Resource Group

• Region

• Use default values unless you need to change size or performance settings.

• Click Review + Create, then Create.

Create a New VM Using the Managed Disk

• Go to Disks in the Azure Portal.

• Select the managed disk you just created.

• Click + Create VM at the top.

• Complete the VM creation wizard as desired; the managed OS disk will be used automatically.

Handling Data Disk Snapshots and Attachments

For each data disk attached to the VM:

From the VM’s Disks page, scroll to the Data Disks section.

Click on a data disk name.

Create a snapshot by repeating the steps from Step 1 (choose the data disk instead of the OS disk).

For each snapshot:

• Go to Snapshots, select the snapshot, and click Create Disk.

• Fill in the necessary details and create the disk.

To attach these disks to the new VM:

• While in the Create VM wizard (under the Disks tab):

• Scroll to Data Disks.

• Click Add a data disk.

• Choose Use existing.

• Select the managed disk you created from the corresponding data disk snapshot.

• Repeat for every data disk.

Please let me know if you face any challenge here, I can help you to resolve this issue further

If the comment was helpful, please click "Upvote"
Naveena Patlolla 4,960 Reputation points Microsoft External Staff Moderator

2025-08-05T05:54:38.1633333+00:00

Hi Brandon Lee
Just want to check if the provided solutions worked for you or else please let us know if any help, we are always here to help whenever you need us.

Please do not forget to "Accept the answer” and “upvote it” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.
Naveena Patlolla 4,960 Reputation points Microsoft External Staff Moderator

2025-08-06T07:22:09.11+00:00

Hi Brandon Lee
We would like to confirm whether the issue has been resolved or if you still need further assistance.

1 answer

Your answer

Naveena Patlolla 4,960 Reputation points Microsoft External Staff Moderator

2025-08-05T05:54:38.1633333+00:00

Hi Brandon Lee
Just want to check if the provided solutions worked for you or else please let us know if any help, we are always here to help whenever you need us.

Please do not forget to "Accept the answer” and “upvote it” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.
Naveena Patlolla 4,960 Reputation points Microsoft External Staff Moderator

2025-08-06T07:22:09.11+00:00

Hi Brandon Lee
We would like to confirm whether the issue has been resolved or if you still need further assistance.

Answer 1

TP 131.7K Volunteer Moderator

Hi Brandon,

Before attempting to move the VM, please navigate to the public IP address and click Dissociate button, confirm, and wait for it to finish (usually seconds). Next go ahead and attempt the move.

enter image description here

Please click Accept Answer and upvote if the above was helpful.

Thanks.

-TP

Brandon Lee 20 Reputation points

2025-08-04T06:07:58.8733333+00:00
Hello TP,

Thank you for your response.

Just to confirm, the process would be as follows:

Dissociate all IP addresses associated with the VMs

Move all instances to a new subscription, including the IPs

Once the move is complete, re-associate the IPs

Does this mean that all instances will be unreachable during the entire process?
TP 131.7K Reputation points Volunteer Moderator

2025-08-04T06:45:43.1366667+00:00

Does this mean that all instances will be unreachable during the entire process?

Correct. As soon as you Dissociate the IP no public traffic from the IP will flow to the VM.
TP 131.7K Reputation points Volunteer Moderator

2025-08-13T15:43:35.78+00:00

@Brandon Lee Any update? Please click Accept Answer and upvote to close up this thread or if you still need assistance, add a comment below.

Thank you.

Share via

Issue with Azure Resource Mover: Cannot Move VM Due to Public IP Dependency

1 answer

Your answer