Unable to delete orphaned Azure Backup Restore Point Collection (DiskRestorePointUsedByCustomer)

Question

Unable to delete orphaned Azure Backup Restore Point Collection (DiskRestorePointUsedByCustomer)

Ik 0

I'm looking for advice on what appears to be an orphaned Azure Backup Restore Point Collection. At this point I believe the issue requires Microsoft backend intervention, but I'd like to confirm there isn't a supported customer-side solution that I've missed.

Environment

Region: Canada Central

Resource Group:

AzureBackupRG_canadacentral_1

Restore Point Collection:

AzureBackup_vm-monitor-test_862018736035475

Current state

The original VM (vm-monitor-test) has been deleted.
The associated Recovery Services Vault has been deleted.
The Restore Point Collection still exists.
Provisioning State = Failed.
The Azure portal cannot delete the Restore Point Collection.
Azure CLI also fails.

Azure CLI error

Troubleshooting completed

Verified there are no resource locks.
Confirmed the VM has been deleted.
Confirmed the Recovery Services Vault has been deleted.
The Restore Point Collection remains in ProvisioningState = Failed.

Documentation reviewed

Microsoft documentation states that the DiskRestorePointUsedByCustomer error is resolved by calling EndGetAccess on the underlying Disk Restore Point before deleting the Restore Point Collection.

However, in my case there is no remaining customer-accessible resource capable of invoking EndGetAccess because:

the VM no longer exists,
the Recovery Services Vault no longer exists,
the backup item no longer exists.

This appears to have left an orphaned Disk Restore Point with an outstanding SAS that cannot be released through customer APIs.

Questions

Has anyone encountered this scenario after both the VM and the Recovery Services Vault were deleted?
Is there any supported customer method to clear the outstanding SAS (EndGetAccess) on an orphaned Disk Restore Point?
If not, does this require Microsoft to perform backend cleanup?

My goal is simply to remove the orphaned Restore Point Collection so that the resource group can be deleted.

Any guidance would be appreciated.I'm looking for advice on what appears to be an orphaned Azure Backup Restore Point Collection. At this point I believe the issue requires Microsoft backend intervention, but I'd like to confirm there isn't a supported customer-side solution that I've missed.

Environment

Region: Canada Central

Resource Group:

AzureBackupRG_canadacentral_1

Restore Point Collection:

AzureBackup_vm-monitor-test_862018736035475

Current state

The original VM (vm-monitor-test) has been deleted.
The associated Recovery Services Vault has been deleted.
The Restore Point Collection still exists.
Provisioning State = Failed.
The Azure portal cannot delete the Restore Point Collection.
Azure CLI also fails.

Azure CLI error

Troubleshooting completed

Verified there are no resource locks.
Confirmed the VM has been deleted.
Confirmed the Recovery Services Vault has been deleted.
The Restore Point Collection remains in ProvisioningState = Failed.

Documentation reviewed

Microsoft documentation states that the DiskRestorePointUsedByCustomer error is resolved by calling EndGetAccess on the underlying Disk Restore Point before deleting the Restore Point Collection.

However, in my case there is no remaining customer-accessible resource capable of invoking EndGetAccess because:

the VM no longer exists,
the Recovery Services Vault no longer exists,
the backup item no longer exists.

This appears to have left an orphaned Disk Restore Point with an outstanding SAS that cannot be released through customer APIs.

Questions

Has anyone encountered this scenario after both the VM and the Recovery Services Vault were deleted?
Is there any supported customer method to clear the outstanding SAS (EndGetAccess) on an orphaned Disk Restore Point?
If not, does this require Microsoft to perform backend cleanup?

My goal is simply to remove the orphaned Restore Point Collection so that the resource group can be deleted.

Any guidance would be appreciated.

0 comments

1 answer

Your answer

Answer 1

Megha Ramakrishnan 335

Hi @Ik

This issue happens when a Recovery Services Vault or a VM is forcefully deleted while a backup snapshot operation was hanging, active, or in a Failed provisioning state, leaving an inconsistent state in the backend.

From the your side, you cannot do anything on this issue since the VM and vault have already been deleted.

To help resolve your issue, please create a support ticket in the Azure portal.

Log in to the Azure Portal.
In the global search bar at the top, type Help + support and select it from the results.
On the Help + support home page, click the Create a support request button. Provide the below details in the description also the summary of your issue.
Subscription ID: [Your Subscription ID]

Resource Group: AzureBackupRG_canadacentral_1

Orphaned Resource: AzureBackup_vm-monitor-test_862018736035475 (Type: Microsoft.Compute/restorePointCollections)

--please don't forget to close up the thread here by marking answer if the reply is helpful--

Onyebuchi Judith Igboabuchukwu 0 Reputation points

2026-07-26T22:56:25.16+00:00

Hello Megha,

Since this has been confirmed as a backend issue with no customer remediation available, could this thread be escalated to the Azure Compute/Azure Backup engineering team, or could you advise an alternative process for Basic support customers?
Ik 0 Reputation points

2026-07-27T00:00:35.9333333+00:00

Hi @Megha Ramakrishnan

Thanks for confirming. That matches everything I found while troubleshooting on my end (Azure Portal, Azure CLI, az resource delete against both the Restore Point Collection and the Restore Point, Resource Explorer, and a forced resource group deletion, which Azure rolled back citing this Restore Point Collection as the blocking resource).

One issue with creating a support request is that this subscription is on the Basic Azure support plan, so Create a support request only offers billing, subscription management, and quota-related requests. I don't have an option to open a technical support case.

Since you've confirmed this is a backend inconsistency and there is no customer-side remediation because both the VM and the Recovery Services Vault have already been deleted, is there a way to have this routed to the appropriate Azure Compute/Azure Backup team without upgrading to a paid support plan?

For reference, here are the resource details:

Subscription ID: 168f4948-8c3b-442f-8ea1-9bd49a05bc6e

Resource Group: AzureBackupRG_canadacentral_1

Restore Point Collection: AzureBackup_vm-monitor-test_862018736035475

Restore Point: AzureBackup_20260724_063716

Disk Restore Point: vm-monitor-test_OsDisk_1_d0148b8fcbb944d092d9455095b54b08_fcd088b1-26a0-411d-8409-3ee7c6e2683b

Resource Group deletion tracking ID: baaaaffc-ccfe-4da7-beeb-2f99ff51eb07

Please let me know if there's any additional information or diagnostic output I can provide.

Thank you.