Articles

Azure Site Recovery Pricing: Full Cost Breakdown (2026)

This guide breaks down every charge on an Azure Site Recovery bill, from the per-instance license to replica disks, egress, and drills, with a worked monthly estimate for a 20-VM setup.

Team Eon
Written by
Team Eon
Published: 
Nov 13, 2026
0
 min read

Quick Summary

  • Each protected instance is free for its first 31 days, then costs $25 a month when replicating to Azure or between Azure regions, and $16 to a customer-owned site.
  • The license is usually the smaller part of the bill. Replica disks, recovery point snapshots, cache storage, transactions, and cross-region egress bill from day one.
  • A sample 20-VM Azure-to-Azure setup with 8 TB of data comes to about $1,614 a month, with replica disks at roughly 59% and the license at 31%.
  • Price the DR region in the Azure Pricing Calculator, then budget separately for networking, firewalls, and Windows or SQL Server licensing on recovered VMs.
  • Site Recovery handles failover. Long-term retention, granular restores, and ransomware rollback need a backup layer, such as Eon for Azure workloads and Microsoft 365.

‍

Azure Site Recovery pricing looks simple on Microsoft’s page: one flat fee per protected VM. Then the first full invoice lands, and the license turns out to be the smaller half of it. Replica disks, snapshots, cache storage, and cross-region traffic all bill separately, and most of them start the day you turn replication on.

Eon’s founding team built CloudEndure, the migration and disaster recovery service AWS later acquired, so replication bills are familiar ground for us. We determined each line item from Microsoft’s published rates and built a sample 20-VM estimate you can adapt to your own fleet.

By the end, you’ll know what each charge covers, roughly what your setup will cost per month, and which costs sit outside Site Recovery entirely (including the backup layer it was never built to be).

What is Azure Site Recovery?

Azure Site Recovery (ASR) is Microsoft’s disaster recovery service. It replicates physical and virtual machines from a primary site to a secondary location, so you can fail over during an outage and fail back once the primary is healthy again.

It covers Azure VMs replicating between regions, plus on-premises VMware VMs, Hyper-V VMs, and physical servers. Azure VMs and VMware VMs replicate continuously, and Hyper-V replication runs as often as every 30 seconds.

ASR keeps a warm copy of each VM’s disks in the target location. No VMs run there until you start a test failover or a real one. That’s why storage and network make up most of the steady-state bill, and compute only shows up during drills and actual disasters.

How Azure Site Recovery billing works

Every charge on an Azure Site Recovery bill traces back to how replication moves and stores your data.

How replication turns into line items

For Azure-to-Azure replication, the data path has three steps:

  1. Disk writes on the source VM go to a cache storage account in the source region.
  2. ASR processes the cache and sends the changes to replica managed disks in the target region.
  3. ASR creates crash-consistent recovery points every five minutes and keeps them for one day by default.

Each step maps to a charge. Step one creates cache storage and transaction costs, step two creates egress and replica disk costs, and step three creates snapshot storage costs.

Replication scenarios and how each one is billed

The scenario you run changes which meters show up on the invoice. The four main setups compare like this:

Scenario License after 31 days Where storage bills Azure egress
Azure VMs to another Azure region $25/instance/month Replica disks in target region, cache in source region Yes, inter-region rates
VMware VMs or physical servers to Azure $25/instance/month Replica disks and cache in target region No (inbound transfer is free)
Hyper-V VMs to Azure $25/instance/month Storage account by default, managed disks optional No (inbound transfer is free)
Hyper-V (via VMM) to a customer-owned site $16/instance/month Your own secondary datacenter None

For on-premises sources, Azure doesn’t charge for inbound data. You still pay for the internet link or ExpressRoute circuit that carries replication traffic out of your datacenter.

Azure Site Recovery pricing: The license fee

ASR charges a flat monthly license for each protected instance (a VM or a physical server), at two rates:

Replication target First 31 days After 31 days
To Azure (including between Azure regions) Free $25 per instance per month
To a customer-owned site Free $16 per instance per month

Billing uses the average daily number of protected instances across the month. Protect 20 instances for the first half and none for the second, and you’re billed for an average of 10.

The 31 free days apply to each instance on its own. If you’ve protected 10 VMs for six months and add an 11th, only the new one gets a free month. The free period also covers the license and nothing else. Storage, storage transactions, and data transfer bill from day one, and a recovered VM can still run up compute charges.

