Resource move validation failed from one subscription to other subscription

Sathwik 20 Reputation points
2025-10-14T06:19:50.0066667+00:00

Hello Team,

I am facing issue while trying to move Azure resources from one subscription to other subscription

As per Azure documentation, I first moved all dependent resources to same RG, then attempted with the move operation, but its failing with the validation error indicating that some resources are hosted in other RGs I have verified that all dependent resources are now located in same RG, I also deleted the previously hosted resource group, but the error persists. Please assist in identifying the case and provide guidance on how to successfully complete the move.

Error: This resource is located in resource group 'dit-dev', but hosted in the resource group 'installed-base-dev'. This may be a result of prior move operations. Move it back to respective hosting resource group.

Regards, Sathwik.

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

Answer accepted by question author
  1. Sandhya Kommineni 2,895 Reputation points Microsoft External Staff Moderator
    2025-10-15T04:40:35.9633333+00:00

    Hello Sathwik,

    Thanks for posting your question in Microsoft Q&A forum

    • This error typically occurs with PaaS (Platform as a Service) or nested Azure resources where the control plane (management metadata) and data plane (underlying hosted components) are associated with different resource groups.
    • In most cases, the issue arises from an incomplete or partially failed move operation. Although the resource now appears in the target resource group (dit-dev), its internal metadata or a dependent component still references the original hosting resource group (installed-base-dev).

    Deleting the old resource group does not remove these internal references, and in some cases, it can make recovery more complex. Azure’s validation process detects this inconsistency and prevents the move until the internal hosting link is corrected.

    To resolve this, verify the resource’s internal hosting relationship using the following command:

    az resource show --ids <resource-id> --query properties.hostingResourceGroupName
    
    • If it still points to the old group, recreate the resource group with the same name and move the resource back temporarily, if not contact Microsoft Support to reset the internal hosting reference.
    • Once the resource is successfully moved back, verify that all its dependent resources are in the same resource group. Ensure there are no dependencies still referencing another resource group.
    • Move the consolidated resource group (with all its dependent resources) to the target subscription and target resource group. Performing the move in a single operation ensures Azure updates both control plane and data plane metadata correctly
    • If you are unable to move the resource back due to the deleted hosting group, or if the move continues to fail, open a Microsoft Support ticket create an Azure support request, you can manage it in the Azure portal. to have the internal hostingResourceGroup reference reset.

    Referral documents:

    I hope the provided answer is helpful, do let me know if you have any further questions on this Please accept as Yes and upvote if the answer is helpful so that it can help others in the community.


0 additional answers

Sort by: Most helpful

Your answer

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