Unable to delete Azure Resource Mover Move Collection – DeleteCollectionFailedResourcesExists

Arkadiusz Wszołek 0 Reputation points
2025-08-01T08:58:07.1433333+00:00

Hi,

I cannot delete a Resource Mover Move Collection.

Resource Group: ResourceMoverRG-westeurope-eastus2-eus2

Move Collection: MoveCollection-we-eus2-eus2

(Subscription ID can be provided privately if required)

When trying to delete the Move Collection (via Portal, PowerShell, or Azure CLI), I always get the error:

Error: DeleteCollectionFailedResourcesExists – deletion of move collection is not allowed when there are move resources present.

However:

  • No moveResources are visible in the Azure Portal (even with "Show hidden types" enabled).
  • No moveResources are returned using Azure CLI (az resource list --resource-group ... --query "[?type=='Microsoft.Migrate/moveResources']").
  • PowerShell and REST API also return empty lists.

It looks like the Move Collection is orphaned and blocking the deletion of the entire Resource Group.

Could Microsoft please assist with backend cleanup of this Move Collection?

Thanks in advance.

Azure Resource Mover
Azure Resource Mover
An Azure service used for moving multiple resources between Azure regions.
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Michele Ariis 2,520 Reputation points MVP
    2025-08-01T10:35:29.16+00:00

    Hi, You’re hitting the guardrail that blocks deleting a Move Collection when it still has child moveResources, even if they don’t show up in Portal or az resource list. You need to explicitly list and delete them using the Resource Mover CLI/API. First, run az extension add -n resource-mover --upgrade, then use az resource-mover move-resource list to enumerate all moveResources under the collection. If there are any, loop through and delete them one by one (az resource-mover move-resource delete ...). Once the list returns empty, delete the Move Collection with az resource-mover move-collection delete. If the CLI list is empty but delete still fails, use az rest to query the actual moveResources endpoint and manually delete anything returned. Also check unresolved dependencies with a similar az rest call. Make sure no resource locks are present and double-check for typos in resource names. If all that fails, it's likely a backend orphan and you’ll need to open an Azure support request under Azure Resource Mover - “Move collection management / Deletion” and provide the subscription ID, RG, Move Collection name, full resource ID, and correlation ID from the failed delete. If you want, share the output of az resource-mover move-resource list and I’ll help identify what’s blocking deletion or confirm if it’s backend-related.

    0 comments No comments

  2. Arkadiusz Wszołek 0 Reputation points
    2025-08-01T16:49:18.4166667+00:00

    Hi, thank you for the detailed explanation. I followed your guidance, listed the hidden moveResources with az rest, deleted them one by one, and then removed the Move Collection successfully. Everything is cleaned up now. Appreciate your help!

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.