If you try to move resources in Azure and see the message ‘Some resources couldn’t be moved,’ it usually means there are dependencies or configuration issues that must be fixed before you can continue.
This error happens when a Public IP (PIP) is attached to a network interface which cannot be moved. To fix this, first remove the Public IP from the NIC, then try moving the resource again.
This guide will show you each step in the process.

 

Step 1. Find Resources That Did Not Pass Validation

When you validate a resource move, you might see several failures. One common issue is with the Public IP address.
  • Virtual machine
  • Network security group
  • Network interface
  • Disks
  • Public IP address (fails validation)
  • Virtual network

You need to remove, or dissociate, the Public IP before the move will work.

Step 2. Dissociate the Public IP address

  • Go to the Public IP Address resource in the Azure portal.
  • Click Dissociate in the top menu.

  • When the confirmation dialog appears, click Yes.

This step removes the PIP from the NIC, but it does not delete the PIP.

Step 3. Begin the process of transferring to a different subscription

Go to the Resource Group that has the VM and its related components.
Select all the resources in the group, such as the VM, NIC, disks, VNet, and NSG.
Then click the three-dot menu, choose Move, and select Move to another subscription.

Step 4. Begin the process of transferring to a different subscription

Check that the source subscription and resource group are correct.
Then, pick the target subscription.
You can either select an existing resource group or create a new one.
When you’re ready, click Next.

Step 5. Ensure Resources Are Validated Before Moving

You should now see a list of all available resources.
Succeeded
This shows that removing the Public IP has fixed the validation errors.
Click Next to continue.

Step 6. Please confirm and initiate movement

Look over the summary details.
Select the box that says, “I understand that tools and scripts for moved resources won’t work until I update them with new resource IDs.
Next, click “Move” to begin the transfer.
The process might take a few minutes, depending on how many resources you have and their size.

Conclusion

If you remove the public IP address before moving the resources, you will avoid validation errors and can transfer all VM-related resources to the target subscription without issues.
Share This