How can i fix a resource group mover that pops errors when deleting the resource group?

This usually happens because the Move Collection still contains move resources or stale Resource Mover references, even if the original source resource group was already deleted.

Try this path:

1. In the Azure portal, open Azure Resource Mover directly, not just the resource group view.
2. Go to Across regions and find the move collection tied to the failing Resource Mover resource group.
3. Remove any resources that still appear in that move collection.
4. If the portal shows no visible resources, check for an orphaned or stale Resource Mover link/reference in the Resource Mover experience and delete that reference.
5. After the move resources or stale reference are removed, retry deleting the Move Collection or the resource group.

If the move collection contains resources in a failed or pending state, the required cleanup depends on the state:

• For VM resources, if the state is Initiate move failed, delete the resource from the move collection and delete anything created in the target region, including replica disks. Infrastructure resources created during the move must be deleted manually.
• For Commit pending or Commit failed, discard the move first so target resources are deleted, then continue from Initiate move pending.
• For Discard completed, the resource is removed from the move collection along with target-created items, but some infrastructure resources may still need manual deletion.
• For SQL resources, Commit pending and Commit failed should also be handled by discarding the move first so target resources are deleted.

If deletion is still blocked, check whether the resource group is in an inconsistent state:

1. Verify the resource group provisioning state is Succeeded.
2. Check Resource groups > the affected resource group > Deployments for any deployment stuck in a state other than Succeeded or Failed.
3. Cancel stuck deployments if needed, then delete failed deployment records before retrying the move or deletion.
4. Check for resource locks on the resource group and remove them temporarily if they are not required for the move. Re-apply them afterward if needed.

Important:

• A move operation can lock the source and destination resource groups for up to four hours while Azure retries dependent operations.
• During that time, create, update, and delete operations on those resource groups can fail.
• Deleting a resource group is irreversible.

• Move Azure resources to a new resource group or subscription
• Manage move collections and resource groups
• Azure resource move fails because resource group isn't in expected state
• Azure virtual machine move fails because resource group has active deployments
• Azure Resource Manager resource group and resource deletion
• Unable to delete a Resource Mover Resource Group - Microsoft Q&A Unable to delete a Resource Mover Resource Group, even though neither original source nor destination resources exist
• Unable To Delete Resource Group - Microsoft Q&A Hello,
• Couldnot be able to remove a resource group - Microsoft Q&A I could not remove a resource group.