Explanation
Why the waste happens and who it affects.
In these cases, Azure Backup keeps applying the retention policy to older recovery points, but the most recent recovery point is retained indefinitely until protection is explicitly stopped with data deletion. Although the source resource no longer exists, backup storage remains allocated and billable with no end date, resulting in unnecessary ongoing costs.
This pattern is common when infrastructure is deleted outside of a formal decommissioning process or when backup ownership is unclear.
Billing model
The pricing dimensions that drive this cost.
Azure Backup charges a protected instance fee for each protected item plus backup storage consumed in the Recovery Services Vault, regardless of whether the original protected resource still exists. If a resource is deleted without stopping protection, its backup item remains active, so both charges continue, and storage charges continue until the backup data is deleted.
How to detect
3 checks to find it in your estate.
- Review backup vaults for protected items that no longer have an associated active resource
- Identify recovery points tied to workloads that have been deleted or decommissioned
- Assess whether retained backups still serve a valid recovery, audit, or compliance purpose
How to fix
3 ways to remove the waste.
- Confirm whether retained backups are still required for recovery or compliance
- Stop backup protection and delete backup data for decommissioned resources when no longer needed
- Incorporate backup cleanup into standard resource decommissioning workflows
Documentation
Vendor references for pricing and configuration.