Microsoft Backup & Recovery Licensing Guide 2026

Microsoft's Backup Landscape: Products, Pricing, and What Most Organisations Miss

Microsoft has six distinct backup and archiving products, each with different licensing models, coverage scope, and cost trajectories. Most organisations deploy two or three without understanding how the billing mechanics interact — particularly how storage-based pricing compounds over a 3-year EA cycle.

The core products and their primary billing mechanisms:

• Microsoft 365 Backup: $0.15/GB/month of protected data (Exchange Online, SharePoint Online, OneDrive for Business). No per-user cap — billing scales with actual consumed storage, not allocated storage.
• Microsoft 365 Archive: $0.05/GB/month for cold compliance storage. Designed for former employee data and regulatory retention, not operational recovery.
• Exchange Online Archiving: $3/user/month standalone (included in E3/E5). Archive-only — no point-in-time restore capability.
• Azure Backup: $10/month per protected instance (VM ≤50GB) plus $0.10/GB over threshold plus vault storage. Scales non-linearly with disk size — a 2TB VM costs $160/month in instance fees alone.
• Azure Site Recovery: $25/instance/month for Azure-to-Azure replication; $16/instance/month for on-premises to Azure. First 31 days free for each newly replicated item.
• MABS/DPM: Included with Software Assurance; Azure Backup vault storage costs apply regardless. Effectively zero licence cost for SA-covered organisations but significant storage charges as data grows.

For a detailed breakdown of each product, see our Microsoft Backup & Disaster Recovery Licensing Complete Guide.

The Compounding Cost Problem

Unlike per-user licensing (which grows with headcount), backup costs grow with data volume — and data volume grows whether or not headcount does. A 1,000-user organisation with 30GB average M365 data pays $4,500/month in M365 Backup at launch. At 25% annual data growth, year-3 costs are $7,031/month — a 56% increase with no change in user count.

This compounding dynamic is the most common reason enterprises significantly under-budget backup costs in 3-year EA negotiations.

Microsoft 365 Backup: What It Covers, What It Doesn't, and What It Costs

Microsoft 365 Backup, launched in late 2023, addresses a long-standing criticism of Microsoft's native tools: the inability to perform point-in-time site or account restores without third-party tooling. It covers Exchange Online mailboxes, SharePoint Online sites, and OneDrive for Business accounts with 10-minute backup frequency and a 30-day restore window.

Coverage Gaps That Matter

Before buying M365 Backup, understand what it does not cover:

• Teams channel messages: Not included. Only Teams chat conversations (stored in Exchange infrastructure) are covered, not channel posts or meeting recordings stored in SharePoint.
• Microsoft Loop: Not covered — Loop workspaces are stored separately from SharePoint.
• Microsoft Forms responses: Not covered.
• SharePoint Server (on-premises): M365 Backup is a cloud-only product. On-premises SharePoint requires MABS or third-party tooling.
• Power Platform data: Dataverse environments have separate backup mechanisms.

Organisations with significant Teams collaboration or Power Platform investment should evaluate whether M365 Backup covers their critical data before purchasing. See our detailed SharePoint Backup Licensing Guide and OneDrive Versioning vs Backup Guide for workload-specific analysis.

Cost Modelling M365 Backup

The key variable is consumed storage, not allocated storage. Users typically consume 5-15% of their allocated OneDrive quota and 10-30% of Exchange quota. Actual consumed storage must be measured via Microsoft 365 admin centre reports before budgeting.

Org Size	Avg Consumed/User	Monthly Cost (list)	Annual Cost	3-Year Cost (25% growth)
500 users	25GB	$1,875	$22,500	~$85K
1,000 users	30GB	$4,500	$54,000	~$204K
5,000 users	35GB	$26,250	$315,000	~$1.19M
10,000 users	40GB	$60,000	$720,000	~$2.72M

Azure Backup: Instance Pricing, Hidden Costs, and What Enterprises Actually Pay

Azure Backup's pricing model creates significant billing surprises for organisations that estimate costs based on the $10/month headline figure. The actual cost for most enterprise VM estates is 2–4× the initial estimate once disk size tiers, storage costs, and SQL Server double-counting are factored in.

The SQL Server Double-Count Problem

This is the single most common Azure Backup billing surprise we encounter. When you enable Azure Backup on a VM running SQL Server, Microsoft charges both a VM instance fee AND a SQL Server instance fee for each SQL instance on that VM. A single VM running two SQL Server instances generates three backup charges: one VM fee plus two SQL fees. For a 200-VM estate with 150 SQL instances, this can add $1,500–$3,000/month in unexpected charges.

For complete pricing details and a 200-VM cost model, see our Azure Backup Licensing and Pricing Guide.

MABS vs Per-Instance Azure Backup

If your organisation has active Software Assurance, MABS (Microsoft Azure Backup Server) is the cost-optimal route for on-premises workloads. MABS is included in SA at zero additional licence cost — you only pay for Azure Backup vault storage, which is charged at standard Azure storage rates. For a 100-server on-premises estate, this can save $16,000–$30,000/year compared to Azure Backup per-instance billing.

SA lapse risk: if SA expires and you rely on MABS entitlement, your backup solution loses its licence basis. Document this dependency explicitly in your SA renewal assessment.

