Unable to delete Replicated Item from RSV

Hello Lakhan Rohilla

From your screenshot, the replicated item “Demovm” shows Replication Health = Healthy but Status = “Disabling protection”, and the active location is “MyDemoProject‑HyperVSite” (Failover health “–”). That pattern usually means the disable/cleanup operation is stuck and the portal can’t complete the final delete.

You uninstalled the Hyper‑V Provider while replication/disable was still in progress, so the service that ASR/Azure Migrate uses to “cleanly” disable protection and remove the protected item can’t complete the workflow. When the source side is missing/not reachable, Use Remove (instead of “Disable replication and remove”) because it stops billing and removes the item from ASR without cleaning on‑prem configuration.

If the item is already stuck in “Disabling protection”, you often need to force-remove the protected item record via CLI/PowerShell/REST (depending on whether it’s an ASR protected item or an Azure Migrate Data Replication protected item).

Please have a look into below Workaround:

A. If this is an Azure Site Recovery (ASR) replicated item (Microsoft.RecoveryServices…)

Microsoft documents two different operations:

• remove = clean disable replication (and remove the item)
• delete = force delete / purge the replication protected item

List protected items (to confirm fabric/container/item names):

Open Azure CLI and try below commands:

az site-recovery protected-item list \
  --resource-group <vaultRG> \
  --vault-name <vaultName> \
  --fabric-name <fabricName> \
  --protection-container-name <containerName>

2. Try clean remove first:

az site-recovery protected-item remove \
  --resource-group <vaultRG> \
  --vault-name <vaultName> \
  --fabric-name <fabricName> \
  --protection-container-name <containerName> \
  --replicated-protected-item-name <protectedItemName>

3. If it’s still stuck → force delete/purge:

az site-recovery protected-item delete \
  --resource-group <vaultRG> \
  --vault-name <vaultName> \
  --fabric-name <fabricName> \
  --protection-container-name <containerName> \
  --replicated-protected-item-name <protectedItemName>

4. As an alternative try Remove-AzRecoveryServicesAsrReplicationProtectedItem to disable replication for an ASR replication protected item and supports -Force and -WaitForCompletion.

“Remove-AzRecoveryServicesAsrReplicationProtectedItem … disables replication … and causes replication to stop for the protected item.”

# After you obtain the ASR replication protected item object ($rpi):
Remove-AzRecoveryServicesAsrReplicationProtectedItem -InputObject $rpi -Force -WaitForCompletion

Reference: https://learn.microsoft.com/en-us/powershell/module/az.recoveryservices/remove-azrecoveryservicesasrreplicationprotecteditem?view=azps-15.4.0

If you prefer ARM calls, use below REST API:

ASR “disable replication/remove” is also exposed as a REST operation: POST .../replicationProtectedItems/{name}/remove?api-version=2025-08-01

Reference: https://learn.microsoft.com/en-us/rest/api/site-recovery/replication-protected-items/delete?view=rest-site-recovery-2025-08-01&tabs=HTTP

B. If your replication item is under Microsoft.DataReplication/replicationVaults/protectedItems, Microsoft’s REST API supports force delete via forceDelete=true.

You need to use PowerShell (Invoke-AzRestMethod) to delete stuck protected item:

Connect-AzAccount
Set-AzContext -Subscription "<subscriptionId>"

$sub = "<subscriptionId>"
$rg  = "<resourceGroupName>"
$rv  = "<replicationVaultName>"
$api = "2024-09-01"

# 1) List protected items
$items = Invoke-AzRestMethod -Method GET -Path "/subscriptions/$sub/resourceGroups/$rg/providers/Microsoft.DataReplication/replicationVaults/$rv/protectedItems?api-version=$api"
$items.Content

# 2) Delete the specific protected item (use the protectedItemName you find above)
$pi = "<protectedItemName>"   # often looks like a GUID/name shown in the JSON
Invoke-AzRestMethod -Method DELETE -Path "/subscriptions/$sub/resourceGroups/$rg/providers/Microsoft.DataReplication/replicationVaults/$rv/protectedItems/$pi?api-version=$api"

# 3) If normal delete fails, force delete
Invoke-AzRestMethod -Method DELETE -Path "/subscriptions/$sub/resourceGroups/$rg/providers/Microsoft.DataReplication/replicationVaults/$rv/protectedItems/$pi?api-version=$api&forceDelete=True"

After this, refresh Azure Migrate/RSV views; the protected item record should disappear once the delete operation completes.

Important Note:

1. If you choose “Remove” (portal/CLI remove) when the source is unavailable, Microsoft notes that on‑prem replication configuration will not be cleaned up (because the source environment isn’t reachable).
2. A force delete/purge is effectively “backend cleanup” of the Azure record—use it only when the clean remove path is stuck and you’re sure you don’t need that replication metadata anymore.

When you click the stuck replicated item and look at its Resource ID, does it contain Microsoft.DataReplication or Microsoft.RecoveryServices?

• Microsoft.DataReplication → use Option B (Invoke-AzRestMethod forceDelete)
• Microsoft.RecoveryServices → use Option A (az site-recovery protected-item delete/remove or Remove-AzRecoveryServicesAsrReplicationProtectedItem)

Kindly let us know if the solution provided worked for you.

If you need any further assistance, please feel free to reach out.

If you found the comment helpful, please consider clicking "Upvote it".

Thanks,

Suchitra.