Azure Backup Pricing UK 2026
Protected instance fees · Vault storage · LRS / GRS / ZRS / RA-GRS · Retention policy impact
Built and verified by an independent Azure engineer. Prices in GBP, UK South, April 2026.
1. Azure Backup pricing at a glance
Azure Backup has two billing dimensions: a protected instance fee charged per workload per month, and backup vault storage charged per GB per month. There is also an optional add-on for Cross-Region Restore, which requires RA-GRS vault storage. Most teams notice the per-instance fee first — it looks modest — and underestimate the storage line, which is usually the dominant cost.
| Workload | Instance fee (USD) | Instance fee (GBP) |
|---|---|---|
| Azure VM | $10.00/month | £7.55/month |
| SQL Server in Azure VM | $31.25/month | £23.59/month |
| Azure Files | $6.25/month | £4.72/month |
| Vault storage type | Rate (USD/GB/month) | Rate (GBP/GB/month) |
|---|---|---|
| Standard LRS | $0.028 | £0.0211 |
| Standard ZRS | $0.035 | £0.0264 |
| Standard GRS | $0.056 | £0.0423 |
| Standard RA-GRS | $0.0711 | £0.0537 |
Source: Azure Retail Prices API (USD-only service), converted at 0.7548 GBP/USD. Verified April 2026.
2. Why storage usually dominates the instance fee
Consider 10 Azure VMs, each with 500 GB of active data and a 30-day retention policy. The instance fees total £75.50/month — just £7.55 per VM. That looks manageable. But the backup vault storage tells a different story. Azure Backup accumulates incremental backup points throughout the retention window. Assuming a 5% daily change rate (typical for general-purpose VMs), each VM accumulates roughly 500 GB × (1 + 0.05 × 30) = 2,250 GB in the vault. Across 10 VMs that's 22,500 GB. At LRS rates: 22,500 GB × £0.0211 = £474.75/month.
Worked example: 10 VMs, 500 GB active data, 30-day retention, LRS
Storage is 86% of the total. Instance fees are the smaller line item.
The storage-to-instance ratio gets worse with longer retention and higher daily change rates (SQL Server at 10% daily change stores proportionally more). This is the headline insight for Azure Backup: plan your budget around the storage cost, not the instance fee.
3. LRS vs GRS vs ZRS vs RA-GRS — when does each make sense?
Vault storage redundancy is the highest-leverage cost control in Azure Backup. GRS doubles the storage cost compared to LRS. RA-GRS costs ~2.5×. Yet GRS is often enabled by default in ARM templates and Terraform modules without explicit intent.
LRS — Locally Redundant Storage
£0.0211/GB/monthDev/test, non-critical workloads, or any backup where regional failure is an acceptable risk. Three copies within a single datacenter.
ZRS — Zone Redundant Storage
£0.0264/GB/monthProduction workloads that need resilience against datacenter failure within a region. 25% more than LRS.
GRS — Geo-Redundant Storage
£0.0423/GB/monthProduction-critical workloads with a documented requirement to survive a regional outage. ~2× LRS cost. Do not use for dev/test.
RA-GRS — Read-Access Geo-Redundant
£0.0537/GB/monthSame as GRS but with read access to the secondary region, enabling Cross-Region Restore. ~2.5× LRS cost. Only justified when CRR is an explicit DR requirement.
4. The Cross-Region Restore surprise
Cross-Region Restore (CRR) allows you to restore backed-up data to the paired Azure region — useful if you need to recover from a full regional outage. CRR requires an RA-GRS vault. The cost has two layers that teams often miss:
- The RA-GRS storage premium (~2.5× LRS) applies to your entire vault, not just the data you intend to restore across regions.
- When you actually perform a cross-region restore, you pay for the data transfer out of the secondary region. This is a one-time charge per restore event and scales with the data size restored.
Most teams enable RA-GRS "because it sounds like the safe option" and then never perform a cross-region restore. The ongoing storage premium is a permanent cost for a capability that may never be exercised.
5. Retention policy and vault storage — the multiplier effect
Azure Backup's pricing model accumulates storage for each retained backup point. The longer you keep backup history, the more vault storage you consume. The formula is straightforward:
| Retention | VM (5%/day) | SQL (10%/day) | Files (2%/day) |
|---|---|---|---|
| 7 days | 1.35× | 1.7× | 1.14× |
| 30 days | 2.5× | 4.0× | 1.6× |
| 90 days | 5.5× | 10× | 2.8× |
| 365 days | 19.25× | 37.5× | 8.3× |
Multiplier = vault storage / active data size. A 12-month retention policy for SQL Server stores ~37× the active data size in the vault.
6. Azure Backup vs Azure Site Recovery — related but not interchangeable
Both services protect data and both have a storage-dominated cost structure. The use cases are different:
Azure Backup
Point-in-time restore of data. Protects against accidental deletion, corruption, ransomware. Recovery takes minutes to hours. Instance fee + vault storage.
Azure Site Recovery
Continuous replication + automated failover. Protects against regional infrastructure failure. Sub-minute RPO, low RTO. Instance fee + replica storage + replication transfer + failover compute.
Site Recovery is more expensive because it provides continuous replication rather than periodic snapshots. For most workloads, the right architecture uses both: Backup for operational recovery (file restores, corruption) and Site Recovery for DR failover (regional outage). Building a DR business case on Backup alone will leave gaps.
7. Soft-delete and the storage tail beyond your retention policy
Soft-delete is enabled by default on Azure Recovery Services vaults since 2021. When backup data is deleted (manually or when a retention policy expires), soft-delete keeps the data for 14 additional days before permanent deletion. This adds a storage cost tail beyond your intended policy. For large vaults with high turnover — environments that frequently onboard and offboard VMs — the soft-delete tail can represent a meaningful fraction of the total vault size. It is worth knowing about when building detailed forecasts, though for most workloads it is a second-order effect.
8. Azure Files backup — the lowest-cost workload type
Azure Files backup has the lowest daily change rate assumption (2% per day) and the lowest instance fee (£4.72/month). For file share workloads that are largely static — document libraries, configuration stores, data exports — the vault storage stays manageable even with longer retention. A 10 TB Azure Files share with 90-day retention accumulates roughly 28 TB in the vault at LRS rates (£591/month total), compared to a similar SQL database which would accumulate ~100 TB. If you have a choice about where to store data that needs long-term backup, Azure Files is the cheaper backup substrate.
FAQ
Is Azure Backup pricing available in GBP from the Azure Retail Prices API?
No. Azure Backup is USD-only in the Retail Prices API (currencyCode returns USD regardless of region). GBP estimates use a 0.7548 conversion rate (verified April 2026). Check the official pricing page to confirm current GBP rates.
Does Azure Backup charge per GB of active data, or per GB of vault storage?
Per GB of vault storage. Vault storage is larger than active data because it accumulates all retained backup points. A 100 GB volume with 30-day retention and 5% daily change rate occupies roughly 250 GB of vault, not 100 GB.
What is the cheapest way to run Azure Backup for dev/test VMs?
Use LRS vault storage, set retention to the minimum needed (7 days is the minimum), and consider whether full VM backup is needed or whether application-level backup (e.g. database export) is sufficient. LRS + 7-day retention keeps vault storage close to active data size.
Can I use Azure Backup instead of Azure Site Recovery for disaster recovery?
They serve different purposes. Backup provides point-in-time restore — suitable for accidental deletion or corruption recovery. Site Recovery provides continuous replication for near-zero-RPO failover. Using Backup as a DR strategy means accepting hours of data loss (the gap since the last backup) and manual recovery steps.
Are there size tiers in Azure Backup instance fees?
No — as of April 2026, the Retail Prices API shows flat per-instance fees regardless of VM size. Earlier Azure documentation referenced size tiers, but current pricing is flat. Verify on the official pricing page for any changes.
Related calculators and guides
backupAzure Backup Calculator
Estimate your backup costs with instance breakdown and storage dominance indicator
Azure Site Recovery Calculator
Continuous replication for DR — same storage-dominates cost shape as Backup
Azure Site Recovery Pricing UK
The full DR cost picture — why the per-instance fee is only part of the bill
Managed Disks Calculator
Estimate the disk storage your VMs are running on — plan backup costs alongside disk costs