Azure Resource Group Stuck in "Moving Resources"

Question

I was doing some cleanup moving some Azure Cloud Services to a newly created Resource group with the following command

Find-AzureRmResource -ResourceNameContains "oldresourcename" |
Move-AzureRmResource -DestinationResourceGroupName "newresourcegroup" -Verbose

Everything was going fine, but the last one I ran seems to be taking a very long time. It is a simple CS with one worker role and one web role and small size.

The command has been in a not completed state for over an hour, and out on the Portal, both resource groups have "Moving Resources" in purple at the top of the page. I am going to wait until tomorrow to see if it still persists, but it should not be taking this long.

Is there a way to cancel or halt this operation? The concern is that both Resource Groups are locked till this process is complete, which will be an issue moving forward.

Misgive

Have you been able to fix this. I'm also facing the same problem. – Stope

I am also facing this issue. Was anyone able to get this resolved. – Appliance

@KeremDemirer, can you please tell us what happened with this? – Felly

@AmanSharma, can you please tell us what happened with this? Thanks! – Felly

@Felly I waited for 4-6 hours and the job failed and I was able to proceed agead next day. – Appliance

I was using the portal, not the command line, suspect this is why it failed: "The destination subscription must be registered for the resource provider of the resource being moved. If not, you will receive an error stating that the subscription is not registered for a resource type. You might encounter this problem when moving a resource to a new subscription, but that subscription has never been used with that resource type." Source: azure.microsoft.com/en-us/documentation/articles/… – Felly

@Felly Mine also, error gone after a while. – Stope

Having the same problem with the Portal at the moment as well. I've moving a key value at the moment and it's taking quite a long time. – Colour

I left it running all night and the service moved during that period. – Colour

wouldn't hurt to have a button to cancel the operation or something... I currently can't perform any operation in both the source and destination resource-group, which is very annoying – Filthy

Sometimes it's just a problem with Microsoft. I'd the same problem and I opened a ticket. They executed a script and 15 minutes – Ultraconservative

Answer 1

From my experience the move will eventually time out if there's an issue. I had a similar issue moving a web app and the SSL cert caused the move to fail, but it took a couple of hours for it to fail.

More information from Microsoft on what is able to move:

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

Godwin

my resource appears to be on the target resource group although i am still receiving this error message. – Selfinduced

how long is this time out? my resource is keep being updated since yesterday. – Selfinduced

@Selfinduced the timeout is 4 hours - i'm looking for how i can manually - stop/clear the locks because the resources all moved already – Shellbark

Answer 2

There are two phases in a move request. In the first phase, the resource is moved. In the second phase, notifications are sent to other resource providers that are dependent on the resource being moved. A resource group can be locked for the entire four hours when a resource provider fails either phase. During the allowed time, Resource Manager retries the failed step.

If a resource can't be moved within four hours, Resource Manager unlocks both resource groups. Resources that were successfully moved are in the destination resource group. Resources that failed to move are left the source resource group.

Ironwork