$25 is the rate in most regions, but a handful charge more. Replication to Azure runs $27.50 in Mexico Central, $31.25 in US Gov Virginia, $32.50 in Taiwan Northwest, and $35 in Chile Central. Disk, snapshot, and compute prices also vary by region, so the region you price in changes the whole estimate.

Consumption costs on top of the license

The license is the one predictable number. Everything below scales with disk size, change rate, retention, and how often you test, and the bill breaks into the same components.

Replica managed disks

Replica disks are the copies ASR keeps up to date in the target region. For Azure VMs, replica and failover disk types normally match the source, so a Premium SSD production disk gets a Premium SSD replica. For VMware and physical machines, each source disk gets a replica managed disk billed on provisioned capacity.

Managed disks bill by provisioned tier for the whole month, whether you ever fail over or not. In Central US, a 512 GiB Standard SSD (E20) lists at $38.40 a month and a 512 GiB Premium SSD (P20) at $73.22. In our sample estimate, this line makes up about 59% of the bill.

Cache storage account

For Azure VMs, the cache account sits in the source region and holds changes until ASR processes them. Cache storage carries its own charge on top of the replica disks. Since data only passes through, the stored volume stays fairly small.

The churn setting decides the storage type. Normal Churn (the default) uses a standard storage account and handles up to 54 MB/s per VM. High Churn supports up to 100 or 500 MB/s per VM (depending on VM size) but uses Premium Block Blob storage, which runs $0.15 per GB a month in East US 2 against $0.0184 for standard hot storage.

For VMware, physical, and Hyper-V sources, the cache account lives in the target region.

Recovery point snapshots

ASR stores recovery points as snapshots of the replica disks in the target region, billed on consumed snapshot capacity. Those are incremental snapshots, which use Standard HDD storage no matter what disk type sits underneath. In Central US, that’s $0.05 per GB a month. 

ASR also takes snapshots of the source disks in the source region, so check snapshot charges in both regions when you review Cost Management.

Retention drives this line. The default policy keeps one day of recovery points, and you can go as far as 15 days on managed disks. Moving from one day to three days stores 12 more recovery points, so every extra day adds snapshot capacity.

Storage transactions

Reads and writes against the cache account are billed as storage transactions. Transaction costs climb during initial replication or a resync, especially as you add disks. After that, they follow the churn on your source disks.

On standard hot storage in East US 2, writes cost $0.05 per 10,000 operations, and Standard SSD replica disks add disk operations at $0.002 per 10,000 in Central US. That’s usually a small number. A write-heavy database VM is where it starts to show.

Network egress between regions

Egress applies only to Azure-to-Azure replication, when traffic leaves the source region. ASR compresses data before sending it, up to 50% for estimates.

The rate depends on geography. Data transfer between regions costs:

  • $0.02 per GB within North America or within Europe.
  • $0.05 per GB from North America or Europe to another continent.
  • $0.08 per GB within Asia, within Oceania, or within the Middle East and Africa.
  • $0.16 per GB within South America.

Initial replication sends the full data set. After that, only the changes cross regions, so egress tracks your daily change rate.

Compute during test failover and failover

Compute is zero for most of the month. A DR drill carries no separate fee, but the test VMs bill at normal rates while they run. Each test failover also creates new target disks from snapshots, and those keep billing until you clean up the test.

A real failover runs your full production compute in the DR region until you fail back. For reference, a D4s v5 VM in Central US costs $0.217 an hour on Linux and $0.401 on Windows at pay-as-you-go rates.

Failover capacity is also best effort. Guaranteed capacity in the target region takes on-demand Capacity Reservation, which bills separately as a VM cost.

One-time costs during initial replication

The first sync costs more than the steady state. ASR creates a temporary source disk with the same size and SKU as each data disk and bills it until initial replication finishes, which takes roughly six hours per TB.

The full data set also crosses regions once, so the seed adds a one-time egress charge on top of the monthly figure.

What a 20-VM Azure-to-Azure setup costs per month

We built this sample estimate from list prices. 

