An Azure backup service that provides built-in management at scale.
Can not delete Azure Backup Resource Group
Remove-AzRestorePoint: Long running operation failed with status 'Failed'. Additional Info:'There is an active shared access signature outstanding for disk restore point data_30ae2a8e-b5a9-4488-ab14-3270f3aa6783. Call EndGetAccess before deleting the VM restore point AzureBackup_20260319_081614.'
ErrorCode: DiskRestorePointUsedByCustomer
ErrorMessage: There is an active shared access signature outstanding for disk restore point data_30ae2a8e-b5a9-4488-ab14-3270f3aa6783. Call EndGetAccess before deleting the VM restore point AzureBackup_20260319_081614.
Azure Backup
-
Siva shunmugam Nadessin • 7,645 Reputation points • Microsoft External Staff • Moderator
2026-03-20T05:50:55.73+00:00 Hello VI,
Thank you for reaching out to the Microsoft Q&A forum.
By investigating What it means
Azure is telling you that the VM restore point cannot be deleted because there’s an active SAS (Shared Access Signature) session open on one of its disks:
A process previously called Grant-AzDiskAccess (or similar API)
That session hasn’t been properly closed.
So Azure blocks deletion to prevent data corruption.
The Root cause is The key part of your error:
“Call EndGetAccess before deleting the VM restore point”
This means:
- A disk inside the restore point (data_30ae2a8e...) is still exposed via SAS
- You must explicitly revoke that access.
You can Fix using PowerShell command
Run this to revoke the SAS access:
Revoke-AzDiskAccess ` -ResourceGroupName <RG_NAME> ` -DiskName data_30ae2a8e-b5a9-4488-ab14-3270f3aa6783Important:
- The disk name comes directly from your error message
- This is not your VM disk, it’s the restore point disk
Then retry deletion
Remove-AzRestorePoint
-ResourceGroupName <RG_NAME>-RestorePointCollectionName <COLLECTION_NAME> ` -Name AzureBackup_20260319_081614If it still fails
Check for any active access on restore point disks:
Get-AzDisk | Where-Object {$_.DiskState -eq "ActiveSAS"}If found, revoke them all:
Get-AzDisk | Where-Object {$_.DiskState -eq "ActiveSAS"} | ForEach-Object { Revoke-AzDiskAccess -ResourceGroupName $_.ResourceGroupName -DiskName $_.Name }Hope this helps!! If you have further questions let us know.
-
VI • 0 Reputation points
2026-03-20T07:01:14.9366667+00:00 Revoke-AzDiskAccess -ResourceGroupName AzureBackupRG_eastus2_1 -DiskName data_30ae2a8e-b5a9-4488-ab14-3270f3aa6783
Revoke-AzDiskAccess: The Resource 'Microsoft.Compute/disks/data_30ae2a8e-b5a9-4488-ab14-3270f3aa6783' under resource group 'AzureBackupRG_eastus2_1' was not found. For more details please go to https://aka.ms/ARMResourceNotFoundFix
ErrorCode: ResourceNotFound
ErrorMessage: The Resource 'Microsoft.Compute/disks/data_30ae2a8e-b5a9-4488-ab14-3270f3aa6783' under resource group 'AzureBackupRG_eastus2_1' was not found. For more details please go to https://aka.ms/ARMResourceNotFoundFix
ErrorTarget:
StatusCode: 404
ReasonPhrase: Not Found
OperationID : 72f11ff2-5ca4-46e2-9e4d-dc66064e8cef
There is no Resource Group other then AzureBackupRG_eastus2_1
There is no disks: Get-AzDisk return nothing
-
Siva shunmugam Nadessin • 7,645 Reputation points • Microsoft External Staff • Moderator
2026-03-20T08:05:22.3566667+00:00 Hello VI
This actually tells us something important. You’re looking in the wrong resource type 👍
That disk in the error:
data_30ae2a8e-b5a9-4488-ab14-3270f3aa6783
is NOT a normal managed disk (Microsoft.Compute/disks) It’s a restore point disk under:
Microsoft.Compute/restorePointCollections/restorePoints/disks
That’s why:
- Get-AzDisk → returns nothing
- Revoke-AzDiskAccess → 404 Not Found
The correct fix is to use the Restore Point Disk APIs
You need to revoke access using Restore Point Disk cmdlets, not regular disk cmdlets.
Step 1 — Get the restore point
$rp = Get-AzRestorePoint ` -ResourceGroupName AzureBackupRG_eastus2_1 -RestorePointCollectionName <COLLECTION_NAME> ` -Name AzureBackup_20260319_081614Step 2 — Identify the disk
$rp.DisksYou should see something like:
Name : data_30ae2a8e-b5a9-4488-ab14-3270f3aa6783
Step 3 — Revoke access (THIS is the key)
Revoke-AzRestorePointCollectionDiskAccess ` -ResourceGroupName AzureBackupRG_eastus2_1 ` -RestorePointCollectionName <COLLECTION_NAME> -RestorePointName AzureBackup_20260319_081614 ` -DiskRestorePointName data_30ae2a8e-b5a9-4488-ab14-3270f3aa6783Step 4 — Retry delete
Remove-AzRestorePoint ` -ResourceGroupName AzureBackupRG_eastus2_1 ` -RestorePointCollectionName <COLLECTION_NAME> ` -Name AzureBackup_20260319_081614If the cmdlet is missing
Some Az modules don’t expose this yet. Then use REST fallback:
$subId = "<subscription-id>" $uri = "https://management.azure.com/subscriptions/$subId/resourceGroups/AzureBackupRG_eastus2_1/providers/Microsoft.Compute/restorePointCollections/<COLLECTION_NAME>/restorePoints/AzureBackup_20260319_081614/disks/data_30ae2a8e-b5a9-4488-ab14-3270f3aa6783/endGetAccess?api-version=2023-03-01" Invoke-AzRestMethod -Method POST -Uri $uriLet me know if you have further queries?
-
VI • 0 Reputation points
2026-03-20T16:39:20.67+00:00 Hello,
Get-AzRestorePoint does not return any disks. See below:
Get-AzRestorePoint
-ResourceGroupName AzureBackupRG_eastus2_1 -RestorePointCollectionName AzureBackup_vmd-001-mro_5414399877361477203-Name AzureBackup_20260319_081614SourceMetadata : Microsoft.Azure.Management.Compute.Models.RestorePointSourceMetadata
ProvisioningState : Failed
ConsistencyMode : CrashConsistent
ExcludeDisks : {}
InstanceView :
TimeCreated : 3/19/2026 8:16:20 PM
Invoke-AzRestMethod return:
Invoke-AzRestMethod -Method POST -Uri $uri
StatusCode : 400
Content : {
"error": { "innererror": { "internalErrorCode": "RequestUrlInvalid" }, "code": "BadRequest", "message": "The request URL is not valid." } }Headers : {
"Cache-Control": "no-cache", "Pragma": "no-cache", "Strict-Transport-Security": "max-age=31536000; includeSubDomains", "x-ms-request-id": "97a67b4a-8ad8-48b5-a124-f926ecbf6f03", "x-ms-operation-identifier": "tenantId=100a79ee-e1bc-4b8c-9fea-411535978e4e,objectId=a36700f8-201d-4ebf-8209-95a19c381d74/eastus2/fefaf763-5226-4eac-b0d7-0e4547971d1a", "x-ms-ratelimit-remaining-subscription-writes": "199", "x-ms-ratelimit-remaining-subscription-global-writes": "2999", "x-ms-correlation-request-id": "ff5f88b9-bd76-4a08-aafb-1dac5bb6d11c", "x-ms-routing-request-id": "EASTUS2:20260320T163706Z:ff5f88b9-bd76-4a08-aafb-1dac5bb6d11c", "X-Content-Type-Options": "nosniff", "X-Cache": "CONFIG_NOCACHE", "X-MSEdge-Ref": "Ref A: FCA1CC18EED84AA2A21A74341FD70D6C Ref B: BL2AA2010204035 Ref C: 2026-03-20T16:37:06Z", "Date": "Fri, 20 Mar 2026 16:37:06 GMT" }Method : POST
d-001-mro_5414399877361477203/restorePoints/AzureBackup_20260319_081614/disks/data_30ae2a8e-b5a9-4488-ab14-3270f3aa6783/endGetAccess?api-version=2023-03-01Version : 1.1
-
VI • 0 Reputation points
2026-03-20T20:02:43.07+00:00 The real problem is the VM and vault was deleted first and the restore point becomes orphaned. Not sure how to fix it.
-
VI • 0 Reputation points
2026-03-20T20:06:26.3666667+00:00 the VM and the vault was deleted first and the restore point becomes orphaned. How to fix it I need to delete the AzureBackupRG_eastus2_1 as it is the only resource remained.
-
Naveena Patlolla • 9,310 Reputation points • Microsoft External Staff • Moderator
2026-03-25T10:57:57.4633333+00:00 Hello VI
Could you please respond in private message? -
Naveena Patlolla • 9,310 Reputation points • Microsoft External Staff • Moderator
2026-03-26T05:09:05.52+00:00 Hello VI
If both manual and script-based methods fail to delete the orphaned restore point collection (RPC), it will need to be removed from the backend by Microsoft.Could you please provide the additional details requested via private message so we can proceed further?
Sign in to comment