Azure Backup Licensing and Pricing: What Enterprises Actually Pay

The Hidden Cost of "Cheap" Backup Pricing

Azure Backup is deceptively cheap at first glance — $10/month per protected instance sounds reasonable until your estate hits 500 VMs, your SQL Server instances each count separately, and your storage costs compound over a 3-year EA. The enterprises that manage Azure Backup costs effectively treat it like a compute workload: right-size, reserve where possible, and negotiate storage caps at EA renewal.

The problem is structural. Azure Backup pricing has two components that are often invisibly misaligned: the protected instance fee (based on disk size, not data used) and the vault storage cost (charged at standard Azure storage rates). This creates a pricing model where organisations frequently overpay because they provision large disks for capacity headroom, then get charged backup instance fees on the full provisioned size regardless of actual usage.

For a 200-VM estate, the difference between a reactive backup deployment and an optimised one is often $200,000–$400,000 over three years. This guide walks through Azure Backup's actual pricing mechanics, shows real cost models for typical enterprise scenarios, and reveals the EA negotiation tactics that work.

Azure Backup Instance Pricing Breakdown

Azure Backup charges a monthly instance fee for each workload protected, with the fee tied to the workload size:

Workload	Instance Definition	Monthly Cost (List)	Storage Billing	Key Trap
Azure VM (≤50GB disk)	Per VM	$10/month	LRS/GRS storage separate	Disk size = disk provisioned, not used
Azure VM (50–500GB disk)	Per VM	$10 + $0.10/GB over 50GB	LRS/GRS storage separate	200GB disk = $25/month instance fee
Azure VM (>500GB disk)	Per VM	$10 + $0.10/GB over 500GB	LRS/GRS storage separate	2TB disk = $160/month instance fee
SQL in Azure VM	Per SQL instance	$10/month + VM fee	Log backups every 15–60 min add storage	Each SQL instance counted separately from VM
Azure Files	Per storage account	$10/month	Snapshot-based, minimal extra	Usually low cost
On-premises via MABS	Covered by SA	Zero if SA active	Azure Backup vault storage	SA lapse = no entitlement

Understanding the Disk Sizing Trap

This is the most expensive mistake IT teams make with Azure Backup. Azure bills based on provisioned disk size, not actual data consumption. A 2TB disk provisioned for capacity headroom is billed as:

$10 + (2,000GB - 500GB) × $0.10 = $10 + $150 = $160/month per VM.

If that 2TB disk is only 500GB full, you're still paying $160/month. Over 3 years for a 200-VM estate with average 1.5TB disks = $5,760,000 in backup instance fees alone, regardless of actual data backed up.

This is why right-sizing is non-negotiable. The negotiation tactic: before enabling backup, audit your Azure VM disk allocations. Right-size high-use VMs to actual consumption, then enable backup. A reduction from 1.5TB average to 800GB average = $60/month per VM × 200 VMs = $144,000/year savings.

SQL Server Backup Pricing — The Hidden Second Charge

One VM + one SQL instance = three backup charges: the VM instance fee, one or more SQL instance fees, and separate log backup storage.

If you enable Azure Backup on a VM running two SQL Server instances, Microsoft charges:

• One VM instance fee (e.g., $10/month for ≤50GB VM disk)
• Two SQL instance fees ($10/month each) = $20/month
• Log backup storage (charged separately at standard Azure Storage rates)

A 500-VM Azure infrastructure with 200 SQL instances generates: 500 × $10 (VMs) + 200 × $10 (SQL instances) + log backup storage = $7,000/month in instance fees = $84,000/year.

The storage surprise: SQL Server log backups run every 15 minutes by default. Over 24 hours, a moderately busy SQL instance (5GB new data per day) = 150GB monthly log backup data. For 200 SQL instances = 30TB/month = 360TB/year in log backup storage. At GRS rates (~$0.02/GB/month for cold tier storage), that's an additional $172,800/year.

Total SQL backup cost for 200 instances = $84,000 (instance fees) + $172,800 (storage) = $256,800/year. Few organisations budget this level of clarity.

Vault Storage Costs — The Second Hidden Line Item

Beyond instance fees, Azure Backup stores data in Azure Storage accounts (blob storage). Storage is charged at standard Azure Storage rates, which vary by:

• Redundancy model: LRS (locally redundant, ~$0.012/GB/month) vs GRS (geo-redundant, ~$0.024/GB/month)
• Access tier: Hot (~$0.012/GB/month) vs Cool (~$0.004/GB/month) vs Archive (~$0.0001/GB/month)
• Backup data volume: Actual size of backups retained

For a 200-VM estate with 100TB backup vault storage retained at GRS rates = 100,000GB × $0.024 = $2,400/month = $28,800/year.

