Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Azure Backup bill explained: protected instance charge and backup storage

Technical article
Backup & Recovery

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

An Azure Backup bill has two separate parts. The first is a fee for each protected instance, set by the size of the data being protected, before compression and encryption, in size bands. The second is a charge for the backup storage consumed, which depends on how much data is held across all recovery points and on the redundancy you chose. Microsoft's pricing page says so directly: "Charges for storage are separate from the cost of Azure Backup Protected Instances."

Most surprises come from the second part, and from billing that carries on after protection has stopped. The sections below explain how each part is counted, from Microsoft's own documentation, and where to look in your account. It quotes no prices, because they differ by region, currency and agreement.

What are the two parts of an Azure Backup charge?

Protected instance. Microsoft's pricing estimate page lists the fee inputs. The pricing page says "the size of the backed-up data determines the pricing for Azure Backup in each protected instance before compression and encryption." A protected instance is, in the FAQ's words, "a computer, server (physical or virtual), or workload that backs up to Azure."

Backup storage. Microsoft's VM page says "the backup storage bill is based on the amount of data that's stored in Azure Backup, which is the sum of the actual data in each recovery point." The pricing page quotes a "per-GB, per-month charge" for storage, listed separately for each redundancy option.

For an Azure VM, billing doesn't start until the first successful backup finishes. From then, "the billing for both storage and protected VMs begins."

How is the size of a protected instance counted?

The pricing page sets out these size bands for VMs and on-premises servers. It prints a price against each, which is not repeated here.

Size of each instance How it is charged
50 GB or less A flat fee per instance, plus storage consumed
More than 50 GB, up to 500 GB A higher flat fee per instance, plus storage consumed
More than 500 GB A fee "for each 500 GB increment", plus storage consumed

The page's own example is an instance with 1.2 TB of data. Its cost is "plus storage consumed", and the page charges the same amount "for each of the two 500 GB increments" and for "the remaining 200 GB data". The leftover 200 GB is therefore charged as a full increment, not prorated, and a 1.2 TB instance is three increments. The page does not state whether GB means decimal or binary units; it treats 1.2 TB as 1,200 GB.

What counts as "size" depends on the workload:

  • For VMs, the pricing page says the size is "based on actual (used) size of VM", which is "the sum of all data in the VM, excluding temporary storage."
  • For files and folders, "the size of the files and folders configured for backup determine the data size."
  • For SQL Server, "the size of the databases configured for backup determine the data size."

The VM page adds a detail: for agent-based application-consistent or file-system-consistent backups, pricing "is based on the actual data that's stored on the data disks, not on the maximum supported size for each data disk." For the agentless multi-disk crash-consistent VM backup, the same page says only that the release "includes changes to billing; see the pricing details." Microsoft's VM page does not spell out those changes, so check the current pricing details if you use that option.

The page gives a worked case: an OS disk with 17 GB used, a data disk with 30 GB, another with 0 GB, and a 5 GB temporary disk "not included for backup". The protected-instance size is 17 + 30 + 0 = 47 GB, which falls in the first band.

The instance size follows the data. "As the amount of data in the VM grows, the protected-instance size used for billing changes to match." A VM that crosses 50 GB or 500 GB moves into a higher band.

How is backup storage counted?

Microsoft's pricing estimator asks for the inputs that drive the storage figure. For Azure VMs and servers these are the used size, the number of servers, the daily churn, and how long to keep daily, weekly, monthly and yearly backups. Churn is defined as "the amount of change in data", with the example that "if you had a VM with 200 GB of data to be backed up and 10 GB of it changes every day, the daily churn is 5%." The page adds: "Higher churn will mean that you back up more data", and suggests Low or Moderate for file servers and High for databases.

Microsoft does not publish the estimator's formula in its pricing documentation. Treat the inputs as the list of things that move the number:

  • Retention. Each kept recovery point adds the data that changed since the one before. Longer retention means more recovery points. The FAQ says each recovery point "behaves like a full point" for restore purposes, while the storage architecture is described as optimising storage; it does not give a ratio.
  • Churn. Databases change more than file servers, so the same retention costs more.
  • Instant Restore snapshots. The pricing page says they "are present in Disks and are charged as Disk snapshots", so they appear as disk snapshot charges rather than in the backup storage line. The estimator takes 1 to 5 days of them for the Standard policy and 30 days for the Enhanced policy.
  • Selective disk backup. Excluded disks are not backed up, so they reduce the size.
  • Archive tier. Monthly and yearly backups kept longer than six months can be moved to an Archive tier. Moved data "is subject to an Archive early deletion period of 180 days", charged pro rata, and restoring from Archive adds a retrieval fee. Restoring from the Standard tier "is free of charge and does not incur any transaction or egress charges."

Which redundancy option changes the storage line?

The pricing page says that in the Standard tier you can choose between locally redundant storage (LRS), zone-redundant storage (ZRS) and geo-redundant storage (GRS). If you enable Cross Region Restore, "we upgrade your backup storage from GRS to read-access geo-redundant storage (RA-GRS)." Each option has its own per-GB rate on that page.

