Last updated: June 2026
To cut Azure Backup and Site Recovery costs, tune retention and backup frequency to the real compliance requirement, choose locally redundant storage over geo-redundant for non-critical data, move long-term recovery points to the archive tier, and stop protection on decommissioned machines. The largest single saving is usually clearing retention and orphaned protected items that bill every month for data no one will ever restore.
- Azure Backup bills per protected instance by source data size, plus separate backup storage.
- Site Recovery bills a per-instance license from day 32, plus replication storage and egress.
- Retention length and backup frequency drive most of the storage bill.
- Archive tier and LRS cut the storage cost of cold and non-critical data.
Azure Backup is a managed backup service that stores recovery points in a Recovery Services vault, and Azure Site Recovery is a disaster recovery service that replicates machines to a secondary region for failover. Cutting their cost means matching retention, frequency, redundancy, and protection scope to the real recovery requirement, rather than defaulting every workload to maximum protection. This article is part of our Azure cluster; the pillar it links up to is the complete guide to Azure cost optimization. Trimming retention and clearing orphans are Cut steps in our See, Cut, Lock, Run method.
How is Azure Backup priced?
Azure Backup bills monthly per protected instance, where the protected instance charge is based on the size of the source data being backed up before compression and encryption, plus a separate charge for the backup storage the recovery points consume. As of June 2026, per the Azure Backup pricing documentation, a protected instance is each virtual machine, database, or workload you protect, and the storage portion scales with how many recovery points you retain and at what redundancy. Because retention length and backup frequency directly determine the storage bill, they are the main levers. Verify the current figures on the linked Azure page before acting, because backup pricing changes.
| Cost component | What drives it | Main lever |
|---|---|---|
| Protected instance fee | Source data size, count of protected items | Clear orphaned and decommissioned items |
| Backup storage | Retention length, backup frequency, redundancy | Trim retention, archive cold points, use LRS |
| Site Recovery license | Average daily protected instances from day 32 | Remove out-of-scope replications |
| Replication storage and egress | Replicated data volume and cross-region transfer | Scope DR to critical workloads only |
How is Azure Site Recovery priced?
Azure Site Recovery bills a per-instance license based on the average daily number of instances you protect over the month, where each instance is a virtual machine or physical server. Per the Azure Site Recovery pricing page, every protected instance is free for the first 31 days and charged from the 32nd day onward, and on top of the license you pay for the replication storage, storage transactions, and outbound data transfer the replication consumes. The practical implication is that disaster recovery is not free to leave running on workloads that no longer need it: a stale replication keeps billing its license and its storage. Scope Site Recovery to the workloads whose recovery time objective genuinely requires cross-region failover, and remove protection from everything else.
How do you cut Azure data protection costs, step by step?
These five steps trim retention, match redundancy to need, and clear protection you no longer use.
- Tune retention to the actual policy requirementReduce daily, weekly, monthly, and yearly retention to what compliance and recovery objectives truly require. The result is fewer recovery points billing storage every month.
- Right-size backup frequencyLower frequency on workloads that do not need multiple daily points and keep hourly or enhanced policies only where the recovery point objective demands them. The result is less stored data for the same protection level.
- Choose the cheapest redundancy that meets the requirementUse locally redundant storage for non-critical backups and reserve geo-redundant or zone-redundant storage for data that needs cross-region durability. The result is the GRS premium avoided where it adds no value.
- Move long-term retention to the archive tierEnable the archive tier for monthly and yearly points that are rarely restored. The result is cold, long-lived data stored at a fraction of standard backup cost.
- Clear orphaned protected items and stale replicationsStop protection and delete backup data for decommissioned machines and remove Site Recovery for VMs no longer in scope. The result is the silent per-instance license waste eliminated.
Paying to protect machines that no longer exist?
Our Azure cost audit tunes retention and frequency to your real policy, matches redundancy to each workload, archives cold recovery points, and clears orphaned protected items and stale replications. On the performance model you pay only from realized savings. No savings, no fee.
Book an Azure cost audit →Should I use LRS or GRS for Azure Backup?
Use locally redundant storage for backups that do not require cross-region durability and geo-redundant storage only for data that must survive a regional outage, because GRS costs significantly more than LRS. The common mistake is setting the entire Recovery Services vault to GRS and paying the cross-region premium on development, test, and easily rebuilt data that would be perfectly safe on LRS. Match the redundancy to the recovery requirement of each workload, the same discipline of paying only for the tier you need that applies to your image storage, covered in our guide to reducing Azure Container Registry and ACR costs.
Billing units, the 31-day Site Recovery free period, and tier behavior reflect Azure as of June 2026. Verify current pricing on the linked Azure documentation before acting, because data protection packaging and rates change.
The Azure Cost Optimization Field Guide includes the retention tuning worksheet and the backup redundancy checklist we apply on engagements. It is the downloadable companion to this article.
Frequently asked questions
How is Azure Backup priced?
Azure Backup bills monthly per protected instance, where the protected instance charge is based on the size of the source data being backed up before compression and encryption, plus a separate charge for the backup storage the recovery points consume. A protected instance is each virtual machine, database, or workload you protect. Retention length and backup frequency drive the storage portion, so tuning them is the main cost lever. Verify current rates on the Azure Backup pricing page.
How is Azure Site Recovery priced?
Azure Site Recovery bills a per-instance license based on the average daily number of instances you protect over the month, where each instance is a virtual machine or physical server. Every protected instance is free for the first 31 days and charged from the 32nd day onward, and you also pay for the replication storage, storage transactions, and outbound data transfer the replication consumes. Removing protection from machines no longer in scope is the main saving.
How do I reduce Azure Backup storage cost?
Reduce backup storage cost by shortening retention to the real compliance requirement, lowering backup frequency where multiple daily points are not needed, moving long-term monthly and yearly points to the archive tier, and using locally redundant storage instead of geo-redundant storage for non-critical data. Each retained recovery point and each redundancy upgrade adds storage that bills every month, so trimming both is where the saving comes from.
Should I use LRS or GRS for Azure Backup?
Use locally redundant storage for backups that do not require cross-region durability and geo-redundant storage only for data that must survive a regional outage, because GRS costs significantly more than LRS. Many estates default the entire backup vault to GRS and pay the cross-region premium on data that would be perfectly safe on LRS. Match the redundancy to the recovery requirement of each workload rather than applying one setting to everything.
The short version
Azure data protection savings come from tuning retention and frequency to real policy, choosing LRS over GRS where cross-region durability is not required, archiving cold recovery points, and clearing protection on machines that no longer exist. When you want your backup and disaster recovery estate matched to actual recovery requirements and the orphaned items cleared, that is exactly what our Azure cost optimization service delivers.
Cloud pricing and service behavior change frequently. Verify the specifics in this guide against the providers’ own current documentation and the FinOps Foundation: Azure pricing ↗, Azure documentation ↗ and FinOps Foundation Framework ↗. This article also reflects Cloud Cost Room’s hands-on, vendor-neutral engagement experience.