Share via


CSP migration, cannot move VM: Resource move is not supported for resources that have plan with different subscriptions

Question

Monday, January 21, 2019 11:40 AM

Hi,

I'm trying to move a resource group to a new subscription. But the validation failed with the following error:

ResourceMoveFailed
Message: Resource move is not supported for resources that have plan with different subscriptions. Resources are 'Microsoft.Compute/virtualMachines/ZBFormulieren' and tracking id is 'bda43449-90a4-4bcc-960a-27dfa67bf8b3'.

I have checked the VM, but the subscription is the same as all the other VM's and apps. Any suggestion?

All replies (12)

Tuesday, January 22, 2019 5:36 AM

Hi Koosvd,

Is that virtual machine created from a Marketplace image with plan attached?

Also checkout the VM limitations.

If that virtual machine has a plan attached, Then rebuilding in the new subscription is the way to go.

Try this out and let me know.


Tuesday, January 22, 2019 8:31 PM

We took over this Azure enviroment a few months ago. I don't know if this VM have a Marketplace image. How can I check this?


Wednesday, January 23, 2019 4:58 AM

Hello, please have a look at this and see if the resource group have any resources that might not be eligible to move between subscriptions.

Based on the error it seems you VM falls under this limitations:

"Virtual machines created from Marketplace resources with plans attached can't be moved across resource groups or subscriptions. Deprovision the virtual machine in the current subscription, and deploy again in the new subscription."

https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-move-resources

Isaac Oben MCITP:EA, MCSE,MCC <a href="https://www.mcpvirtualbusinesscard.com/VBCServer/4a046848-4b33-4a28-b254-e5b01e29693e/interactivecard"> View my MCP Certifications</a>


Wednesday, January 23, 2019 5:19 AM

Hi,

You can use the below command to check if the vm has a plan attached with it or not.

az vm show -n "vm name"  -g "resource group name" --query "{name:name,plan:plan}" -o table

Like Issac Oben mentioned, i suspect that your vm has a plan attached with it.


Thursday, January 24, 2019 11:58 AM

Hi,

You can use the below command to check if the vm has a plan attached with it or not.

az vm show -n "vm name"  -g "resource group name" --query "{name:name,plan:plan}" -o table

Like Issac Oben mentioned, i suspect that your vm has a plan attached with it.

If I try your command, I get this:

C:\WINDOWS\system32>az vm show -n "ZBFormulieren"  -g "contoso" --query "{name:name,plan:plan}" -o table
Name

ZBFormulieren

C:\WINDOWS\system32>

Monday, April 8, 2019 6:01 PM

Did you ever manage to get around this? I'm having the same problem. 

The command above just returns the VM name without any plan. My vm has been created from marketplace. But what exactly means "with a plan attached"? Can please someone explain what to look for in the portal?

@issac_oben @jakaruna-msft ?


Thursday, April 11, 2019 7:47 AM

I will try a new migration next week. I gonna remove the VM (not the disk). Start the migration and recreate the VM again (from the disk).


Friday, October 25, 2019 11:57 AM

Anyone have any tips for this one? I'm having the exact same error message and can't find any information…

The PowerShell command does not work for me and I'm trying to get something out from the Get-AzVM command instead.

Thanks for your help guys!


Wednesday, October 30, 2019 4:13 PM

Did you ever manage to get around this? I'm having the same problem. 

The command above just returns the VM name without any plan. My vm has been created from marketplace. But what exactly means "with a plan attached"? Can please someone explain what to look for in the portal?

@issac_oben @jakaruna-msft ?

@Nico.Kaiser

Try this command instead:

az vm show -n "vm name"  -g "resource group name" --query "{name:name,plan:plan.name}" -o table

Subtle difference in the command above. Im actually trying to perform the same type of move, and this command above confirms that I have a plan attached to my VM, but I havent found a solution yet (I REALLY dont want to have to rebuild).


Thursday, October 31, 2019 8:36 AM

I got the confirmation that the VM and all the attached components I try to move have been created from the Markeplace.

As a result, I have no other choice but to rebuild everything…

The following article explains it all: Move VM, scenarios not supported

"Virtual machines created from Marketplace resources with plans attached can't be moved across resource groups or subscriptions. De-provision the virtual machine in the current subscription, and deploy again in the new subscription."


Thursday, October 31, 2019 9:27 AM

Hi,

For anyone stuck on this - there is no alternative right now. You have to rebuild. 

Simple and terrible but better know it early and start planning than waste time!

Also, there is no way to see a Plan via the portal, you have to use one of the CLIs.

Joe 


Thursday, October 31, 2019 11:34 AM | 2 votes

And if you rebuild, make a good documentation of the used plan on the VM. In my case, I removed the VM and tried to rebuild the VM from the VHD. This failed, because the plan was not matched with the new VM. I didn't document the plan information, so I was prety lost. Even Microsoft Support was not able to fix this.