Unable to delete Restore Point Collection

Sarah Ashlie 40 Reputation points
2026-09-26T06:06:32.6366667+00:00

I have a restore point collection created automatically by Azure Backup, and I am unable to delete it. All related resources (VM, disks, snapshots, vault, etc.) have already been deleted as part of a lab environment cleanup.

The restore point collection details:

RG: AzureBackupRG_westus2_1

Location: West US 2

Resource Type: Microsoft.Compute/restorePointCollections

Name: AzureBackup_nw-app01_7661713682812430095

ProvisioningState: Failed

Inside the collection there is a single restore point with a disk restore point. Trying to delete the restore point or the collection returns the following error:

(DiskRestorePointUsedByCustomer) Resource:'AZUREBACKUPRG_WESTUS2_1/AzureBackup_20260925_072155', Message:There is an active shared access signature outstanding for disk restore point NW-APP01_OsDisk_1_8fe21dd408474349bf5a301caf02f1af_17e0b702-9edd-45e3-90d3-672957b87299. Call EndGetAccess before deleting the VM restore point AzureBackup_20260925_072155.

Code: DiskRestorePointUsedByCustomer

Message: Resource:'AZUREBACKUPRG_WESTUS2_1/AzureBackup_20260925_072155', Message:There is an active shared access signature outstanding for disk restore point NW-APP01_OsDisk_1_8fe21dd408474349bf5a301caf02f1af_17e0b702-9edd-45e3-90d3-672957b87299. Call EndGetAccess before deleting the VM restore point AzureBackup_20260925_072155.

The disk itself does not exist (when I click the link for the disk in the restore point, it says Resource Not Found).

Thank you in advance to anyone who can help me delete this remaining this remaining Restore Point Collection!

Azure Backup
Azure Backup

An Azure backup service that provides built-in management at scale.

0 comments
Answer accepted by question author
Taz 10,126 Reputation points MVP Volunteer Moderator
2026-09-26T17:49:35.88+00:00

Hi Sarah,

The DiskRestorePointUsedByCustomer error is caused by an active SAS access lease on the disk restore point. Azure's supported operation is EndGetAccess to revoke that access before deleting the restore point.

In your case, the underlying disk, VM, and Recovery Services vault have already been deleted. That leaves the restore point referencing a resource that no longer exists, so the normal EndGetAccess operation cannot be completed.

There is a directly matching Microsoft Q&A case where the VM, vault, and disk were deleted and the same error remained. Microsoft staff confirmed that this becomes an orphaned restore-point metadata state and requires Microsoft Support to perform backend cleanup.

I would open an Azure Support case and provide:

Restore Point Collection:
AzureBackup_nw-app01_7661713682812430095

Resource Group:
AzureBackupRG_westus2_1

Error:
DiskRestorePointUsedByCustomer

The referenced disk no longer exists and the VM/Recovery Services vault
have already been deleted. Please perform backend cleanup of the
orphaned disk restore point/SAS lease so the Restore Point Collection
can be deleted.

Do not delete/recreate unrelated resources. The collection itself is normally deletable, but the outstanding SAS must first be cleared.

Was this answer helpful?

2 people found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

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.