The compounding growth: Backup vault storage grows 25–40% annually as VMs are provisioned and data volumes increase. Year 1: $28,800. Year 2: $36,000–$40,320. Year 3: $45,000–$56,450. Over three years = $110,000–$125,000 in vault storage costs for that single estate.

Many organisations select GRS (geo-redundancy) without cost analysis. For non-critical development/test workloads, LRS is sufficient and cuts storage costs by 50%.

Real Cost Model: 200-VM Azure Estate

Assumptions: 200 Azure VMs with mixed sizes, 50 running SQL Server (average 2 SQL instances each = 100 SQL instances total), average VM disk 300GB (mix of small and large), GRS backup storage retention 30 days average.

• VM instance fees: 150 VMs × $10 = $1,500/month
• Large VM fees (50 VMs, avg 400GB disk): 50 × ($10 + 350 × $0.10) = 50 × $45 = $2,250/month
• SQL instance fees: 100 SQL instances × $10 = $1,000/month
• Subtotal instance fees: $4,750/month = $57,000/year
• Vault storage (GRS, 150TB average): 150,000GB × $0.024 = $3,600/month = $43,200/year
• Log backup storage (200 SQL instances, 30TB/month): 30,000GB × $0.024 = $720/month = $8,640/year
• Total Year 1: ~$108,840/year

Year 2 (25% storage growth): Instance fees stable at $57,000. Storage: ($43,200 + $8,640) × 1.25 = $64,800. Total = $121,800/year.

Year 3 (additional 25%): Total = ~$150,000/year.

3-year cumulative cost: ~$380,000+

Azure Backup vs. MABS vs. Per-Instance Agents

Deployment Model	What It Protects	SA Requirement	Azure Backup Vault Cost	Best For
Azure Backup (cloud-native)	Azure VMs natively, SQL in Azure, Azure Files	None	Yes, charged at standard storage rates	Cloud-only estates; minimal on-premises
MABS (on-premises)	On-premises VMs, SQL, File shares, DPM-compatible workloads	Yes, required	Yes, but no per-instance fees	100+ on-premises machines; hybrid estates
Per-instance agents	Individual servers via installed agent	None	Yes, charged at standard storage rates	Small estates; <50 machines

MABS Cost Advantage for On-Premises Workloads

If you have Software Assurance, MABS is zero-cost licensing. MABS (Microsoft Azure Backup Server) is essentially System Center DPM with Azure connectivity — it protects on-premises workloads and pushes backups to Azure Backup vault. The only charge is vault storage; there are no per-instance fees.

Comparison for 100 on-premises servers:

• Per-instance agent model: 100 servers × $10/month = $1,000/month = $12,000/year (instance fees only; storage additional)
• MABS model (with SA): $0 instance fees; storage only (~$1,500/month = $18,000/year)
• Net savings: $12,000/year with MABS

The catch: MABS requires a dedicated server (physical or VM) to run the backup appliance, plus SA entitlement. If your SA lapses (common during EA transitions), you lose MABS entitlement and must switch to per-instance agents retroactively, risking coverage gaps.

EA Negotiation Tactics for Azure Backup Costs

Tactic 1: Committed Storage Tiers

Most organisations negotiate Azure Backup storage as a committed tier rather than pay-as-you-go. The agreement is: "We commit to 500TB backup vault storage for 12 months in exchange for 15% discount on standard GRS rates."

Calculation: 500TB committed at 15% discount = 500,000GB × $0.024 × 0.85 = $10,200/month ($122,400/year). Without commitment = 500,000GB × $0.024 = $12,000/month ($144,000/year). Savings = $21,600/year.

How to negotiate: Provide Microsoft's account team a 12-month projection of expected backup storage based on your VM provisioning roadmap. The more predictable your forecast, the larger the discount. If you're uncertain, start conservative; overage storage is billed at list price, which is often acceptable trade-off.

Tactic 2: GRS vs LRS Strategic Choice

Many organisations default to GRS (geo-redundant storage) for "safety," but for non-critical workloads (development, test, lower-priority production), LRS is sufficient. LRS costs half GRS.

Audit your backup vault tiers:

• Critical production workloads: GRS (~$0.024/GB/month)
• Secondary production / mid-tier workloads: LRS (~$0.012/GB/month)
• Dev / test / low-priority: Archive tier (~$0.0001/GB/month) with longer retrieval SLA

A 200-VM estate splitting 50% GRS / 30% LRS / 20% Archive reduces storage costs by ~30% while maintaining adequate DR SLA coverage.

Tactic 3: MACC Consumption Timing

Azure Backup costs count toward your Azure Consumption Commitment (MACC). If your MACC is $500,000/year and you're at 70% consumption, you're leaving 30% × $500,000 = $150,000 of committed spend unused. This money goes to Microsoft whether you consume it or not.

