Resource move blocked by stale DiskHasRestorePoints

Hello @Brian Peterson We are looking into this issue and will keep you posted updates.

Thanks,

Suchitra.

Hello @Brian Peterson

Resource move is blocked with DiskHasRestorePoints, even though:

• Azure VM backup was stopped with “Retain data”
• Recovery Services Vault shows zero protected items
• PowerShell confirms no backup containers or items
• No restore point collections are visible in the portal

The move validation still fails for the managed disk:

/providers/Microsoft.Compute/disks/MCT-AZ-SVR01_disk1_...

When Azure VM Backup is stopped with Retain data, Azure does not automatically delete the Instant Restore snapshots (restore point collections) created for that disk.

These restore points are stored as hidden RestorePointCollection resources under an AzureBackupRG_ resource group*. Even if:

• The vault has no protected items
• PowerShell shows no backup containers
• The portal shows no visible restore points

The managed disk metadata still indicates restore points exist, which causes Azure Resource Move to block the operation with DiskHasRestorePoints.

Azure Resource Move explicitly blocks disks that have any restore points, regardless of whether the backup is active or visible in the vault.

Please try below workarounds:

1. Locate the hidden Azure Backup resource group

Look for a resource group named:

AzureBackupRG_<region>_<number>

These resource groups are created automatically by Azure Backup and are hidden by default.

2. Show hidden resources

In that resource group:

1. Open Resource Group
2. Select “Show hidden types”
3. Look for resources of type:

Microsoft.Compute/restorePointCollections

3. Delete the Restore Point Collection:

Delete the restore point collection associated with the disk.

Deleting the restore point collection permanently removes all instant recovery points for that disk and cannot be undone. This is expected behavior when backups were stopped with Retain data.

4. Retry the resource move

After deletion:

• Re‑run Move validation
• The DiskHasRestorePoints error will no longer occur
• The disk can now be moved successfully

Azure Resource Move validates disk‑level restore points, not vault‑level backup items.

The move is blocked because hidden Azure Backup restore point collections still exist for the disk. Stopping backup with Retain data does not delete restore points. Manually deleting the RestorePointCollection from the AzureBackupRG_* resource group clears the DiskHasRestorePoints flag and allows the move.

Thanks,
Suchitra.

This was already done. I have co-pilot and that is the exact response it gave me, I don't have any resources hidden or otherwise with the AzureBackupRG* name in the resource group.

This was already done. I have co-pilot and that is the exact response it gave me, I don't have any resources hidden or otherwise with the AzureBackupRG* name in the resource group.

Hi Brian Peterson

Since no restore point collections exist and all backup artifacts are already removed, the DiskHasRestorePoints error is caused by a stale internal disk metadata flag that requires Backend support to clear at the Compute control plane level.

We have asked few details via Private message. Please have a look into it and share us the details for further assistance on this issue.

Thanks,

Suchitra.