Azure Backup cost looks fixed at $5 per protected instance per month, which is why the first invoice at three or four times that number catches teams off guard. That flat fee is the only number the pricing page makes obvious.
Everything that actually moves the bill sits one layer down, and most of it is a charge you can bring back under control once you can see it.
Azure Backup cost at a glance
Rates shown are US-region list prices and vary by region.
Azure Backup cost breakdown
Every Azure Backup bill comes down to two questions. How many resources are you protecting, and how much backup data are you storing, where, and for how long?
Protected instance fees
Azure counts each backed-up resource as a protected instance and charges a monthly fee based on its source data size before compression. A VM under 50 GB costs $5 per month, one between 50 GB and 500 GB costs $10, and anything larger adds $10 for each additional 500 GB increment. A 1.2 TB VM lands at $30 in instance fees alone.
The fee is predictable, but Azure charges it on the pre-compression size and keeps billing until you actively stop protection. A decommissioned VM that nobody removed from its backup policy stays on the invoice.
Backup storage and redundancy tiers
Storage is billed per GB per month, and the redundancy you pick sets the rate. Locally redundant storage (LRS) keeps three copies in one region. Geo-redundant storage (GRS) replicates to a paired region and costs roughly double.
Long-term data can move to the Archive tier at $0.0027 per GB for LRS, a large drop from Standard. Two constraints apply. Redundancy is set at the vault level and can't be changed once you start protecting items, so getting it wrong means building a new vault later. Archive also carries a 180-day early-deletion charge, prorated if you remove data sooner.
Azure Backup cost by workload
Pricing shifts by the type of resource you protect. Databases and SAP HANA carry higher instance fees, while Disks and operational Blob backup skip the instance fee entirely.
To see how the bill adds up, take a small Azure environment: a team protects four production VMs at roughly 500 GB each, backed up daily into a GRS vault, with the retained backup footprint settling around 3 TB after compression and retention.
- Protected instances: four VMs in the 50 to 500 GB tier at $10 each is $40 per month.
- Storage: 3 TB (3,072 GB) at the GRS Standard rate of $0.0448 is about $138 per month.
- Monthly total: roughly $178, before instant-restore snapshots or cross-region restore.
Switch that same vault to LRS and storage falls to about $69, which brings the bill to roughly $109. The instance fee holds at $40 across both, so storage is what swings the total. Actual footprint depends on your change rate and retention length.
Standard vs Enhanced policy costs
The backup policy you assign sets two things that feed the snapshot bill, how often backups run and how long instant-restore snapshots stay on disk.
- Standard policy runs daily backups and keeps those snapshots for 2 days by default, adjustable up to 5.
- Enhanced policy runs backups as often as every 4 hours and holds snapshots for 7 days by default, up to 30.
More frequent snapshots held for longer means more snapshot data sitting on managed disks, which is why Microsoft flags that Enhanced protection incurs higher snapshot cost.
Those instant-restore snapshots bill as disk snapshots, separate from vault storage, so an Enhanced policy on a high-churn VM raises the snapshot line on its own. Match the policy to the recovery point objective each workload needs, and reserve Enhanced for the ones that require sub-daily recovery points.
Choosing the right redundancy and tier
Redundancy and tier drive cost more than the workload does, so set each one to the recovery requirement it actually needs.
Choose LRS if the data is dev, test, or reproducible and a single-region copy meets your recovery objective. It is the cheapest storage option and halves the GRS rate.
Choose GRS or RA-GRS if you need to recover in a second region after a regional outage. RA-GRS also unlocks cross-region restore, so reserve it for workloads that genuinely require it.
Choose the Archive tier if you retain data for compliance well beyond six months and rarely read it back.
Choose operational Blob backup for local accidental-deletion protection with no instance fee. Choose vaulted Blob backup when you need isolation against ransomware or malicious deletion; that isolation adds instance and transaction charges.
When Azure Backup is worth it
Azure Backup is worth it if you run a smaller, Azure-only environment and want native protection that lives inside each subscription with no extra tooling. For a single 200 GB VM on LRS, the all-in cost sits in the low tens of dollars per month, which is hard to beat for basic coverage.
Reconsider it once your environment spans multiple subscriptions, regions, or clouds, where the charges above (GRS doubling, instant-restore snapshots on disk, RA-GRS for cross-region restore, Archive early deletion, and orphaned instances) concentrate and compound.
Azure also groups backup charges under the Recovery Services vault, so a 5,000-line invoice rarely maps back to a single VM or team.
That last gap is the one Eon's Cost Explorer removes. It attributes backup spend down to the individual resource, so the oversized VM behind a spike appears on its own line, priced and named.
How to reduce Azure Backup costs
Most Azure Backup savings come from three levers: storage redundancy, retention length, and how much duplicate data you store.
Right-size storage redundancy
Set redundancy per workload instead of applying GRS everywhere. Keep reproducible dev and test data on LRS and reserve GRS for production that genuinely needs cross-region recovery. Because redundancy locks at the vault level, plan this before the first backup runs.
Tier long-term retention to the Archive tier
Compliance data you keep for years but rarely read belongs in Archive, the cheapest tier by a wide margin. Confirm each dataset will sit past the 180-day minimum first, or the early-deletion charge cancels the win.
Trim retention and remove orphaned instances
Audit protected instances on a regular cadence and stop protection on VMs, databases, and dev environments that no longer exist. Retention drift, where a resource keeps backups far longer than policy requires, is one of the most common sources of waste.
Commit to reserved capacity at scale
If you consistently store 100 TB or more of backup data, reserved capacity trades a one-year or three-year commitment for a lower per-GB rate. It rewards predictable volume and penalizes environments whose data shrinks, so size the commitment conservatively.
Deduplicate across the environment, not per instance
Azure Backup compresses within a workload, but stores each protected instance separately with no credit for data shared across VMs, databases, or accounts. Cloud-native deduplication stores one copy of repeated blocks across the whole environment instead.
Eon's forever-incremental model uses this to cut backup storage by around 30–50% versus native tools. That is the model Sigdo Koppers ran the numbers on during its Google Cloud migration, projecting backup costs around 38% below native GCP snapshots.
Azure Backup vs. the alternatives: Cost comparison
Native Azure Backup is one option among several, and the right choice depends on how many clouds you run and how you recover.
Eon vs Azure Backup
Across multiple subscriptions, regions, or clouds, three native limits start to cost real money. Coverage depends on someone manually adding each new resource, storage carries no cross-resource deduplication, and recovering one record means restoring the whole instance around it.
Each of those limits has a direct fix on Eon. Coverage stops waiting on a person once Cloud Backup Posture Management (CBPM) discovers and protects new resources the moment they appear. The cross-resource storage penalty drops out because deduplication runs across the whole environment, and restoring one record stops requiring the instance around it, since recovery reaches down to a single file, object, table, or row.
Those backups land in open formats, Parquet, Iceberg, and Delta Lake, ready for zero-ETL ingestion into Snowflake, Databricks, BigQuery, or Athena. An audit or analytics request runs against the backup copy directly, with no separate copy of the data to stand up or pay for.
The trigger to switch is usually the invoice itself, or a recovery that ran too slow when it counted. Eon keeps backups logically air-gapped and immutable, and restores exactly what was hit.
That isolation model is what ransomware recovery demands, and the proof arrived quickly for SoFi, which cut recovery from a day to minutes across five regions and reported over 100% ROI in year one.
For smaller Azure-only setups, native Azure Backup still holds its ground.
The bottom line
Azure Backup costs are easy to underestimate, since the $5 instance fee hides a storage bill driven by redundancy, retention, and duplicate data.
Matching redundancy and retention to each workload, then deduplicating globally, keeps the bill under control. Accept the defaults instead, and you pay for coverage you can't see and data you don't need.
Where is your Azure Backup spend actually going, by subscription, workload, and team? If that question is hard to answer from your invoice, book a demo and see how Eon shows cost, coverage, and recovery in one view.
Frequently asked questions
How much does Azure Backup cost per month?
Azure Backup costs $5 to $10 per month for a protected VM instance plus separate storage charges based on redundancy and retention. A single 200 GB VM on LRS runs in the low tens of dollars per month, while larger environments scale with instance count, storage volume, and whether you use GRS.
Are restores and egress charged in Azure Backup?
No, Azure Backup does not charge for restore operations or the outbound bandwidth associated with restores. The transfer-related costs that do apply are RA-GRS storage for cross-region restore and a retrieval fee when rehydrating data from the Archive tier.
Why is my Azure Backup bill higher than expected?
High Azure Backup bills usually come from GRS storage on data that only needs LRS, forgotten protected instances still billing for deleted resources, instant-restore snapshots held on disk, and long retention windows. Storage almost always outweighs the per-instance fee.
Is LRS or GRS cheaper for Azure Backup?
LRS is cheaper than GRS for Azure Backup, at $0.0224 versus $0.0448 per GB per month, roughly half the cost. GRS is worth the premium only for workloads that need to recover in a second region after a regional outage.
Does Azure Backup deduplicate across VMs?
No, Azure Backup compresses data within each workload but does not deduplicate across separate VMs, databases, or accounts. Platforms with cloud-native deduplication store one copy of repeated data across the whole environment, which is where much of the 30–50% storage savings over native tools comes from.
How can I reduce Azure Backup costs?
You reduce Azure Backup costs by matching redundancy to each workload, moving long-term data to the Archive tier, trimming retention, removing orphaned protected instances, and deduplicating across the environment. Reserved capacity adds further savings once you consistently store 100 TB or more.
