Check Azure Backup charges before changing retention
On this page
This check is due for a source refresh. Confirm the current documentation before you rely on provider-specific details.
Backup cost cuts can remove recovery points, so separate Protected Instance, Backup Storage and Disk snapshot charges and confirm recovery needs before changing retention or Archive settings. Skip this guide for Azure Disk Backup-only scopes: they have snapshot charges, but no Protected Instance fee or Backup Storage charge.
What you need first
- Tool
- Use Azure Backup Reports, a reporting tool built on Azure Monitor logs and workbooks for backup usage and policies. Start with reports already configured for your vaults, matching billing records and current vault settings. This is a read-only worksheet, not a command.
- Access
- Ask authorized backup and billing colleagues to provide read-only report results, settings and charge lines for the selected subscriptions, vaults and completed billing period.
- If you do not use that tool
- Give those colleagues your subscription and vault list plus the billing period. Request Cloud Storage, Protected Instances, Protection Stopped items, retention policies, tiers, redundancy and matching billing lines with displayed units.
Why this is worth a look
Moving eligible backups to Archive can increase costs rather than reduce them. Azure virtual machine (VM) recovery points change from incremental to full when archived, so review Azure's recommendations, not eligibility alone.
Protected Instances are billed by the number of instances, with backed-up data size determining instance pricing. Backup Storage is charged separately, and Instant Restore snapshots are charged as Disk snapshots. Cutting one category does not address the others.
Run this check
CHECKLISTComplete these steps using existing Azure Backup Reports, billing records and vault settings, or results from authorized colleagues. Use one completed billing period and record units exactly as displayed. Do not change policies or resources.
Azure Backup charge worksheet
Scope and charge types
[ ] Record subscriptions, vaults, workloads and one completed billing period. Ask authorized backup and billing colleagues for read-only results if needed.
[ ] Separate identified Protected Instance, Backup Storage and Disk snapshot billing lines. Record labels, amounts and units exactly as displayed; do not infer missing charges from reports.
[ ] Keep Azure Disk Backup separate: its incremental snapshots bill per GiB of storage occupied by changes since the previous snapshot. It has no Protected Instance fee or Backup Storage charge. Stop this worksheet if that is the entire scope.
Usage and stopped protection
[ ] Select completed UTC days matching the review period in existing Backup Reports. Record Cloud Storage and Protected Instances with displayed units. These are end-of-period values, not monthly billed totals.
[ ] On Backup Items, select the colored Protection Stopped tile. Record the filtered items below it, their vaults and policies. Ask each owner why the retained data is needed before proposing changes.
[ ] Flag gaps: items deleted during the range are absent from the end-of-period report. Do not use absence as evidence of no billed usage.
Recovery requirements
[ ] Record Standard or Archive tier and redundancy: locally redundant (LRS), zone redundant (ZRS), or geo-redundant (GRS). If cross-region restore is enabled, note the upgrade from GRS to read-access geo-redundant storage (RA-GRS).
[ ] Record vault retention and Instant Restore snapshot retention separately. Ask the owner which recovery points and recovery locations must remain available.
Archive screening, only if proposed
[ ] Read the Archive support matrix for the workload before proposing a move. Do not archive points needed for Cross Region Restore; rehydrating them into Standard does not restore that capability.
[ ] For Azure VMs, require monthly or yearly points, at least 3 months in Vault-standard and at least 6 months of retention left. Require no active on-demand, daily or weekly dependencies, and no unexpired daily or weekly points between the candidate and the next monthly or yearly point.
[ ] For SQL Server or SAP HANA in Azure VMs, require full recovery points, at least 45 days in Vault-standard, at least 6 months of retention left and no dependencies.
[ ] For Azure VMs, request the recommendation set. Eligibility without a recommendation can mean higher overall storage costs. Flag added or removed disks, which can make recommendations inaccurate.
[ ] For stopped items with retained data, check the policy. Long-term retention allows moving recommended points to Archive; short-term retention does not support tiering in this state.
Owner decision
[ ] Record the charge category, required recovery points, policy owner and outcome: keep, investigate retained stopped data, or assess a retention/tier change.
[ ] Before seeking approval, flag that a policy change can delete older Standard and Archive points. Deleting points before 180 days in Archive can incur prorated charges for the remaining selected retention period at the Archive tier price.How to confirm it
- 01
Separate the billing categories
Record one completed billing period and split Protected Instance, Backup Storage and Disk snapshot lines using their displayed units. Exclude Azure Disk Backup from the vaulted-cost assessment; it bills incremental snapshot storage per GiB of changes since the previous snapshot.
- 02
Review stopped items with their owners
Select the colored Protection Stopped tile on Backup Items in configured Backup Reports. Ask each owner whether the retained recovery points are still required. Compare the scoped billing lines rather than assuming stopped protection means no charge.
- 03
Protect required recovery options
Confirm required retention and recovery locations with the backup owner. Use the worksheet to record storage tier, redundancy and snapshot retention. Do not propose Archive for points needed for Cross Region Restore, even if they could be rehydrated into Standard.
- 04
Assess Archive only where it fits
Check the workload rules and request Azure VM Archive recommendations before proposing a move. Treat eligible points without a recommendation as a possible cost increase, not a saving. Flag disk configuration changes when reviewing recommendations.
- 05
Send a proposal, not a deletion request
Record whether to keep the configuration, investigate stopped retained data or assess a policy change. Ask the owner to review older recovery points and Archive early-deletion charges before approval. Do not expect immediate storage reduction from Azure VM schedule changes; incremental-backup storage can shrink gradually.
Before making changes
Do not use Backup Reports as a bill reconciliation. This review assumes billing records and configured reports cover the same scope and completed period. Cloud Storage and Protected Instances are end-of-period values; items deleted during the range are omitted. Reports exclude the current partial UTC day. If reporting was newly configured, wait two days before reviewing it. Policy changes can delete older recovery points, and deleting points before 180 days in Archive can incur prorated charges.