
That makes budgeting tricky. The total depends on protected data, change rate, retention, redundancy, recovery needs, and region, not just VM size or whether the VM is running.
This guide covers current US pricing components, cost drivers, illustrative scenarios, commonly missed charges, and a practical way to estimate your budget.
Key Takeaways
- Azure VM Backup combines a protected-instance fee with recurring storage charges for recovery points.
- Retention, churn, redundancy, snapshot settings, and VM count move the bill most.
- Small, low-change, short-retention workloads cost least; large, high-churn, geo-redundant setups cost most.
- The cheapest setup isn't always right. Weigh savings against recovery speed and compliance.
How Much Does Azure VM Backup Cost? (Pricing Overview)
There's no universal price range. Microsoft bills components separately, and final prices vary by region, redundancy, agreement, and retention. The figures below use East US list prices in USD from Microsoft's pricing page, captured in a late-2026 snapshot. Your agreement may differ.
Protected-instance charges
The fee depends on used data per VM, not compute size or provisioned disk capacity.
| Protected used data per VM | Monthly fee (storage excluded) |
|---|---|
| Up to 50 GB | $5 |
| Over 50 GB, up to 500 GB | $10 |
| Over 500 GB | $10 per 500 GB increment |
Charges are prorated by protected days. A stopped-protection VM with retained data keeps billing based on its last successful backup size.
Backup storage charges
Recovery points consume vault storage priced by tier and redundancy (East US, per GB-month):
| Tier | Redundancy | Price |
|---|---|---|
| Standard | LRS | $0.0224 |
| Standard | ZRS | $0.028 |
| Standard | GRS | $0.0448 |
| Standard | RA-GRS | $0.0569 |
| Archive | LRS | $0.0013 |
| Archive | GRS | $0.004 |
Archive retrieval carries a one-time fee. Check the current rate on Microsoft's pricing page before budgeting for it.
Illustrative pricing scenarios
These are simplified estimates, not universal prices. They exclude snapshots, monitoring, restored resources, and discounts. Stored-data figures are assumptions.
Small or dev environment: 3 VMs at 40 GB used each, LRS, about 150 GB stored.
- Instance: 3 × $5 = $15
- Storage: 150 × $0.0224 = $3.36
- Total: roughly $18/month
Standard production: 20 VMs at 200 GB used each, GRS, about 6 TB stored with moderate retention.
- Instance: 20 × $10 = $200
- Storage: 6,000 × $0.0448 = $268.80
- Total: roughly $469/month, plus snapshots and monitoring
Large or high-retention: 10 VMs at 2 TB used each, RA-GRS, about 60 TB stored given high churn and long retention.
- Instance: 10 × $40 = $400
- Storage: 60,000 × $0.0569 = $3,414
- Total: roughly $3,814/month

Here storage dominates. Archive can cut unit cost for eligible monthly or yearly points, but early deletion within 180 days triggers a prorated charge, and retrieval adds a fee.
What Drives Azure VM Backup Costs?
The headline per-VM fee is the smaller part of most bills. These factors shape the rest.
Protected data size versus provisioned disk capacity
Microsoft measures actual used data before compression and encryption, excluding temporary storage. A 1 TB disk holding 80 GB is billed on roughly 80 GB. Don't estimate from maximum disk size.
Data change rate and backup method
The first backup is a full copy. After that, only changed blocks are stored. Higher daily churn means more retained blocks. Expired points are cleaned up regularly, but Microsoft's recovery-point guidance notes that storage reduction can be gradual, not proportional to expired points.
Backup policy and retention
Maximums are generous: 9,999 daily, 5,163 weekly, 1,188 monthly, and 99 yearly. Those are limits, not recommendations. Match retention to recovery objectives rather than applying a long default to every workload.
Storage redundancy and Azure region
Moving from LRS to RA-GRS raises Standard storage from $0.0224 to $0.0569 per GB-month, about 2.5 times. Enabling Cross Region Restore upgrades GRS storage to RA-GRS billing. Rates also vary by region, so pull prices for your deployment region.
Snapshot backup and instant-recovery settings
Instant Restore keeps managed-disk snapshots in a restore point collection for faster recovery. Snapshot used space is billed in addition to vault storage.
- Standard policy: 1-5 days of snapshot retention, default 2
- Enhanced policy: 1-30 days, default 7
Selective-disk billing differs by policy. Under Standard with OS-only protection, snapshots still cover all VM disks. Under Enhanced, included disks count toward all three billing bases.
Additional and adjacent charges
- Soft delete is free for 14 days; longer configured retention (up to 180 days) is billed at regular rates
- Backup Reports use Azure Monitor logs, with ingestion and extended retention charged
- Restored VMs and disks incur normal compute and disk charges, and staging VHDs can add cost
- Archive retrieval and early deletion carry fees
- Standard-tier restore operations and egress are free

