Share via

Cannot move resources across subscriptions

Capiteq Support 0 Reputation points
2026-03-03T02:15:37.18+00:00

Failing moving recovery service vault move across subscriptions

Azure Migrate
Azure Migrate

A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.

{count} votes

2 answers

Sort by: Most helpful
  1. Bharath Y P 5,800 Reputation points Microsoft External Staff Moderator
    2026-03-03T05:00:14.6066667+00:00

    Hello Capiteq Support, you are trying to move a Recovery Services Vault from one Azure subscription to another, and the move operation is failing. This typically happens because the vault contains configuration, backup data, or dependencies that Azure does not allow to be moved across subscriptions.

    A Recovery Services Vault cannot be moved across subscriptions if it contains any of the following:

    • Backup dependencies: A vault with active VM backups or Azure Site Recovery replication cannot be moved.
    • Region restrictions: Certain Azure regions don’t support vault moves.
    • Resource locks: Locks applied to the vault or resource group prevent changes.
    • Configuration gaps: Alerts, diagnostics, and firewall rules don’t migrate automatically, requiring manual reconfiguration.
    • Backup data is tied to the vault and cannot be transferred across subscriptions.

    Initial Steps to Check & Resolve this issue is

    Check for Backup Items:

    • Go to Azure portal > Vault > Backup Items
    • If anything exists: Stop backup, delete backup data or Remove backup policies.

    Disable Soft Delete:

    • Go to Azure portal > Vault > Properties
    • Security Settings > Disable Soft Delete temporarily.

    Delete soft-deleted items permanently. Soft delete retention (14 days) blocks vault move.

    Secure by Default with Soft Delete for Azure Backup - Azure Backup | Microsoft Learn

    Check for Azure Site Recovery: If ASR was ever enabled

    • Go to Azure portal >Vault > Site Recovery Infrastructure
    • Remove: Replicated items, Protection containers, Fabrics or Policies

    ASR configuration blocks move even if replication is stopped.

    Remove Registered Servers: If using MARS agent:

    • Go to Azure portal > Vault > Backup Infrastructure > Registered Servers > Unregister all servers.

    Delete Private Endpoints:

    • Go to Azure portal > Vault > Networking
    • Remove any private endpoint connections.

    Remove Locks:

    • Go to Azure portal > Vault > Locks > Delete any: CanNotDelete or ReadOnly

    Here is the Document that contains instructions for removing dependencies before deleting the vault Delete a Microsoft Azure Recovery Services Vault - Azure Backup | Microsoft Learn

    If all the above steps verified now you can try move. If still blocked, it means backend metadata still exists.

    Some of the useful References documents:

    1. Move resources to a new resource group or subscription
    2. Move Azure Site Recovery (Recovery Services vaults)
    3. Troubleshoot moving Azure resources between subscriptions
    4. Move operation support for resources
    0 comments No comments

  2. Marcin Policht 82,360 Reputation points MVP Volunteer Moderator
    2026-03-03T02:27:12.2066667+00:00

    Follow https://robertsmit.wordpress.com/2023/08/15/move-a-recovery-services-vault-across-azure-subscriptions-and-resource-group-backup-asr-azure-itpro-powershell/


    If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    hth

    Marcin

    0 comments No comments

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.