How to remove a move-collection

ravella krishna charan 0 Reputation points
2025-06-26T05:05:05.9166667+00:00

I am trying to clean up my resource groups , but i keep getting an error that move collection exists, i tried to remove it but system-assigned managed identity error. used powershell scripts to remove but it wont remove the move collection, the Vnet in it is not even existing anymoreScreenshot (241)

Azure Resource Mover
Azure Resource Mover
An Azure service used for moving multiple resources between Azure regions.
288 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Deepanshu katara 16,945 Reputation points MVP Moderator
    2025-06-26T06:42:46.1833333+00:00

    Hello , Welcome to MS Q&A

    It sounds like you're encountering a common issue when trying to delete a Move Collection in Azure Resource Mover, especially when it involves a system-assigned managed identity that no longer has valid permissions or is orphaned. Here are some steps and workarounds based on official guidance and community solutions:


    Steps to Resolve the Issue

    1. Check for Hidden Resources

    • Go to the Resource Group in the Azure Portal.
    • Click on “Show hidden types” at the top of the resource list.
    • Look for the Move Collection or any Move Resources still listed.
    • Try deleting them manually from the portal.

    2. Use Azure Resource Mover UI

    • Navigate to Azure Resource Mover > Across regions.
    • Select the subscription and regions involved.
    • If any move resources are listed, delete them first.
    • Then try deleting the move collection again.

    3. PowerShell Cleanup

    If the portal doesn’t work, try this PowerShell command:

    Remove-AzResourceMoverMoveCollection -MoveCollectionName "<MoveCollectionName>" -ResourceGroupName "<ResourceGroupName>"
    
    

    But only after ensuring all move resources inside the collection are deleted.

    4. System-Assigned Managed Identity Issue

    If you're getting errors related to the system-assigned managed identity, try:

    • Disabling and re-enabling the identity (if the resource still exists).
    • If the resource is deleted, the identity might be orphaned. In that case, you may need to:
      • Use the Azure CLI or PowerShell to force delete the resource group.
        • Or contact Microsoft Support for backend cleanup.

    📚 Helpful Links

    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.