Azure Site Recovery appears in every enterprise DR conversation as a low-cost replication solution — until the bill arrives. The $25/instance/month for Azure-to-Azure replication looks reasonable at 50 VMs ($1,250/month), but a 500-VM estate with cross-region replication costs $150,000/year in instance fees alone before network egress and storage replication costs are added. The organisations that manage ASR costs effectively treat it as a licensing negotiation problem, not a technical one.
ASR Pricing Structure: What You Actually Pay
Azure Site Recovery pricing splits into four distinct components: instance fees (the largest), storage costs, network egress during failover, and cache storage. Understanding each is critical because Microsoft bundles them inconsistently across documentation.
| Scenario | Instance Fee | Free Period | Storage | Network Egress |
|---|---|---|---|---|
| Azure VM → Azure VM (same region) | Not applicable | N/A | N/A | N/A |
| Azure VM → Azure Region (Azure-to-Azure) | $25/instance/month | First 31 days free per new item | Cache + replica storage charged separately | Egress on failover |
| On-premises (VMware/Hyper-V) → Azure | $16/instance/month | First 31 days free | Azure storage for replication | Egress on failover/failback |
| Physical server → Azure | $16/instance/month | First 31 days free | Azure storage for replication | Egress on failover/failback |
The pricing asymmetry is deliberate: Microsoft charges more for Azure-to-Azure ($25) because you're protecting cloud-native workloads that drive revenue. On-premises protection ($16) exists primarily to migrate workloads into Azure.
Real-World Cost Model: 300-VM Hybrid Estate
Let's walk through the actual bill for a realistic hybrid environment:
- 150 Azure VMs (Azure-to-Azure replication): 150 × $25 = $3,750/month
- 150 on-premises VMs (VMware → Azure): 150 × $16 = $2,400/month
- Cache storage (500GB LRS per region): ~$10/month
- Replica storage (3TB LRS): ~$60/month
Total: ~$6,220/month = $74,640/year
Apply a typical EA discount of 10-15% and you save $7,464–$11,196 annually. But here's what most organisations miss: this model assumes all VMs replicate continuously. The moment you pause replication (for non-production or seasonal workloads), you eliminate instance fees for those VMs while retaining the ability to protect them on demand. Strategic pausing can reduce costs 15-20%.
The First-31-Day Free Period: Tactical Use Cases
Microsoft offers 31 days of free ASR protection for each newly replicated item. This sounds generous until you understand the constraints:
How it works
When you enable replication on a VM for the first time, ASR is free for 31 calendar days. Instance fees begin on day 32. This applies to each unique replication setup — if you replicate the same VM to two different regions, you get two separate 31-day windows.
Where it fails
If you disable replication and re-enable it on the same VM/region pair, the free period does NOT restart. This is a critical trap for organisations testing DR before commitment. The timer is per replication endpoint, not per VM.
Strategic deployment
The 31-day window works best in phased migration waves. Deploy replication in cohorts aligned to your EA calendar:
- Wave 1 (Month 1): Replicate 150 VMs — 31 days free
- Wave 2 (Month 2): Replicate next 150 VMs — overlaps with Wave 1 paid period
- Total: ~15 days of free replication overlap, saving roughly $50K–$70K across the program
This approach is particularly valuable if you're testing failover procedures. Conduct your DR tests during the free period, then commit to ongoing protection. If tests fail, you can disable replication without cost.
Storage Costs: The Silent Budget Killer
ASR storage charges are buried in the Azure bill under separate line items, which means they often go unnoticed until the second billing cycle. For a 500-VM estate, storage costs can reach $4,000–$6,000/month.
Cache storage
Created in the source region, cache storage is Standard LRS at ~$0.018/GB/month. For a typical 500-VM estate with 100GB average per VM, cache storage = 50TB × $0.018 = ~$900/month.
Replica managed disk storage
The replica disk in the target region is billed as a managed disk. Pricing depends on region and disk tier:
- Standard LRS: ~$0.04/GB/month
- Premium SSD: ~$0.13/GB/month (for mission-critical workloads)
500 VMs × 128GB average replica = 64TB in Standard LRS = 64,000GB × $0.04 = $2,560/month
If 20% of your VMs require Premium replication (for high-IOPS databases), add another $655/month. Total storage across cache and replica: ~$3,500–$4,200/month for a 500-VM estate.
Log storage
Minimal but measurable. Replication logs are stored as blobs and charged per GB per month. High-churn VMs (those with sustained write activity) generate 5-50GB of logs monthly. Budget $200–$400/month for this.
Network Egress During Failover: The Surprise Charge
Most organisations fail to account for the cost of actually failing over. Azure charges data egress from source to target region at $0.02–$0.08/GB depending on regions.
Test failover (planned)
If you use an isolated test network for failover testing (recommended), egress charges do NOT apply. You're moving data between Azure regions within Microsoft's network backbone — it's free.
Unplanned failover (actual DR event)
When you failover to production, Azure counts it as egress:
- 500 VMs × 50GB average failover data = 25TB
- At $0.02/GB (intra-region Azure): $500
- At $0.05/GB (cross-region): $1,250
- At $0.08/GB (cross-geography): $2,000
One failover event across your estate could cost $500–$2,000 in egress alone. This is a negotiation point: ask Microsoft whether ASR failover events are counted toward Azure egress quotas. Some EA agreements cap total egress charges or classify ASR failover as priority replication (lower rates).
ASR vs. Zerto vs. Commvault: Where ASR Wins and Loses
Azure Site Recovery is not the best DR solution for every workload. It's best-in-class for Azure-native infrastructure but falls short in three areas: multi-cloud environments, on-premises complexity, and granular recovery objectives.
Azure Site Recovery strengths
- Cost leadership for Azure-to-Azure workloads ($25/VM/month all-in is unbeatable)
- Native integration with Azure — no third-party software to manage
- Counts toward Azure MACC spend (if you have an Azure commit)
- Acceptable RPO (30 seconds) for non-mission-critical workloads
Where ASR falls short
- Multi-cloud: ASR only replicates to Azure. If you need AWS or GCP, ASR is not an option.
- On-premises complexity: Zerto and Commvault offer better application-aware replication for complex databases and multi-tier applications.
- Sub-1-hour RPO: ASR's standard RPO is 15 minutes (VMware) to 30 seconds (Azure). Zerto achieves seconds-level RPO with continuous data protection.
- Ransomware protection: ASR has no immutable backup capability. Zerto and Commvault can isolate replicas from production networks.
Zerto (typical pricing)
$60–$90/VM/month all-in. Offers continuous data protection, sub-minute RPO, multi-cloud support. Significantly more expensive than ASR but offers feature depth ASR lacks.
Commvault (typical pricing)
$3,000–$6,000/socket for on-premises, $80K–$150K for cloud environments. Comprehensive backup and DR but complex to deploy. Used primarily by large enterprises with complex, multi-vendor environments.
For pure Azure workloads with standard RTO/RPO requirements, ASR wins on price. For hybrid or mission-critical workloads, third-party tools justify their premium.
EA Negotiation Tactics for ASR
Azure Site Recovery is treated as an Azure service within EA pricing, not a separate product line. This creates several negotiation opportunities.
Bundle with MACC
If you have an Azure MACC (Minimum Amount Commitment), ASR instance fees count toward your monthly burn. This effectively gives you a "discount" by reducing your true MACC overage risk. Frame it this way: "We're committing $800K/year to Azure compute; ASR instance fees ($74K/year) reduce our net overage exposure." Microsoft accounts teams respond to this framing.
Competitive displacement
Zerto licensing and maintenance can run $600K–$900K/year for a 500-VM estate. When you're evaluating Zerto, Microsoft will discount ASR 10-20% to prevent you from choosing Zerto. This is legitimate leverage. Formally evaluate Zerto or Commvault, request pricing from both, and use Zerto's quotes as your anchor point during EA renewal.
Staged protection commitment
Instead of committing to protect 500 VMs immediately, negotiate a ramp:
- Year 1: Protect 100 VMs at $16–$25/instance negotiated rate
- Year 2: Ramp to 300 VMs at same per-instance rate
- Year 3: Full 500 VMs with floor pricing
This reduces Microsoft's risk (they get to prove value) and yours (you get to validate DR procedures before committing). Ramp clauses are standard in large EA deals.
Test failover economics
Negotiate explicitly that test failover events using isolated test networks do NOT consume ASR test failover credits (if your agreement includes these) and do NOT incur data egress charges. This removes friction from DR testing procedures and encourages teams to test failover regularly.
Free Tier vs. Paid: When to Use Azure Backup Instead
Azure Backup and Azure Site Recovery are often confused because they both protect VMs. They serve different purposes and should not be treated as alternatives.
Azure Backup: Point-in-time snapshots. Use for accidental deletion, ransomware recovery, compliance retention. Charged per GB of protected data. Standard LRS: $0.01–$0.05/GB/month depending on tier.
Azure Site Recovery: Continuous replication. Use for disaster recovery (region failure, datacenter loss). Charged per instance per month regardless of data size.
The decision is mathematical: if you need to protect 500 VMs with 500GB average = 250TB, Azure Backup costs 250TB × $0.02/GB = $5,000/month. ASR costs 500 × $25 = $12,500/month. Backup wins on cost alone.
But if you need RPO of 30 seconds (Backup offers 24-hour RPO), ASR is mandatory.
Frequently Asked Questions
Is Azure Site Recovery the same as Azure Backup?
No — they serve fundamentally different purposes. Azure Backup creates point-in-time recoverable copies of data for protection against accidental deletion or corruption. Azure Site Recovery provides continuous replication for disaster recovery — it keeps a live replica of your VMs in a secondary region that can be activated within minutes if the primary region fails. Both are licensed and billed separately.
What RPO and RTO can we achieve with Azure Site Recovery?
For Azure-to-Azure replication, ASR achieves RPO of approximately 30 seconds (replication cycle) and RTO of minutes for planned failover. For on-premises VMware to Azure, RPO is approximately 15 minutes with standard replication frequency. These figures assume network bandwidth is not constrained — real-world RPO for high-churn VMs can be 1–4 hours.
Does Software Assurance include Azure Site Recovery?
No — SA does not include ASR licences. SA provides rights to use on-premises DR capabilities through Windows Server (failover clustering, Hyper-V Replica). Azure Site Recovery requires separate Azure subscription charges. However, SA does reduce your Azure costs indirectly through AHUB rights, which reduce Windows Server VM costs in the target Azure region.
How does the 31-day free replication period work in practice?
Each newly enabled replication item (VM or physical server) receives 31 days of free ASR protection. After 31 days, standard instance fees apply. This applies once per replication setup — disabling and re-enabling replication on the same resource does not reset the free period. The clock starts when you enable replication, not when you first test failover.
Can we use Azure Site Recovery to migrate from on-premises to Azure instead of just DR?
Yes — and many organisations do this. Microsoft allows ASR to be used for migration without converting to a migration-specific product. The economics are attractive: $16/instance/month with the 31-day free period often makes ASR migration cheaper than Azure Migrate for smaller estates. After migration is complete, you can disable ASR replication without incurring additional costs.
Internal Reference Links
For deeper dives into related topics, see our guides on:
- Microsoft Backup & Disaster Recovery Licensing Guide
- Azure Backup Licensing & Pricing
- Veeam vs Azure Backup Comparison
- Microsoft Backup vs Third-Party Alternatives
- Disaster Recovery & Software Assurance
- Azure Cost Optimisation Complete Guide
- Azure Reserved Instances Explained
- Azure Hybrid Benefit Deep Dive