Understand Azure Backup storage and retention charges

Why this is worth a look

Azure Backup has separate protected-instance and Backup Storage charges. Standard storage supports LRS, ZRS, or GRS redundancy, while eligible long-term recovery points can use Archive tier. Instant Restore creates snapshots charged as Disk snapshots. Backup Reports show usage, protected instances, policies, retention, and protection-stopped items, with Cloud Storage and Protected Instances reported at the end of the selected range. Use the billing data and reports as separate views of the charge and protection configuration.

A read-only worksheet for comparing a complete Azure Backup billing period with reported usage, protected instances, policies, retention, recovery points, storage tier, and vault redundancy.

Azure Backup charge review

Scope and window
[ ] Record the Azure subscription or billing scope and a complete billing period. Record the billing values exactly as shown in the selected billing view or export.
[ ] Confirm the review scope includes the relevant vaults and, if Backup Reports are used, the configured reporting data source.

Billed-cost review
[ ] In the selected billing view or export, identify Azure Backup-related costs for the scope and period. Use only the labels and dimensions actually present.
[ ] Separate protected-instance costs from Backup Storage costs where the billing data does so. Note Standard or Archive storage, redundancy-related details, and Disk snapshot costs when the billing data or service configuration identifies them. Do not assume a meter label that is not present.

Backup Reports and retained items
[ ] If Backup Reports are configured for the relevant vaults, select a full-day UTC range that ends before the current partial day. Record Cloud Storage and Protected Instances at the end of the selected range.
[ ] On Backup Items, use the Protection Stopped tile when available and record the items shown after that filter. Retained recovery points remain subject to their retention or archive handling.
[ ] Record the backup item, workload, vault, policy, protection state, schedule, and retention information shown by the reports. Reports cover the supported scenarios configured for the estate.

Storage and retention
[ ] Record each vault's configured redundancy: LRS, ZRS, or GRS. If cross-region restore is enabled, note that Azure Backup storage is upgraded from GRS to RA-GRS.
[ ] For material recovery points, record age, recovery-point type, retention remaining, dependencies, workload, and tier. Check the Archive support matrix: Azure VMs require monthly or yearly points, age of at least three months in Vault-standard, at least six months of retention left, and no listed active dependencies. SQL Server and SAP HANA in Azure VMs require full points, age of at least 45 days in Vault-standard, at least six months of retention left, and no dependencies. Archive is not supported for ZRS-configured vaults.
[ ] Record Instant Restore snapshot presence and retention where the backup configuration exposes it. Azure charges these snapshots as Disk snapshots.

Decision record
[ ] Classify the observed driver as protected-instance size or count, Standard or Archive storage, retention, Disk snapshots, redundancy, or retained stopped protection.
[ ] Record the recovery objective and policy owner before proposing a retention, tier, redundancy, or protection change.
[ ] Treat policy edits and recovery-point deletion as separate controlled operations. A policy change can apply to older recovery points, and Archive deletion before 180 days can incur prorated remaining-retention charges.

How to confirm it

1. 01

   Set the scope and time window

   Record the Azure subscription or billing scope and choose a complete billing period. In the selected billing view or export, identify Azure Backup-related costs using only the labels and dimensions that are present. Record billing values exactly as shown.

2. 02

   Separate the billing drivers

   Where the billing data identifies them, separate protected-instance costs from Backup Storage. Note Standard or Archive storage, vault redundancy, and Disk snapshot costs when those details are available. Azure documents that Backup Storage is separate from protected-instance costs and that Instant Restore snapshots are charged as Disk snapshots.

3. 03

   Review reports and retained items

   If Backup Reports are configured for the relevant vaults, use a full-day UTC range that ends before the current partial day. Record Cloud Storage and Protected Instances at the end of that range. On Backup Items, select the Protection Stopped tile when available and relate the displayed items to their workload, vault, policy, schedule, and retention information. Items deleted during the range are not displayed at period end.

4. 04

   Check workload-specific archive eligibility

   Record vault redundancy and cross-region restore status. For material recovery points, record workload, type, age in Vault-standard, retention remaining, dependencies, and tier. Use the support matrix: Azure VMs require monthly or yearly points, age of at least three months, at least six months of retention left, and no listed active dependencies. SQL Server and SAP HANA in Azure VMs require full points, age of at least 45 days, at least six months of retention left, and no dependencies. Archive is unavailable for ZRS-configured vaults.

5. 05

   Document a controlled decision

   Classify the observed driver as protected-instance size or count, Standard or Archive storage, retention, Disk snapshots, redundancy, or retained stopped protection. Record the recovery objective and policy owner. Treat policy edits and recovery-point deletion separately because policy changes can affect older recovery points, while Archive deletion before 180 days can incur prorated remaining-retention charges.

Primary sources