Lever point: "We will expand our backup storage footprint by 200TB in Q1 2026, which will add ~$50,000/year to our backup costs. If you tier our MACC to $600,000/year without increasing the percentage discount, we gain full MACC utilization and you gain incremental committed revenue."

This is a legitimate negotiation point during EA renewals or amendments because it converts unused MACC capacity into actual spend.

Tactic 4: SQL Server Log Backup Frequency Negotiation

The default SQL log backup frequency is every 15 minutes, which creates enormous vault storage overhead. If your backup SLA permits, negotiate reduced backup frequency (e.g., hourly log backups instead of 15-minute) to reduce log backup storage volume by 75%.

For 200 SQL instances at 30-minute backup frequency instead of 15-minute = 50% reduction in log storage = ~$4,320/year savings. Aggregate across 200-500 instances = $50,000–$100,000/year for marginal SLA changes.

Tactic 5: Backup Storage Cost Caps at EA Renewal

Microsoft will negotiate cost caps for backup storage growth as part of larger EA amendments (especially if you're committing >$1M/year in Azure MACC). The structure is typically:

"Year 1 backup storage at negotiated GRS rate. Year 2 capped at 20% growth above Year 1. Year 3 capped at 20% growth above Year 2. Growth beyond 20% per year is at no charge."

This converts open-ended backup cost growth into predictable budgeting and incentivises Microsoft to help you optimise backup efficiency.

Azure Backup vs. Veeam Backup for Azure — When to Consider Alternatives

Veeam Backup for Microsoft Azure is a third-party backup solution designed for Azure-native workloads. Pricing is typically $1,400–$2,200 per 10-workload Universal Licence with 1-year maintenance included.

Cost comparison for 200 Azure VMs:

• Azure Backup (built-in): $108,840/year (as calculated above)
• Veeam Backup for Azure: (200 VMs / 10) × $2,000 × UL model = Cost depends on licensing structure, typically $30,000–$50,000 year-1 + $10,000 annual maintenance. Add storage if using Veeam-managed backup vault: ~$20,000/year = $50,000–$70,000 total.

When Veeam makes sense: If you require cross-cloud backup (Azure + AWS), advanced compliance features (immutable backups, ransomware detection), or tighter RTO/RPO SLAs, Veeam justifies the cost. For pure Azure-only estates, Azure Backup is cheaper unless you're optimising heavily.

Negotiation use: Surface Veeam pricing during EA renewal to pressurize Microsoft account teams to improve Azure Backup pricing or add complementary features.

FAQ: Azure Backup Licensing and Pricing

Does Azure Backup pricing include storage, or is storage charged separately?

Azure Backup uses two separate billing lines: a protected instance fee (based on workload size) and vault storage costs charged at standard Azure storage rates. The instance fee covers the backup service; storage costs depend on vault redundancy (LRS vs GRS) and actual backup data volume. Both line items appear on your Azure bill separately.

If we have Software Assurance, is Azure Backup included?

Not entirely. SA provides entitlement to MABS (Microsoft Azure Backup Server) for on-premises workloads — essentially System Center DPM functionality with Azure connectivity. However, Azure Backup vault storage costs are always charged separately even with SA. Purely cloud workloads (Azure VMs, SQL in Azure) are charged at standard Azure Backup instance rates regardless of SA status. The benefit of SA is eliminating per-instance fees for on-premises workloads protected via MABS.

How does Azure Backup pricing compare to Veeam for Azure VMs?

For smaller Azure estates (under 100 VMs), Azure Backup is often cheaper. Above 300+ VMs, Veeam Backup for Microsoft Azure becomes cost-competitive at $1,400–$2,200 per 10-workload Universal Licence. The tipping point depends on your VM size distribution — large-disk VMs (>500GB) are disproportionately expensive under Azure Backup's instance fee model. For mixed estates or cross-cloud requirements, Veeam's supplemental capabilities may justify the cost difference.

Are SQL Server backups charged separately from VM backups in Azure?

Yes — this is one of the most common Azure Backup billing surprises. If you enable Azure Backup on a VM running SQL Server, you will receive BOTH a VM instance fee and one or more SQL instance fees. A single VM running two SQL instances generates three backup charges: one VM instance fee ($10/month) + two SQL instance fees ($10/month each). Additionally, SQL log backups (running every 15 minutes by default) generate significant vault storage charges separately.

Can we cap Azure Backup costs in our EA to prevent runaway storage growth?

Microsoft will negotiate storage cost caps for Azure Backup as part of an EA amendment, particularly for organisations committing >$1M/year in Azure MACC. The mechanism is typically a committed storage tier (e.g., 500TB reserved at a fixed monthly rate) with overage capped at list price, rather than a flat cap. Cost caps require you to provide accurate forecasting of backup storage growth; Microsoft will reserve the right to review actual vs projected usage quarterly.

Related Azure and Backup Licensing Resources