Azure Site Recovery is a separately priced disaster-recovery service, not ordinary backup.
Low-Cost vs High-Cost Azure VM Backup: What's the Difference?
The gap comes from policy choices, not a basic-versus-premium tier.
Lower-cost configuration
Suited to rebuildable dev systems and low-criticality workloads:
- Short retention and brief snapshot windows
- Selective disk backup (with the policy billing caveats above)
- LRS storage
Trade-off: no protection from a regional outage, and fewer restore points to roll back to.
Higher-cost configuration
Suited to production and compliance-driven workloads:
- Long retention and higher churn
- GRS or RA-GRS with Cross Region Restore
- Enhanced policy with longer-lived snapshots
Without CRR, restoring from the secondary region requires Azure to declare a disaster. With CRR you can restore on demand, though worst-case secondary RPO can reach 36 hours.
Compare on recovery outcomes, not price alone
Test both options against:
- Recovery point and recovery time objectives
- Regional outage protection
- Compliance retention
- Restore speed and admin effort
Don't cut coverage just to hit a number. A cheap backup that can't meet your RTO costs more when you need it.
How to Estimate the Right Azure VM Backup Budget
Base the budget on workload risk and recovery requirements, not the lowest per-VM price.
Inputs to collect before estimating
- VM count and used data per VM
- Included disks and daily change rate
- Backup frequency and retention schedule
- Redundancy, region, and snapshot duration
- Archive eligibility and expected restores
- Your Azure agreement or discounts
Use a transparent cost formula
Monthly cost = Instance fees + Vault storage + Snapshot storage + Archive charges + Monitoring + Restore resources
- Instance fees: VM count × band rate
- Vault storage: retained GB × redundancy rate
- Snapshot storage: snapshot GB × managed-disk snapshot rate
- Archive: stored GB, retrieval, early deletion
- Monitoring: log ingestion and retention beyond included periods
- Restore resources: compute and disks from test or real restores
Populate rates with Microsoft's pricing calculator or the Retail Prices API. Signed-in calculator estimates can reflect negotiated prices.
Build a worked estimate
Single VM: 300 GB used, LRS, about 450 GB stored. Instance $10 plus storage $10.08 is about $20/month. Switching to GRS raises storage to $20.16, for about $30.
Fleet: 20 VMs at 200 GB used. With about 6 TB stored on LRS, storage is $134.40 plus $200 instance, about $334.
On RA-GRS the same data costs $341.40 in storage, about $541. Doubling retained data through longer retention on RA-GRS pushes storage to about $682.80.

Change one variable at a time to see what moves the bill.
Validate the estimate against actual billing
Compare your forecast with Azure Cost Management line items once recovery points have accumulated through a full retention cycle. Early invoices understate mature storage costs.
Granular billing adds vault-level, protected-item, and tag-based attribution. Budget alerts flag overruns.
What most people miss when controlling costs
- Stopped or deleted VMs with retained recovery data still bill
- Orphaned backup items; Backup Reports flags items with no recovery point in 7 days
- Duplicate VM-level and in-guest workload protection
- Unnecessary disks and long default retention
- Restore targets that create normal compute and disk charges
Good habits include:
- Azure Policy for enablement and auditing
- Periodic backup audits
- Selective disk protection
- Retention reviews and restore testing
- Cost alerts
Lucidity Lumen can help on the adjacent storage side. It supports Azure and identifies four idle disk types (unattached, reserved, unmounted, and zero-I/O) that can represent up to 70% of unused block storage spend. It doesn't replace Azure Backup or remove Recovery Services vault charges.
Conclusion
Azure VM Backup costs come from protected data, recovery-point storage, retention, redundancy, snapshots, and related services, not a single VM price.
Keep spend aligned with recovery needs:
- Model current US regional pricing against your recovery objectives
- Validate estimates against actual billing
- Trim storage and policies without weakening required protection
Frequently Asked Questions
How much does Azure Backup cost?
It depends on protected instances, stored recovery points, redundancy, retention, region, and extra services. In East US, instance fees start at $5/month per VM; check Microsoft's current pricing for your region.
Do stopped Azure VMs still cost money?
Stopping a VM ends compute charges, but backup charges continue while protection or recovery data remains. Billing ends only after you delete the retained data and it passes any soft-delete period.
How are Azure VMs backed up?
Backups go to a Recovery Services vault under a policy. The first is a full copy, then incremental changed blocks form recovery points. Running Windows VMs use VSS for application consistency.
What is snapshot backup and how does it work?
Snapshots are point-in-time disk copies kept locally for fast restores, alongside vault backups. Their used space is billed separately from vault storage.
Is Azure Backup free?
No. Expect instance and storage charges, plus snapshot, monitoring, and restore costs. Include Backup fees in your estimates and check Microsoft's pricing page for any current trial offers.
How can I reduce my Azure VM backup costs?
Right-size retention, protect only needed disks, pick redundancy deliberately, and use Archive for eligible long-term points. Remove orphaned backups, review snapshots, and audit Cost Management regularly.