Azure Site Recovery: DR Licensing, Costs, and the 31-Day Free Period

Azure Site Recovery provides continuous replication for disaster recovery — keeping a live replica of VMs in a secondary region that can be activated within minutes if the primary fails. It serves a fundamentally different purpose from Azure Backup, and both are required in a comprehensive enterprise BC/DR strategy.

Pricing by Scenario

Scenario	Instance Fee	Free Period	Storage Cost
Azure VM → Azure Region (Azure-to-Azure)	$25/instance/month	31 days per new item	Cache + replica storage separate
On-premises VMware/Hyper-V → Azure	$16/instance/month	31 days per new item	Azure storage for replicas
Physical server → Azure	$16/instance/month	31 days per new item	Azure storage for replicas

The 31-day free period is a legitimate cost management tool for staged DR implementation. By sequencing replication waves in 31-day batches, organisations can defer instance fees while building out full DR coverage. For detailed cost modelling and negotiation tactics, see our Azure Site Recovery Licensing Guide.

Storage Costs Are Often Underestimated

ASR instance fees are the visible cost — but replica storage compounds significantly for large estates. A 500-VM estate with 128GB average disk size generates 64TB of replica data in the target region, costing approximately $2,560/month in LRS storage (or $5,120/month in GRS) before instance fees. Many organisations budget only for instance fees and receive storage bills 30–50% higher than projected.

Veeam vs Microsoft Native Backup: TCO for Enterprise Environments

Veeam remains the market leader in enterprise backup for a reason: it covers VMware, Hyper-V, physical servers, Azure, AWS, GCP, and M365 workloads from a single licence model. Microsoft's native tools are increasingly competitive for pure Microsoft cloud environments, but consistently lose on TCO for hybrid or multi-cloud estates.

The 3-Year TCO Decision Point

For 300 Azure VMs plus 1,000 M365 users:

• Veeam (VUL + VBO): $261,000 over 3 years
• Microsoft native (Azure Backup + M365 Backup): $421,200 over 3 years
• Difference: $160,200 in favour of Veeam for this workload profile

The TCO crossover point changes for smaller organisations or pure M365 environments where Azure Backup's low per-instance fee for small VMs becomes competitive. For a detailed comparison, see our Veeam vs Azure Backup Licensing Guide.

For a broader comparison including Commvault, Rubrik, Cohesity, and Druva, see our Microsoft Backup vs Third-Party Alternatives Guide.

Negotiation Tactics: Getting Better Terms on Microsoft Backup

Backup licensing is negotiable — but only if you approach it as a licensing decision rather than a technical one. The organisations that achieve the best backup pricing treat it as part of the EA negotiation cycle, surface competitive alternatives explicitly, and understand Microsoft's commercial incentives.

Five Proven Negotiation Levers

• Storage commitment tiers: M365 Backup and Azure Backup vault storage can be committed at fixed monthly rates, typically 10–20% below pay-as-you-go for 50TB+ commitments. Negotiate this at EA renewal, not mid-term.
• Competitive displacement pricing: Microsoft account teams have 15–25% discretionary discount on Azure Backup and M365 Backup when facing a credible Veeam or Commvault evaluation. Issue a formal RFP 9–12 months before renewal.
• MACC bundling: Azure Backup, Azure Site Recovery, and M365 Backup storage all count toward Azure MACC commitments. If you're close to a MACC tier threshold, timing backup expansion can unlock higher-tier discounts across all Azure services.
• Year-2/3 growth caps: Negotiate a cap on True Forward exposure for backup storage growth — a fixed-rate schedule for Year 2 and Year 3 storage increases prevents unexpected cost spikes from data growth compounding.
• SA for MABS: If on-premises backup is a significant cost, ensure SA is maintained for MABS entitlement. The EA negotiation should explicitly include SA for on-premises server products if MABS replaces a per-instance billing model.

Building Your Backup Licensing Assessment: The Right Framework

Before any backup licensing decision, complete a four-step assessment:

Step 1: Baseline Actual Storage Consumption

Run Microsoft 365 admin centre storage reports for Exchange, SharePoint, and OneDrive. For Azure, pull actual disk usage (not allocated) for all protected VMs. The gap between allocated and consumed storage is typically 60–80% for M365 and 40–60% for Azure VMs — this dramatically changes cost projections.

Step 2: Identify Coverage Gaps

Map your critical data against what each backup product covers. Teams channels, Power Platform, SharePoint Server, multi-cloud workloads, and physical servers each require specific coverage decisions. The most expensive gaps are the ones discovered after an incident.

Step 3: Model 3-Year Growth

Apply realistic data growth rates (25–35% for M365 collaboration data, 20–30% for Azure VM data) to your Year 1 baseline. Calculate Year 2 and Year 3 costs under both storage-based and per-instance pricing models.

Step 4: Establish Competitive Benchmarks

Get current Veeam VUL and Veeam Backup for M365 pricing from your LAR. Use this as your baseline benchmark in Microsoft EA negotiations. You don't need to switch — you need to demonstrate you've evaluated alternatives seriously.

For detailed workload-specific analysis, see:

• SharePoint Backup Licensing Guide
• OneDrive Versioning vs Backup Guide
• Microsoft 365 Backup Complete Guide
• Azure Backup Pricing Guide
• Azure Site Recovery Licensing Guide