MovingResources

Jeisson Velasquez 20 Puntos de reputación
2026-03-19T19:25:11.3333333+00:00

Resource Group stuck in 'MovingResources' state after cross-subscription move.

Unable to perform any operation:

  • Cannot update NIC
  • Cannot stop VM
  • Cannot modify IP configuration

Error observed:

Deployment 'NICIPConfigUpdateDeployment' failed during move.

Details:

Subscription ID: e55c1eaf-ac8a-4d0b-af7a-9f09473e4de4

Resource Group:

Correlation ID:

Request:

Please force-complete or reset the move operation and unlock the resource group.

Azure Advisor
Azure Advisor

Motor de recomendaciones personalizadas de Azure que ayuda a los usuarios a seguir los procedimientos recomendados para optimizar las implementaciones de Azure.

0 comentarios No hay comentarios

Respuesta aceptada por el autor de la pregunta
Siva shunmugam Nadessin 10,905 Puntos de reputación Personal externo de Microsoft Moderador
2026-03-20T08:50:55.2933333+00:00

Hello Jeisson Velasquez

Thank you for reaching out to the Microsoft Q&A forum.

When investigated we see that your resource group is still locked in the “MovingResources” state because the NIC IP‐config update deployment failed mid‐move. During a cross-subscription move, Azure puts both the source and target resource groups under a “CanNotDelete” lock for the duration of the operation (up to four hours) to ensure consistency. If a child deployment fails (like your NICIPConfigUpdateDeployment), Resource Manager will retry for four hours, but sometimes those locks stick and you end up unable to stop VMs, update NICs, etc.

Here’s how you can force-complete/reset the move and unlock the RG:

Cancel and delete the stuck deployment

This can be done using Powershell or Azure CLI.

1.PowerShell

Stop-AzResourceGroupDeployment -ResourceGroupName <YourRG> -Name NICIPConfigUpdateDeployment 
Remove-AzResourceGroupDeployment -ResourceGroupName <YourRG> -Name NICIPConfigUpdateDeployment

2.Azure CLI

az deployment group cancel --resource-group <YourRG> --name NICIPConfigUpdateDeployment 
az deployment group delete --resource-group <YourRG> --name NICIPConfigUpdateDeployment

Verify and remove any secondary locks on the RG • List locks:

az lock list --resource-group <YourRG> --output table

• Delete any “CanNotDelete” or ReadOnly locks you find:

az lock delete --ids <lockId>

Check that your dependent networking resources (NICs, IP configs, NSGs, etc.) are all in a “Succeeded” state. If any of them are in a failed or updating state, fix/redeploy them so they’re healthy.

Re-trigger the move operation (including all dependent resources in the same request) once everything is clean. Make sure your destination subscription is registered for the Microsoft.Network provider and that you have the required move permissions on both RGs.

If the RG still remains locked let us know 

Reference docs:

• Move resources across resource groups or subscriptions

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

• Why is my resource group locked for four hours during resource move?

https://docs.microsoft.com/azure/azure-resource-manager/management/move-resource-group-and-subscription#why-is-my-resource-group-locked-for-four-hours-during-resource-move

• Networking move limitations

https://docs.microsoft.com/azure/azure-resource-manager/management/move-limitations/networking-move-limitations

• List and delete resource group locks https://docs.microsoft.com/azure/azure-resource-manager/management/lock-resources#list-and-delete-locks-on-resource-groups

¿Le resultó útil esta respuesta?

0 comentarios No hay comentarios

0 respuestas adicionales

Ordenar por: Lo más útil

Su respuesta

Las respuestas pueden ser marcadas como Respuestas aceptadas por el autor de la pregunta, lo que indica a los usuarios que la respuesta resolvió su problema.