{"id":12506,"date":"2026-10-16T13:33:51","date_gmt":"2026-10-16T18:03:51","guid":{"rendered":"https:\/\/www.apps4rent.com\/blog\/?p=12506"},"modified":"2026-10-16T13:35:11","modified_gmt":"2026-10-16T18:05:11","slug":"azure-backup-pricing-explained","status":"publish","type":"post","link":"https:\/\/www.apps4rent.com\/blog\/azure-backup-pricing-explained\/","title":{"rendered":"Azure Backup Pricing Explained: What You Will Actually Pay"},"content":{"rendered":"

Azure Backup looks simple from the outside. You enable it on a VM, pick a policy, and recovery points start appearing. The invoice is where it stops being simple. The first bill often carries line items nobody planned for: a fee for every protected item, storage that grows with each recovery point, snapshots billed on a different meter, and backups still billing for machines that were deleted months ago.<\/p>\n

None of it is hidden, exactly. It is spread across Microsoft’s pricing page, a handful of documentation articles, and a calculator that asks questions most teams cannot answer on day one. This guide pulls it into one place: how the two core meters work, what each workload costs, where the extras come from, worked examples with the arithmetic shown, and eight ways to lower the bill without weakening your recovery position. If you are new to the service, our overview of what Azure Backup protects and why it is worth using<\/a> covers the basics before we get to the money.<\/p>\n

\n

Short answer<\/p>\n

Azure Backup bills two things: a monthly protected instance fee for every item you back up (for a VM, $10 per 500 GB of data, and half that up to 50 GB) and the backup storage those recovery points use (from $0.0224 per GB per month on LRS to $0.0448 on GRS). Everything else on the bill, such as snapshots, extended soft delete and restored resources, follows from choices you make around those two meters. Prices in this guide are East US list prices checked in October 2026.<\/p>\n<\/div>\n

How Azure Backup Pricing Works<\/h2>\n

Azure Backup bills on two meters, and almost every question about the invoice comes back to one of them.<\/p>\n

The protected instance fee<\/strong> is a monthly charge for each item you back up: a VM, a SQL Server database server, an Azure file share account, an on-premises server. It is sized by the amount of data on the source, measured before compression and encryption. For a VM it reflects the data actually stored on the disks, not the provisioned size of each disk, so a 128 GB disk holding 30 GB of data is priced as 30 GB.<\/p>\n

Backup storage<\/strong> is a monthly per-GB charge for the recovery points held in the vault. It depends on how much data changes each day, how long you retain recovery points, which redundancy option the vault uses, and whether a recovery point sits in the Standard or Archive tier.<\/p>\n

Three details shape both meters. First, each needs its own tuning: shortening retention lowers the storage line but never the instance fee, and shrinking a VM lowers the instance fee but not what already sits in the vault. Second, the instance fee keeps billing for as long as backup data exists for that item. Third, restoring from the Standard tier carries no transaction or egress charge, according to Microsoft’s pricing page. What you pay for is whatever you restore into.<\/p>\n

\"Diagram<\/p>\n

Two meters drive the bill. A third group of costs sits on other meters and is easy to miss.<\/p>\n<\/div>\n

Protected Instance Fees by Workload<\/h2>\n

The instance fee differs by workload because the work Azure does differs. A plain VM sits at the low end, database workloads cost more, and some newer workloads have their own meters. For VMs the rule is simple: half the unit price up to 50 GB, one unit for 50 to 500 GB, and one additional unit for each further 500 GB. A VM holding 1.2 TB of data is therefore three units.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Workload<\/strong><\/th>\nList instance fee (per month)<\/strong><\/th>\nWhat to know<\/strong><\/th>\n<\/tr>\n<\/thead>\n
Azure VM<\/strong><\/td>\n$10 per 500 GB, half that up to 50 GB<\/td>\nSized on the data actually stored, before compression. Each extra 500 GB adds one more unit.<\/td>\n<\/tr>\n
SQL Server in an Azure VM<\/strong><\/td>\n$25 (base size band)<\/td>\nWorkload-aware database backup, billed separately from the VM’s own backup.<\/td>\n<\/tr>\n
SAP HANA in an Azure VM<\/strong><\/td>\n$80<\/td>\nFlat per instance, plus storage.<\/td>\n<\/tr>\n
On-premises server (MARS or MABS)<\/strong><\/td>\n$10<\/td>\nSame per-instance model, for servers backed up from your own site.<\/td>\n<\/tr>\n
Azure Files, snapshot tier<\/strong><\/td>\n$5, and 60% of that up to 250 GB<\/td>\nSnapshot storage is billed with your Azure Files usage.<\/td>\n<\/tr>\n
Azure Files, vaulted<\/strong><\/td>\n$10<\/td>\nPlus vaulted storage. A storage account with both kinds of shares carries two fees.<\/td>\n<\/tr>\n
Azure Blobs, operational<\/strong><\/td>\nNone<\/td>\nRelies on soft delete, versioning and point-in-time restore, which bill as Blob features.<\/td>\n<\/tr>\n
Azure Blobs, vaulted<\/strong><\/td>\n$10 base unit<\/td>\nScaled down for small accounts (10%, 30% and 60% bands under 1 TB), plus write transactions.<\/td>\n<\/tr>\n
Managed disks<\/strong><\/td>\nNone<\/td>\nIncremental snapshots bill as snapshot storage in your subscription.<\/td>\n<\/tr>\n
PostgreSQL, AKS, Cosmos DB<\/strong><\/td>\n$7.50, $12, $25<\/td>\nNewer workloads, each on its own meter.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

East US list prices in USD, taken from Microsoft’s Retail Prices API in October 2026. Your region, agreement or CSP pricing will differ.<\/p>\n

Two things in the table are worth a second look. The SQL Server fee is two and a half times the VM fee for the same machine, which matters if you protect both the database and the VM (more on that below). And “none” in the instance column does not mean free: operational Blob backup and managed disk backup still bill for the snapshots and storage features they depend on.<\/p>\n

Backup Storage Costs: Redundancy, Tiers, and What Makes Storage Grow<\/h2>\n

Storage is the meter that moves most as an environment matures, because it compounds: every retained recovery point adds to it. Three choices set its size and price.<\/p>\n

Redundancy: LRS, ZRS, GRS and RA-GRS<\/h3>\n

New Recovery Services vaults default to geo-redundant storage. That default is a sound one for production data, since Microsoft recommends GRS for mission-critical workloads that must survive a regional disaster. It is also the most expensive Standard option short of RA-GRS: GRS lists at exactly twice the per-GB price of LRS. Microsoft’s guidance is to set redundancy before you protect your first workload, because it cannot be changed once items are protected, so this decision belongs at vault creation, not at the first invoice.<\/p>\n\n\n\n\n\n\n\n\n\n\n
Storage option<\/strong><\/th>\nList price per GB per month<\/strong><\/th>\nUse it when<\/strong><\/th>\n<\/tr>\n<\/thead>\n
Standard LRS<\/strong><\/td>\n$0.0224<\/td>\nDev and test, or data you can rebuild. The cheapest vault option.<\/td>\n<\/tr>\n
Standard ZRS<\/strong><\/td>\n$0.028<\/td>\nYou need to survive a zone failure with data staying in one region.<\/td>\n<\/tr>\n
Standard GRS<\/strong><\/td>\n$0.0448<\/td>\nProduction data must survive a regional outage. This is the default for new vaults.<\/td>\n<\/tr>\n
Standard RA-GRS<\/strong><\/td>\n$0.0569<\/td>\nWhat GRS storage becomes when you enable Cross Region Restore.<\/td>\n<\/tr>\n
Archive LRS<\/strong><\/td>\n$0.0013<\/td>\nMonthly and yearly points kept for compliance.<\/td>\n<\/tr>\n
Archive GRS<\/strong><\/td>\n$0.004<\/td>\nLong-term points that also need geo-redundancy.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

East US list prices in USD, taken from Microsoft’s Retail Prices API in October 2026. Your region, agreement or CSP pricing will differ.<\/p>\n

One more redundancy detail: Cross Region Restore, which lets you restore into the paired region even when your primary region is healthy, requires GRS and upgrades the vault’s storage to RA-GRS. At list prices that is about 27 percent more per GB than plain GRS, a fair price for audit-ready regional restore drills but not something to switch on by default for every vault.<\/p>\n

What makes storage grow<\/h3>\n

A reasonable model for VM backup is the first full copy of the used data, plus the data that changes each day, multiplied by the days of retention. Weekly, monthly and yearly points add more on top. Compression can reduce what is stored, but it does not reduce the instance fee, which is calculated before compression. Retention is the lever that surprises people: Microsoft’s Enhanced policy template defaults to 180 days of daily points, 12 weeks of weekly points, 60 months of monthly points and 10 years of yearly points. That is a defensible starting point for some regulated workloads and an expensive one for a file server whose data you could rebuild.<\/p>\n

The Archive tier<\/h3>\n

Archive storage exists for long-term retention, and the price gap is large: on LRS, Archive lists at about 17 times less per GB than Standard. Holding 1,000 GB of retained data for a month costs $22.40 in Standard LRS against $1.30 in Archive LRS, or $44.80 against $4.00 on GRS. The trade-offs are real, though:<\/p>\n