unable to delete recovery service vault

Hello Satish, it usually comes down to "there’s something still in the vault" blocking the delete. Here’s a quick checklist to work through:

1. Check for Azure Site Recovery items
   • Go into your Recovery Services vault > “Site Recovery Infrastructure” > “Replicated items” (or “Servers”/“Jobs”).
   • Remove any protected items (VMs, servers) and unregister servers.
   • Follow the step-by-step for your scenario: Azure VM, VMware to Azure, Hyper-V (with/without VMM).   Delete an Azure Site Recovery vault - Azure Site Recovery | Microsoft Learn Delete an Azure Site Recovery vault - Azure Site Recovery | Microsoft Learn Delete an Azure Site Recovery vault - Azure Site Recovery | Microsoft Learn
2. If you used Azure Migrate
   • Delete your Migrate project first (this removes discovered‐machine metadata).
   • Remove any replicated items per your VM scenario (same links as above). Create and manage projects - Azure Migrate | Microsoft Learn
3. Backup items & soft-deleted data • In the vault, go to Backup items and delete every active backup instance. • If soft delete is enabled, you’ll need to undelete the items and delete them again or disable soft delete (may require privileged approval). – https://docs.microsoft.com/azure/backup/backup-azure-delete-vault?tabs=portal – https://docs.microsoft.com/azure/backup/secure-by-default?tabs=preview#disable-soft-delete-action
4. Force-delete via PowerShell (if you just want to blow everything away – irreversible!)

Connect-AzAccount 
Select-AzSubscription -SubscriptionName "YourSubscription" $vault = Get-AzRecoveryServicesVault -Name "YourVaultName" Remove-AzRecoveryServicesVault -Vault $vault

Delete an Azure Site Recovery vault - Azure Site Recovery | Microsoft Learn

Once all of the above are gone, head back to the portal and hit Delete on the vault it should finally succeed.

Hope that Helps! If you still see an error, let me know:

• What error code/message do you get when you try to delete?

• Which scenario did you use the vault for (Site Recovery, Backup, Migrate)?

• Have you already removed all “Backup items,” “Site Recovery” entries, and any soft-deleted data?

Reference (all from Microsoft Docs):

• Delete a Vault – Azure Site Recovery (remove registered servers & items)

• Delete a Vault – Azure Migrate (remove project & items)

• Delete a Recovery Services Vault – Azure Backup (portal + PowerShell)

• Resolve Vault Deletion Issues Due to Soft-Deleted Items

• Use PowerShell to Force-Delete a Vault and Dependencies

Please feel free to reach out if you have any further questions.

To delete a Recovery Services vault, all dependencies must be removed first. A vault cannot be deleted if it:

1. Contains protected data sources (for example, IaaS VMs, SQL databases, Azure file shares).
2. Contains backup data (including items in soft-deleted state).
3. Has registered storage accounts.
4. Has protected/on-premises servers or backup management servers registered.

If any of these exist, vault deletion fails with errors such as:

• “Vault cannot be deleted as there are existing resources within the vault…”
• “Recovery Services vault cannot be deleted as there are backup items in soft deleted state in the vault…”

Use the following steps in the Azure portal to unblock deletion:

1. In the Recovery Services vault, go to Overview and select Delete.
   • Follow the guided flow; it opens blades for each dependency (backup items, protected servers, storage accounts, Site Recovery items, etc.).
2. If multiuser authorization (MUA) is enabled, obtain required approval from the security administrator before performing critical delete operations.
3. Disable security features that can block deletion:
   • Go to Properties → Security Settings.
   • Disable Soft Delete (and Security Features if enabled).
   • If Soft Delete is Enabled with always on, vault deletion cannot proceed until that configuration is changed.
4. Delete all cloud backup items:
   • Go to Backup items in the vault.
   • For each backup type (Azure VMs, Azure Storage, Azure Files, SQL in Azure VMs, etc.):
     • Select the item.
     • Use Stop Backup and choose Delete Backup Data, or directly Delete Backup Data where shown.
     • Confirm by entering the item name and complete the operation.
   • Refresh Backup items and ensure all lists are empty.
5. Handle soft-deleted items:
   • After disabling Soft Delete, check for items in soft-deleted state.
   • Restore them, then delete again so they are permanently removed.
   • Vault deletion is blocked until no items remain in soft-deleted state.
6. Clean up on-premises/MARS/MABS/DPM dependencies (if used):
   • In the vault, go to Backup Infrastructure.
   • Under Protected Servers and Backup Management Servers, delete/unregister all servers after deleting their backup data (via MARS, MABS, or DPM consoles as applicable).
7. Unregister storage accounts:
   • In Backup Infrastructure → Storage Accounts, unregister all listed storage accounts.
8. Remove private endpoints:
   • Go to Settings → Networking → Private access.
   • Remove any private endpoint connections associated with the vault.
9. Delete the vault:
   • In the vault, verify in the Essentials pane that there are no backup items, protected servers, backup management servers, or replicated items.
   • Select Delete on the vault dashboard and confirm.

If all dependencies are removed and deletion still fails, use one of these automation options:

• PowerShell script (recommended):
  • From the vault Overview, choose Delete → Delete using PowerShell Script → Generate and Download Script.
  • Run the script in PowerShell 7; it will:
    1. Disable soft delete and security features.
    2. Delete backup items.
    3. Unregister servers and storage accounts.
    4. Delete disaster recovery items.
    5. Remove private endpoints.
    6. Delete the vault.
• ARMClient (last resort when portal delete still fails with no dependencies):
  • After confirming the vault is empty, use ARMClient.exe delete against the vault resource ID as documented to force deletion.

If the vault contains only Azure VM backups, the Azure CLI can also be used:

1. Disable protection and delete backup data with az backup protection disable --delete-backup-data.
2. Then delete the vault with az backup vault delete.

Once all dependencies (including soft-deleted items) are removed, the Recovery Services vault deletion will succeed.

References:

• Delete an Azure Backup Recovery Services vault
• PowerShell script to delete a Recovery Services vault
• Delete a Recovery Services vault
• PowerShell
• CLI
• Azure Resource Manager
• Tutorial: Manage the resiliency estate using Copilot
• Remove-AzRecoveryServicesVault
• No option to stop or delete - Microsoft Q&A