Disk Storage: Dependency Issue Preventing Resource Deletion — Managed Disk No Longer Visible in Portal

Question

Disk Storage: Dependency Issue Preventing Resource Deletion — Managed Disk No Longer Visible in Portal

Josh Haley 0

Problem description

I am unable to delete all resources related to my Azure environment because a managed disk that was previously attached to a virtual machine still appears to be in use, even though it has since been deleted and shows a 404 error when attempting to access. Attempts to remove the disk and associated resources fail with errors indicating a dependency or resource in use.

All resources except for this disk, its restore point collection, and that collection's resource group have been successfully deleted.

Environment

Azure Disk Storage in Australia East region, involving a managed disk, backup restore points in a Recovery Services vault, and related VM resources.

What I've already tried

I have tried deleting the resource directly, via the portal and powershell. I have checked for soft-delete and SAS permissions. I have attempted to force-delete the disk but as there is no disk to delete it has been unsuccessful.

Current status

I am seeking assistance to identify the lingering dependency preventing resource deletion and to perform a force delete of all related resources to free my account and continue my studies.

Isuru Heendeniya 70 Reputation points

2026-08-28T20:52:27.47+00:00

Hi all,

This might be the reason for this behaviour.

https://docs.azure.cn/en-us/site-recovery/azure-to-azure-how-to-enable-zone-to-zone-disaster-recovery

Thank you

Kind regards

Isuru

1 answer

Your answer

Isuru Heendeniya 70 Reputation points

2026-08-28T20:52:27.47+00:00

Hi all,

This might be the reason for this behaviour.

https://docs.azure.cn/en-us/site-recovery/azure-to-azure-how-to-enable-zone-to-zone-disaster-recovery

Thank you

Kind regards

Isuru

Answer 1

Hello Josh Haley

This looks much more like an orphaned Restore Point Collection / Disk Restore Point dependency than a managed-disk problem.

The fact that the original managed disk now returns 404 is expected after deletion. Trying to force-delete that disk will not help because the resource Azure is refusing to remove is probably a child restore-point object that still contains a reference to the deleted disk.

The remaining restore-point objects can still reference it and block deletion.

Try:

az resource list \   --resource-type Microsoft.Compute/restorePointCollections \   -o table

Then delete the collection:

az restore-point collection delete \   --resource-group <RG> \   --collection-name <collection-name> \   --yes

If deletion fails, check for:

nested Disk Restore Points
an active SAS on a Disk Restore Point
resource locks
a remaining/soft-deleted VM backup item in the Recovery Services vault

Also check the Activity Log for the failed DELETE operation the exact error.code and error.message should identify the remaining dependency.

If the collection cannot be deleted even after all dependencies are gone, it may be orphaned Azure backend metadata and require an Azure Support cleanup.