# Azure Backup data retained beyond intended retention period Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/azure-backup-data-retained-beyond-intended-retention-period Backup data persists longer than intended due to misaligned or outdated retention policies. By: Aaran Bhambra Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Azure Backup Data Retained Beyond Intended Retention Period The short version Backup data persists longer than intended due to misaligned or outdated retention policies. [Aaran Bhambra](https://www.linkedin.com/in/aaran-bhambra/) FinOps Engineer / DevOps Engineer @ WTW Azure service [Azure Backup](https://www.pointfive.co/efficiency-hub/cloud-services/azure-backup) Category [Storage](https://www.pointfive.co/efficiency-hub/service-category/storage) Reference CER-0278 Type Excessive Data Retention ## 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. [Manage recovery points](https://learn.microsoft.com/en-us/azure/backup/manage-recovery-points) [Manage Azure VM backups with Azure Backup service](https://learn.microsoft.com/en-us/azure/backup/backup-azure-manage-vms) [Azure Backup pricing](https://azure.microsoft.com/en-us/pricing/details/backup/) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - Azure Backup CER-0286 ### [Retained Azure Backup Data After Resource Decommissioning](https://www.pointfive.co/efficiency-hub/inefficiencies/retained-azure-backup-data-after-resource-decommissioning) A protected resource (such as a virtual machine, database, or file share) is decommissioned without explicitly stopping backup protection. In these cases, Azure Backup keeps applying the retention policy to older recovery points, but the... Storage - Azure Backup CER-0446 ### [Daily Full Backups for SQL Server and SAP HANA Databases in Azure VMs](https://www.pointfive.co/efficiency-hub/inefficiencies/daily-full-backups-for-sql-server-and-sap-hana-databases-in-azure-vms) Azure Backup protects SQL Server and SAP HANA databases running in Azure VMs with streaming workload backups: full, differential (and for HANA, incremental) and log backups written to a Recovery Services vault. When a SQL Server backup... Storage - Azure Blob Storage CER-0268 ### [Excessive Retention of Audit Logs](https://www.pointfive.co/efficiency-hub/inefficiencies/excessive-retention-of-audit-logs) Audit logs are often retained longer than necessary, especially in environments where the logging destination is not carefully selected. Projects that initially route SQL Audit Logs or other high-volume sources to LAW or Azure Storage may... Storage --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.