# Retained Azure Backup data after resource decommissioning Canonical: 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. By: Aaran Bhambra Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Retained Azure Backup Data After Resource Decommissioning The short version A protected resource (such as a virtual machine, database, or file share) is decommissioned without explicitly stopping backup protection. [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-0286 Type Excessive Data Retention ## 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. [https://learn.microsoft.com/en-us/azure/backup/backup-overview](https://learn.microsoft.com/en-us/azure/backup/backup-overview) [https://learn.microsoft.com/en-us/azure/backup/backup-azure-delete-vault](https://learn.microsoft.com/en-us/azure/backup/backup-azure-delete-vault) [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-0278 ### [Azure Backup Data Retained Beyond Intended Retention Period](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. It often arises when retention requirements change over time, but older recovery points are not evaluated or cleaned up accordingly. In some cases,... 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.