The workload assumptions are illustrative, so swap in your own numbers:

  • 20 Linux VMs replicating from East US 2 to Central US.
  • Each VM has a 128 GiB OS disk and a 512 GiB data disk on Standard SSD, so replicas use the E10 ($9.60) and E20 ($38.40) tiers.
  • 8 TB of used data across the fleet, with a 3% daily change rate (240 GB a day, about 7,200 GB a month).
  • 50% compression on replicated changes.
  • The default one-day recovery point retention.
  • Two DR drills a year, each running all 20 VMs as D4s v5 for 48 hours.
Cost line How we got it Monthly cost
ASR license 20 instances × $25 $500
Replica managed disks 20 × ($9.60 + $38.40) $960
Recovery point snapshots About 240 GB × $0.05 $12
Cache storage Rough allowance for in-flight data $5
Storage transactions Rough allowance $20
Cross-region egress 7,200 GB × 50% × $0.02 $72
DR drills (spread across 12 months) 2 × (20 VMs × 48 hours × $0.217 + test disks) ÷ 12 About $45
Total About $1,614

That’s about $19,400 a year, or roughly $80 per protected VM each month. Replica disks make up about 59% of it, and the license about 31%. Prices are pay-as-you-go list rates as of October 2026, before any enterprise discount.

A few changes move the cost:

  • Premium SSD replicas (P10 and P20) push the disk line from $960 to $1,858.60, more than the whole Standard SSD estimate.
  • Windows VMs without Azure Hybrid Benefit raise each drill’s compute from about $208 to about $385.
  • Seven days of retention can push the snapshot line toward $84 a month.
  • The first month has no license charge, but the 8 TB seed adds up to $160 in one-time egress.
  • A week-long failover adds roughly $729 in compute for these 20 VMs.

A larger fleet on Premium SSD climbs fast: a 50-VM Azure disaster recovery estimate lands above $10,000 a month.

How to estimate Azure Site Recovery pricing in the Azure Pricing Calculator

The Azure Pricing Calculator prices each service separately, so an ASR estimate is really five or six cards added together. 

Build it in this order:

  1. Add Site Recovery and set the region to the one that will host your Recovery Services vault. The vault can sit in any region except the source, which usually means your DR region, and pricing the source region by habit is an easy slip.
  2. Enter your protected instance count for the right target (Azure or a customer-owned site). The calculator shows the steady-state license, so the free 31 days won’t appear.
  3. Add Managed Disks in the DR region, with one line per disk tier and a count that matches your source disks.
  4. Add Bandwidth for inter-region transfer. Use your monthly change volume after compression, and add the initial seed as a one-time figure.
  5. Add Storage Accounts for the cache (in the source region for Azure VMs) and for snapshot capacity at your chosen retention.
  6. Add Virtual Machines in the DR region for drill hours, plus a failover scenario if you want a worst-case number.
  7. Save or export the estimate, then compare it against Cost Management after your first full month.

Microsoft also links an ASR-specific calculator for Azure-to-Azure managed disks from its cost guide. For VMware and Hyper-V, the Deployment Planner produces a cost estimation report from profiled disk and churn data.

Pro tip: measure churn before you estimate. A guessed change rate is the input most likely to throw off the egress and transaction lines.

Costs that sit outside the ASR line

A working DR region needs more than replicated disks. In our 20-VM sample, an always-on Azure Firewall alone would add more than half the ASR bill, and these components rarely show up in a Site Recovery quote. The full cost of disaster recovery runs well past the ASR line.

Network connectivity into the DR region

Users and branch offices need a path to the failed-over apps. That usually means a VPN Gateway or an ExpressRoute connection in the DR region. A VpnGw1AZ gateway in Central US runs $0.21 an hour, or about $153 a month if it stays provisioned all the time. 

Microsoft is consolidating the non-zonal VPN SKUs, so price the AZ version for new gateways.

Firewalls, load balancers, and DNS failover

Security and traffic controls have to exist in the DR region too. Azure Firewall Standard costs $1.25 an hour per deployment in Central US (about $913 a month) plus $0.016 per GB processed. Application Gateways and load balancers add their own charges.

Traffic Manager keeps DNS names stable during failover. It bills $0.54 per million DNS queries (for the first billion each month) and $0.36 per monitored Azure endpoint a month, so it’s cheap next to the firewall. The bigger decision is whether to keep these components running all the time (faster recovery, fixed monthly cost) or deploy them from code at failover (lower cost, slower recovery).

Reserved instances and capacity in the DR region