The vault page says "be sure to change the storage replication type for a Recovery Services vault before you configure a backup in the vault. After you configure a backup, the option to modify is disabled." Microsoft's guidance is to keep the default GRS if Azure is your primary backup endpoint, and to choose LRS "to reduce storage costs" if it is not.

Disruptive step: moving a vault from GRS to LRS after backups exist. Microsoft calls one route "destructive and can't be undone": delete the protection and data in the GRS vault and reconfigure in a new LRS vault. The other route keeps the old recovery points in the GRS vault, where "you need to pay to keep" them while you build up the new vault. Back out only by keeping the old vault until the new one holds the history you need.

What does soft delete add to the bill?

Microsoft's soft delete page says deleted backup data is kept in a soft-deleted state for 14 days by default, extendable "up to 180 days". It adds: "You don't incur additional costs for 14 days. However, you're charged for any period beyond 14 days."

The page's example shows where the free days fall. With 60 days of soft-delete retention, "standard rates apply for the first 46 days (60 days of configured soft-delete retention, minus 14 days of default soft-delete retention)". There are "no charges for the last 6 days" of a recovery 52 days after deletion. So the free 14 days sit at the end of the window.

This rule does not apply everywhere: "the preceding billing rule doesn't apply for soft-deleted operational backups of disks and VM backup snapshots. The billing continues according to the cost of the resource." For what soft delete stops from a security view, see Azure Backup soft delete, immutable vaults and multi-user authorisation, which has its own topic.

Does billing stop when protection stops?

Not by itself. The VM page says "if you stop protection for a VM, but backup data for the VM exists in a vault, billing continues." It continues until "the protection is stopped and all backup data is deleted." While data is retained, "the size of the last successful VM backup becomes the protected instance size used for the monthly bill."

Disruptive step: deleting backup data to end billing. Once soft-delete retention elapses, "the item is permanently deleted, and you can't restore it." There is no way back after that point. Confirm that no restore, audit or legal need remains before the retention window closes.

Worked numbers

Example (illustrative): a small business protects three servers in one vault. app01 has 40 GB used, sql01 has 320 GB, and fs01 has 1,200 GB. All use agent-based file-system-consistent backups.

  • app01: 40 GB is 50 GB or less, so it falls in the first band.
  • sql01: 320 GB is above 50 GB and not above 500 GB, so it falls in the middle band.
  • fs01: 1,200 GB is above 500 GB. Following the page's own example, that is two 500 GB increments plus the remaining 200 GB, and the page charges the remainder at the same amount as a full increment, so fs01 is three increments (2 + 1 = 3).
  • Instance fees therefore total one first-band fee, one middle-band fee, and three increment fees. The fee amounts are in the price table for your region; no price is used here.
  • Storage is a separate line: GB held across all recovery points multiplied by R per GB-month for the chosen redundancy. Microsoft does not publish a formula for GB held, so use the estimator for that figure.

Now the owner deletes fs01's backups, with soft-delete retention set to 60 days, and asks for them back 52 days later. Following Microsoft's example: 46 days are charged at standard rates and the last 6 days are free.

How do you check this on your own account?

  1. List what is protected and its size. The vault's backup items give each instance. Microsoft's diagnostic data model lists a front-end size field, BackupItemFrontEndSize ("Front-end size (in MBs) of the backup item"), and a storage-consumed field, StorageConsumedInMBs ("Backup storage consumed by the backup item"). The page recommends system functions on Azure Monitor logs rather than the raw tables for reports.
  2. Place each instance in a size band. Use the used size, not the disk size.
  3. Open the cost export for the month. Microsoft's cost details fields include MeterCategory, MeterSubCategory, MeterName, ResourceId, Quantity, UnitOfMeasure and, for Enterprise Agreement and Microsoft Customer Agreement accounts, CostInBillingCurrency. The cost details page does not list Azure Backup's meter names, so group the vault's rows by MeterName and compare the unit in UnitOfMeasure. Look for snapshot charges on the VM or disk resource, not the vault. Azure cost exports and bill drivers have their own topic, which covers reading Actual and Amortized exports.
  4. Compare the storage quantity with StorageConsumedInMBs, and the instance count with the protected items you expect.
  5. Ask whoever sells the subscription, if it is not Microsoft directly: which redundancy is set, what soft-delete period is set, which items are stopped with data retained, and whether any data sits in the Archive tier.
  6. Download Microsoft's pricing estimator and enter the same sizes, churn and retention, then compare it with the bill.

Risks and limits

  • Prices are not quoted, and the pricing page shows regional price data that changes. The size bands and charge structure above come from the pricing page, which shows no date. The estimator page was updated on 2026-08-26.
  • Microsoft's storage formula is not published, so the storage line cannot be calculated exactly from a bill. The estimator is Microsoft's own guide.
  • Microsoft's pricing pages do not say whether GB is 1,000 or 1,024 million bytes. A boundary case near 50 GB or 500 GB should be checked with the unit shown on your own bill.
  • Agentless multi-disk crash-consistent VM backups have separate billing changes that Microsoft's VM page does not detail.
  • Meter names and cost export values vary by agreement type and change over time. Check yours.
  • Soft-delete behaviour has regional and vault-type differences; the page describes secure-by-default soft delete as in preview for some vault types and generally available for others.

Sources