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

Question

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

1. Has anyone encountered this scenario after both the VM and the Recovery Services Vault were deleted?
2. Is there any supported customer method to clear the outstanding SAS (EndGetAccess) on an orphaned Disk Restore Point?
3. 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

1. Has anyone encountered this scenario after both the VM and the Recovery Services Vault were deleted?
2. Is there any supported customer method to clear the outstanding SAS (EndGetAccess) on an orphaned Disk Restore Point?
3. 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.

Answer 1

Hello @Ik

Thank you for reaching out to Microsoft Q&A. We apologize for the inconvenience caused by this issue.

Based on the information you provided, we would like to gather some additional details and perform a few validation steps. If you have PowerShell access, could you please run the following commands and share the results?

Key PowerShell Commands for Orphaned Restore Points collections cleanup:

1.** Connect to Azure and set the **subscription

Connect-AzAccount

Set-AzContext -SubscriptionId "<SubscriptionID>"

2.** Verify the Restore Point Collection **exists

Get-AzRestorePointCollection `

-ResourceGroupName "AzureBackupRG_canadacentral_1" `

-Name "AzureBackup_vm-monitor-test_862018736035475"

3.** List restore points within the **collection

$rpc = Get-AzRestorePointCollection `

-ResourceGroupName "AzureBackupRG_canadacentral_1" `

-Name "AzureBackup_vm-monitor-test_862018736035475"

$rpc.RestorePoints

4.** Attempt to delete individual restore **points

Remove-AzRestorePoint `

-ResourceGroupName "AzureBackupRG_canadacentral_1" `

-RestorePointCollectionName "AzureBackup_vm-monitor-test_862018736035475" `

-Name "<RestorePointName>"

5.** Attempt deletion of the Restore Point Collection via ARM REST **API

$resourceId = "/subscriptions/<subscription-id>/resourceGroups/AzureBackupRG_canadacentral_1/providers/Microsoft.Compute/restorePointCollections/AzureBackup_vm-monitor-test_862018736035475"

Invoke-AzRestMethod `

-Method DELETE `

-Path "$resourceId?api-version=2023-03-01"

6.** Check for remaining restore point **resources

Get-AzResource `

-ResourceGroupName "AzureBackupRG_canadacentral_1" |

Where-Object {$_.ResourceType -match "restorePoint"}

7.** Export resource details for support **escalation

Get-AzResource `

-ResourceGroupName "AzureBackupRG_canadacentral_1" `

-Name "AzureBackup_vm-monitor-test_862018736035475" `

-ResourceType "Microsoft.Compute/restorePointCollections" |

ConvertTo-Json -Depth 20 |

Out-File C:\Temp\RestorePointCollection.json

8.** Collect failed operation logs and correlation **IDs

Get-AzLog `

-ResourceGroupName "AzureBackupRG_canadacentral_1" `

-DetailedOutput |

Sort-Object EventTimestamp -Descending |

Select-Object -First 20

Once you have executed the commands, please share the outputs, especially any error messages, failed operations, activity logs, or correlation IDs. This information will help us investigate the orphaned Restore Point Collection further and determine the appropriate next steps.

We appreciate your cooperation and look forward to your update. Thank you.

Regards,

Venkat.M

Answer 2

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.

1. Log in to the Azure Portal.
2. In the global search bar at the top, type Help + support and select it from the results.
3. 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--