Reservations lock to a specific resource, size, and region, so the RIs you bought for production won’t discount VMs running in the DR region. Azure savings plans apply across regions automatically, which makes them the better fit for failover compute.

You can buy reservations in the DR region, and ASR failovers use them automatically. The catch is that you pay for the reservation every month, whether you fail over or not.

Windows Server and SQL Server licensing on recovered VMs

Software inside a recovered instance must be properly licensed. In Azure, pay-as-you-go Windows rates include the license, which is why that D4s v5 costs $0.401 an hour on Windows against $0.217 on Linux.

Azure Hybrid Benefit lets you run Windows Server licenses with Software Assurance at the base compute rate. For SQL Server, Software Assurance includes rights to run passive SQL Server instances for disaster recovery in Azure. 

That benefit comes into play when you protect databases with Always On replicas, which keep a VM running (and billing for compute) in the DR region all month.

There’s a reason to go that route for busy databases. ASR’s default recovery points are crash-consistent, and app-consistent snapshots stay off until you set a frequency.

How to keep Azure Site Recovery costs down

Most savings come from protecting the right VMs at the right level. 

These habits keep the bill close to the estimate:

  • Tier your workloads. Give minutes-level recovery to the apps that need it, and cover the rest with backup and restore.
  • Keep retention short. One day of recovery points is the default, and every extra day adds snapshot storage you’ll rarely restore from.
  • Stay on Normal Churn unless a VM writes more than 54 MB/s. High Churn moves the cache to Premium Block Blob storage.
  • Time-box drills and clean up each test failover. Test VMs and disks keep billing until you do.
  • Disable replication for retired VMs. The license bills on the daily average of protected instances, so a forgotten VM keeps costing $25 a month.
  • Cover failover compute with a savings plan or Azure Hybrid Benefit.

Disaster recovery vs. backup: What each one costs

Azure gives you several disaster recovery strategies: backup and restore with Azure Backup, replication and failover with Site Recovery, zone-redundant deployments inside one region, and database-native geo-replication such as Azure SQL failover groups. Most production estates use more than one.

ASR and backup get confused because both copy data somewhere else. They solve different problems and bill on different models:

ㅤ Azure Site Recovery Azure Backup
Main job Fail over to another region fast Restore data from a point in time
How far back you can go Up to 15 days of recovery points Months or years, set by policy
Pricing model $25 per instance plus disks, snapshots, egress, and failover compute Per-instance fee by protected size, plus backup storage
Typical restore Whole VM, in the DR region VM, disk, or files

Replication copies every write within minutes. That includes ransomware encryption, accidental deletes, and a bad schema change. You can roll back to an earlier recovery point, but only inside the retention window you’re paying for. Backup and replication cover different failure modes.

Backup runs on its own model of per-instance fees, storage redundancy, and archive tiers. If you’re weighing the full menu, Azure Backup pricing and the wider set of cloud disaster recovery solutions each cost out differently.

Where Eon fits

Eon sits on the backup side of that line. ASR keeps a second region ready to run, and Eon keeps the copies you restore from after corruption, deletion, or ransomware.

Eon created Cloud Backup Posture Management (CBPM). It discovers Azure VMs, SQL Server on Azure VMs, and Blob storage across subscriptions, classifies the data, and applies backup policy as new resources appear, so coverage doesn’t drift as the estate grows.

Backups land in logically air-gapped, immutable vaults in a dedicated Eon tenant, separate from your production subscriptions. Eon’s ransomware detection, a priced add-on, scans Azure VM backups so you restore from the last clean point.

Recovery is granular. Global Search finds a file across backups in seconds, and you can query SQL Server records straight from a backup, then restore just what you need to a storage account and skip rebuilding the VM. After moving to Eon, NETGEAR cut storage costs 35% and dropped recovery on a 10 TB SQL Server database from 24 hours down to 3.

The same platform covers Microsoft 365 backup for Exchange, OneDrive, SharePoint, and Teams. Pricing is usage-based per GB, and global deduplication cuts backup storage costs by 30% to 50%.

Eon doesn’t fail VMs over to another region, so it pairs with ASR. It extends what Azure’s native backup covers.

Pros and cons of the ASR pricing model

ASR’s pricing suits planned DR for a stable fleet. It also has weak spots that show up once the fleet grows.

