Explanation
Why the waste happens and who it affects.
It often arises when retention requirements change over time, but older recovery points are not evaluated or cleaned up accordingly. In some cases, manually configured backups or legacy policies remain in place even after operational or compliance needs have been reduced.
As a result, backup storage continues to grow and incur cost without delivering additional recovery value.
Billing model
The pricing dimensions that drive this cost.
Azure Backup charges a protected instance fee for each protected item, based on the size of the protected data, plus backup storage (LRS, ZRS, or GRS in the Standard tier, or the Archive tier) for retained recovery points. Shortening retention reduces only the storage portion. Data retained beyond operational or compliance needs continues to generate storage charges.
How to detect
3 checks to find it in your estate.
- Review backup vaults for recovery points that exceed current retention requirements
- Identify backups governed by legacy or manually configured policies
- Compare actual retained backup age against documented retention standards
How to fix
3 ways to remove the waste.
- Revalidate required retention periods with stakeholders and compliance owners
- Align backup policies with current retention needs
- Shorten retention in the backup policy to reduce unnecessary backup storage costs (the change applies to existing recovery points, and expired ones are cleaned up automatically). Individual recovery points cannot be deleted selectively, so for items that are no longer needed, stop protection and delete backup data. Expect storage to decline gradually, because expired incremental recovery points are merged into later ones rather than removed outright
Documentation
Vendor references for pricing and configuration.