Azure Backup: Old recovery points not deleting despite expiry — Need backend cleanup

Question

Azure Backup: Old recovery points not deleting despite expiry — Need backend cleanup

Jeremy Kropf 25

Problem description

I am experiencing an issue where two old recovery points from March 2023 remain in my Azure Backup vault, even though the retention policy was shortened over a year ago and those points are well past their expiry date (also in 2023). Despite running on-demand backups and policy re-evaluation, these recovery points persist and are not automatically deleted. Current daily backups are all functioning and pruning as expected.

Environment

Azure Backup protecting an Azure VM in a vault.

What I've already tried

I reviewed the available recovery points and confirmed the presence of two from March 2023. I verified that daily backups are ongoing and that the backup policy was changed to a shorter retention period more than a year ago. I also ran on-demand backups and re-evaluated the policy; however, these older points remained. I reviewed documentation indicating that retention changes do not immediately delete recovery points and that backend garbage collection may cause delays.

Current status

I am seeking guidance on how to manually clean up these orphaned recovery points from the backend, possibly through escalation or triggering a manual garbage collection sweep, as they are no longer supposed to be retained.

Hemant Bharadwaj 90 Reputation points Microsoft Employee

2026-11-03T16:01:51.9866667+00:00
From your description, this can happen when old recovery points are already queued in backend cleanup and retention recalculation has not completed for those legacy points.

Reconfirm policy and item mapping.

Verify the protected item is still linked to the expected policy and retention settings in the same vault.

Ref: https://learn.microsoft.com/azure/backup/backup-azure-manage-vms

Trigger one fresh backup and observe lifecycle timestamps.

This helps confirm current policy execution is healthy even if old points are stale.

Validate if stale points are from older protection state.

If points were created under previous policy/protection context, deletion can lag until backend compaction/garbage collection completes.

Collect required evidence for support escalation.

Vault name, protected item ARM ID, recovery point IDs/dates, policy JSON, UTC timestamps of recent successful jobs.

Ref: https://learn.microsoft.com/azure/backup/backup-azure-vms-introduction

Open Azure Support for backend cleanup request.

Ask for recovery point metadata reconciliation/manual backend cleanup for orphaned points beyond retention.

Ref: https://learn.microsoft.com/azure/backup/backup-azure-manage-vms

Note: Avoid stop/reprotect just for cleanup unless support recommends it, because it can affect restore-chain continuity and recovery posture.

“If you find this answer helpful, please upvote it. If this resolves your issue, please mark it as the accepted answer so that it can help others in the community.”
Bharath Y P 10,610 Reputation points Microsoft External Staff Moderator

2026-11-03T16:06:33.92+00:00

Hello Jeremy,

Thank you for posting your query on Microsoft Q&A platform.

We are looking into your issue and will keep you posted updates. Thanks

Your answer

Hemant Bharadwaj 90 Reputation points Microsoft Employee

2026-11-03T16:01:51.9866667+00:00

From your description, this can happen when old recovery points are already queued in backend cleanup and retention recalculation has not completed for those legacy points.

Reconfirm policy and item mapping.

Verify the protected item is still linked to the expected policy and retention settings in the same vault.

Ref: https://learn.microsoft.com/azure/backup/backup-azure-manage-vms

Trigger one fresh backup and observe lifecycle timestamps.

This helps confirm current policy execution is healthy even if old points are stale.

Validate if stale points are from older protection state.

If points were created under previous policy/protection context, deletion can lag until backend compaction/garbage collection completes.

Collect required evidence for support escalation.

Vault name, protected item ARM ID, recovery point IDs/dates, policy JSON, UTC timestamps of recent successful jobs.

Ref: https://learn.microsoft.com/azure/backup/backup-azure-vms-introduction

Open Azure Support for backend cleanup request.

Ask for recovery point metadata reconciliation/manual backend cleanup for orphaned points beyond retention.

Ref: https://learn.microsoft.com/azure/backup/backup-azure-manage-vms

Note: Avoid stop/reprotect just for cleanup unless support recommends it, because it can affect restore-chain continuity and recovery posture.

“If you find this answer helpful, please upvote it. If this resolves your issue, please mark it as the accepted answer so that it can help others in the community.”
Bharath Y P 10,610 Reputation points Microsoft External Staff Moderator

2026-11-03T16:06:33.92+00:00

Hello Jeremy,

Thank you for posting your query on Microsoft Q&A platform.

We are looking into your issue and will keep you posted updates. Thanks