Pros

  • The flat per-instance license is easy to forecast and the same in most regions.
  • No compute charges while you’re not testing or failing over.
  • Each new VM gets 31 license-free days, which keeps pilots cheap.
  • Drills carry no separate fee beyond the compute and disks they use.

Cons

  • Replica disks bill at full provisioned size all month, even when they’re mostly empty.
  • The cost spreads across six or more meters, which makes chargeback harder.
  • Recovery points cap at 15 days.
  • Networking, security, and software licensing for the DR region aren’t included.

Is Azure Site Recovery worth the cost?

Azure Site Recovery is worth it for workloads that need to be running in another region within minutes to hours. At about $80 per VM a month in our sample, it costs far less than a hot standby. Running the same 20 D4s v5 VMs around the clock on Linux in Central US would add about $3,170 a month in compute alone.

ASR is worth it if you:

  • Run customer-facing apps on Azure VMs where a few hours of downtime costs more than a year of replication.
  • Need tested, repeatable failover with drills that don’t disrupt production.
  • Are moving VMware or Hyper-V workloads toward Azure and want DR in place along the way.

Look elsewhere, or pair it with something else, if you:

  • Mostly need to recover from deletions, corruption, or ransomware found weeks later.
  • Run PaaS-heavy apps where the databases and storage have their own geo-replication.
  • Can tolerate a day of downtime, where backup and restore costs far less.

Budgeting the full Azure Site Recovery bill

The full monthly cost tends to land near three times the license fee, a quick way to sanity-check any estimate. Replica disks are the biggest lever; drills, egress, and snapshots stay small as long as you keep retention tight and clean up tests.

The harder question is what ASR leaves uncovered. It gives you a second region to run in, and its memory stops at 15 days. When ransomware has sat quietly for a month, or a deploy corrupted a database three weeks ago, the copy you need has to come from a backup layer with longer retention and a clean point you can prove.

Do you know which of your Azure VMs have a clean restore point older than 15 days? Book a demo and see how Eon discovers your Azure resources, applies backup policy automatically, and restores a single file or database record from an isolated vault.

Frequently asked questions

How much does Azure Site Recovery cost per month?

Azure Site Recovery costs $25 per protected instance per month after a 31-day free period, or $16 when replicating to a customer-owned site. Storage, egress, and failover compute come on top. A 20-VM Azure-to-Azure setup on Standard SSD runs roughly $1,600 a month at list prices.

Is Azure Site Recovery free for the first 31 days?

Yes, but only the license. Each protected instance skips the $25 fee for its first 31 days, while replica storage, storage transactions, and data transfer bill from the start.

Does Azure Site Recovery charge for data transfer?

Yes, for Azure-to-Azure replication. Traffic leaving the source region bills at Azure’s inter-region rates, which start at $0.02 per GB within North America or Europe. Replication from on-premises into Azure has no Azure transfer charge, since inbound data is free.

Is there an Azure Site Recovery pricing calculator?

Yes. The Azure Pricing Calculator covers the license, disks, bandwidth, storage, and VMs as separate cards, and Microsoft links an Azure-to-Azure calculator from its Site Recovery cost guide. VMware and Hyper-V users can run the Deployment Planner for a cost estimation report.

What are the disaster recovery strategies available in Azure?

Azure’s main disaster recovery strategies are backup and restore (Azure Backup), replication and failover (Azure Site Recovery), zone-redundant deployments within a region, and database geo-replication such as Azure SQL failover groups. Most teams combine at least two of them.

Is Azure Site Recovery the same as Azure Backup?

No. Azure Site Recovery replicates VMs to another location so you can fail over during an outage, with recovery points kept for up to 15 days. Azure Backup stores point-in-time copies for restores over months or years, on a separate pricing model.

FAQ

No items found.
Team Eon
Team Eon
>100% ROI in the first year

SoFi automated multi-region resilience and regulatory alignment across five AWS regions with Eon’s cloud-native platform, cutting recovery time from a day to minutes and achieving over 100% ROI.

Read case study
88% faster recovery, 35% savings

NETGEAR replaced its legacy backup provider with Eon's cloud-native platform, cutting a 10TB recovery from 24 hours to under three and reducing backup storage costs by 35% in under a week.

Read case study

Turn your backups into usable data

Eon turns your backups into instantly searchable, usable data so you can recover exactly what you need without delays.

  • Instantly search backup data with Global Search
  • Find any backup data with Global Search
  • Restore only what you need
See eon in action