Azure Ransomware Recovery Solutions Compared (2026)

Compare 8 ways to recover Azure VMs and Azure SQL after ransomware: where copies live, how each finds a clean recovery point, recovery speed and published pricing.
Share post:

Quick summary

  • Yes, several tools specialize in ransomware recovery for Azure. They differ on three things: where the recovery copies live, how you find a clean recovery point, and whether you get back whole environments or single VMs.
  • Azure Backup is the baseline. Immutable vaults, soft delete and multi-user authorization protect the copies. Vaulted VM backups run no more often than every 4 hours, and its threat detection (preview) reads Defender alerts on the source VM rather than scanning backups.
  • Azure Site Recovery is replication, built for failover. Its oldest usable recovery point is 15 days old, so an attack that sat undetected longer than that leaves no clean replica.
  • Scanning for a clean point: Commvault, Veeam, Rubrik, Cohesity and Druva each scan backups for threats in some form, with different limits on Azure.
  • N2W keeps backups in your own Azure subscription, as often as every 60 seconds, and brings back VMs with their VNet in an order you set. A copy in Wasabi, under separate credentials, survives a compromised Azure tenant. It doesn’t scan for malware. The Standard plan is $249 a month for up to 20 instances.

Which Azure ransomware recovery solution is fastest?

The fastest recovery comes from a recent, clean copy that an attacker with your Azure credentials couldn’t delete, restored together with the network it needs. Here is how each option handles those three parts.

ToolWhere recovery copies liveFinding a clean recovery pointRecovery path on AzureShortest backup interval on AzurePricing
N2WYour own Azure subscription; archive copies in Azure Blob or WasabiYou choose the point; no malware scanningVMs, disks and Azure SQL, cross-region and cross-subscription, VNet and subnets included, ordered Recovery Scenarios60 seconds$249/month for up to 20 instances (Standard); higher plans quote-based
Azure BackupMicrosoft-managed vaults, isolated from your tenantThreat detection (preview) flags points from Defender alerts on the source VM; no scan of the backup itselfRestore VMs, disks and databases; Cross Region Restore from GRS vaults4 hours (Enhanced policy)Per protected instance by size band, plus storage. A 50 to 500 GB VM is $10/month in East US
Azure Site RecoveryReplica disks in a second regionNone; you pick a recovery point up to 15 days oldFailover of whole VMs with recovery plans; 1-hour RTO SLACrash-consistent point every 5 minutes (replication)$25 per instance per month in East US; first 31 days free
VeeamYour own Azure Blob storage (immutable), or Veeam Data CloudSecure Restore scans before restoring, with Veeam Backup & Replication 13Restore Azure VMs, SQL and Cosmos DB; restore into an isolated VNet if a threat is foundPer policyFree up to 10 instances; Veeam Data Cloud for Azure $42 per TB/month
Commvault CloudYour Azure Blob, or Air Gap Protect (Commvault-managed, on Azure)Anomaly detection on backup jobs; Threat Scan on Air Gap Protect copiesCleanroom Recovery into an isolated Azure environmentPer policyVM Backup $102.49 per 10 VMs/month; Cleanroom quote-based
Rubrik Security CloudRubrik-managed storage (Rubrik Cloud Vault)Anomaly detection; threat hunting for Azure VMsCyber recovery of Azure VMs into an isolated environmentPer SLA policyQuote-based
CohesityCohesity’s SaaS, or FortKnox (Cohesity-managed vault)Anomaly detection and threat scanning in FortKnoxRestore to another subscription, region or resource group; clean room recoveryPer policyQuote-based
DruvaDruva’s cloud, outside your Azure tenantThreat Hunting scans past snapshots before a restoreRollback of encrypted disks; cross-region restoreNot publishedNot published
ZertoReplica in a second region, journal up to 30 daysEncryption detection is not available on AzureJournal-based failover to a point seconds before an attackContinuous replicationPer VM; not published

The prices cover different things. N2W and Veeam’s appliance license software, and you pay Azure for the storage. Veeam Data Cloud, Commvault Air Gap Protect, Cohesity and Druva store copies themselves, so storage is in their price. Compare what each one covers before you compare totals.

What makes ransomware recovery on Azure fast, or slow

Four things decide how long you’re down.

  1. How recent the clean copy is. An attacker usually sits in the environment before encrypting. You need a recovery point from before the intrusion, which means frequent backups kept long enough to reach past the dwell time. Azure Site Recovery keeps at most 15 days of points; vaulted Azure Backup keeps longer history but runs no more often than every 4 hours.
  2. Whether the attacker could delete it. If the copies sit under the same Azure identity the attacker took, a lock is only as strong as the permissions around it. An Azure Owner can remove a resource lock. Microsoft’s locked immutable vault and multi-user authorization close much of that gap inside Azure; a copy with a different provider closes it completely.
  3. Where you restore from. A restore from a snapshot is fastest: Azure attaches the disk right away and hydrates it in the background. A restore from a vault or an archive tier copies data first and takes longer. Plan which copy you’ll restore from before you need it.
  4. Whether the environment comes back, or just the VMs. VMs restored without their network, in the wrong order, don’t run an application. Recovery that brings back the VNet and starts the tiers in sequence turns a pile of restored machines into a working service.

For the native mechanisms in more depth, see why Azure soft delete alone won’t stop ransomware and Azure immutable backups.

How we evaluated these tools

We compared each option on five criteria, checked against each vendor’s own documentation and pricing pages in November 2026:

  1. Copy isolation. Where recovery copies live, and who can delete them.
  2. Clean-point help. Whether the tool scans backups or flags suspicious recovery points, and how that works on Azure specifically.
  3. Recovery path. Single VMs or whole environments, across regions and subscriptions, with or without the network.
  4. Backup frequency. The shortest interval on Azure, which sets how much data you lose.
  5. Pricing. What’s published, and what the price includes.

N2W is our product, so it’s listed first. The list covers Azure IaaS workloads. Microsoft 365, Entra ID and endpoint backup are out of scope.

The 8 best Azure ransomware recovery solutions

1. N2W

What it does: Backup and disaster recovery software you deploy in your own Azure subscription (or AWS account). Backups stay in your subscriptions, and N2W never holds or accesses your data. One console covers Azure, AWS and Google Cloud.

Best for: Teams running Azure VMs, disks and Azure SQL, alone or alongside AWS, that want frequent backups in their own subscriptions and ordered recovery of whole environments.

Key features:

  • Backups as often as every 60 seconds, agentless on Azure through Azure APIs and snapshots.
  • Immutable copies through Azure’s own locks: a Delete lock on VM and disk snapshots, and a lease on every object in an Azure storage repository.
  • A copy outside Azure. Archive Azure backups to Wasabi, a separate provider with its own object lock and credentials, so a compromised Azure tenant can’t reach that copy.
  • Recovery Scenarios bring many VMs back together, in parallel or in a set order, across regions or subscriptions. N2W captures the Azure VNet configuration and subnets with the VMs. Scheduled Dry Runs check a recovery without launching anything.
  • A posture view of protected and unprotected resources and immutability status across every connected cloud, with up to 200 unprotected resources added to a policy in one click.

Pros:

  • Frequent recovery points to roll back past an attacker’s dwell time
  • A true air gap through a second provider
  • Restores from snapshots in your own subscription, which is the fastest path Azure offers: recovery takes minutes

Cons:

  • No malware scanning or anomaly detection; you choose the clean recovery point yourself
  • On Azure, an Owner can remove the Delete lock or cancel the lease. That’s why the Wasabi copy matters
  • Azure coverage is VMs, managed disks and Azure SQL. No Azure Files, Blob workloads or AKS

Pricing: The Standard plan is $249 a month for up to 20 protected instances. Advanced, Enterprise and Enterprise+ are quote-based. Price is set by instance count, not data volume, and Azure storage stays on your own Azure bill. See N2W pricing.

Bottom line: The fit when your priority is a recent copy you control, outside Azure if needed, and an environment that comes back in order.

2. Azure Backup

What it does: Microsoft’s native backup service for Azure VMs, disks, SQL Server and SAP HANA in VMs, Azure Files, Blob and more, stored in Recovery Services or Backup vaults.

Best for: Azure-only teams that want ransomware protection built into the platform they already pay for.

Key features:

  • Immutable vaults. Enabled and locked, the setting can’t be reversed, so recovery points can’t be deleted or have retention cut before they expire.
  • Soft delete keeps deleted backups for 14 to 180 days (the first 14 free).
  • Multi-user authorization through Resource Guard, which can sit in a separate subscription or tenant, so one stolen admin account can’t turn off protection.
  • Threat detection (preview) marks recovery points as suspicious from Microsoft Defender for Servers alerts on the source VM.
  • Cross Region Restore from geo-redundant vaults.

Pros:

  • Nothing to deploy, and strong in-tenant controls once the vault is locked and MUA is on

Cons:

  • Vaulted VM backups run no more often than every 4 hours, under the Enhanced policy
  • Threat detection doesn’t scan the backups themselves, and Microsoft says so
  • Cross Region Restore can lag the primary by up to 36 hours
  • Not a free tool: The price increases with the amount of data on each VM

Pricing: A monthly fee per protected instance by size band, plus storage. An Azure VM of 50 to 500 GB is $10 a month in East US before storage.

Bottom line: Lock the vault and turn on multi-user authorization whatever else you use. On its own, the 4-hour interval and the lack of backup scanning are the gaps.

3. Azure Site Recovery

What it does: Microsoft’s replication and failover service. It copies VM disks to a second region continuously and fails over whole VMs with recovery plans.

Best for: Regional outages, and ransomware caught within days.

Key features:

  • A crash-consistent recovery point every 5 minutes, app-consistent as often as hourly.
  • Recovery plans that fail over groups of VMs in order.
  • A 1-hour RTO SLA.

Pros:

  • The fastest native failover of complete VMs

Cons:

  • Replication copies encryption to the replica. The oldest usable point is 15 days old, so a longer dwell time leaves nothing clean
  • No long-term history and no immutability, so it can’t stand in for a backup

Pricing: $25 per protected instance per month in East US, free for each instance’s first 31 days.

Bottom line: Pair it with a backup, never use it in place of one.

4. Veeam

What it does: Veeam Backup for Microsoft Azure is an appliance in your subscription that backs up Azure VMs, Azure SQL, Cosmos DB and VNet configuration to your own storage. Veeam Data Cloud for Azure is the SaaS version.

Best for: Teams already running Veeam Backup & Replication on-premises.

Key features:

  • Immutable backups in Azure Blob, for the full retention period. Veeam says even a Global Administrator can’t delete them.
  • Secure Restore scans a backup with Veeam Threat Hunter, antivirus or a YARA rule before restoring, then stops the restore or restores into a different VNet.
  • Veeam Data Cloud for Azure keeps backups immutable and isolated from production.

Pros:

  • Malware scanning before restore, and the option to restore into isolation

Cons:

  • Secure Restore needs a Veeam Backup & Replication 13 server, not the appliance alone
  • The free edition leaves out Cosmos DB and VNet configuration backup

Pricing: Free for up to 10 instances. Beyond that, per-instance licensing under the Veeam Universal License, quote-based. Veeam Data Cloud for Azure is $42 per TB a month (MSRP; varies by reseller).

Bottom line: Strongest on scan-before-restore if you run the full Veeam stack.

5. Commvault Cloud

What it does: Commvault’s data protection platform, as SaaS or self-managed software, covering Azure VMs, Blob, Files and AKS along with data-center and SaaS workloads.

Best for: Enterprises that want a dedicated, isolated recovery environment in Azure.

Key features:

  • Cleanroom Recovery restores Azure VMs and Active Directory into an isolated Azure environment, with orchestrated SQL Server restore.
  • Air Gap Protect: immutable Azure Blob storage that Commvault manages.
  • Anomaly detection flags VM backups on file activity, file types and backup size, and Threat Scan checks Air Gap Protect copies on demand or when an anomaly is found.

Pros:

  • A ready-made clean room on Azure, so you don’t restore into a compromised network

Cons:

  • Cleanroom Recovery doesn’t support encrypted Azure disks
  • Threat Scan doesn’t run on a schedule

Pricing: VM Backup is $102.49 per 10-VM pack per month, Azure included. Cleanroom Recovery is quote-based.

Bottom line: The most complete clean-room story on Azure, at enterprise scope.

6. Rubrik Security Cloud

What it does: Rubrik’s SaaS platform for backup and data security. On Azure it protects VMs, managed disks, Blob, Azure SQL Database, SQL Managed Instance and PostgreSQL Flexible Server.

Best for: Security-led teams that want backup and threat analytics from one vendor across cloud and data center.

Key features:

  • Anomaly Detection on Azure backups.
  • Threat hunting across past backups to find the last clean point.
  • Cyber recovery of Azure VMs into an isolated environment.
  • Air-gapped copies in Rubrik-managed storage.

Pros:

  • Detection and investigation tooling built around recovery

Cons:

  • Rubrik added several Azure VM recovery capabilities after their AWS and on-premises versions, so confirm each is GA on Azure before you count on it
  • Copies sit in Rubrik’s storage, so Rubrik joins your audit scope

Pricing: Quote-based.

Bottom line: A fit for security teams buying a platform, not only Azure backup.

7. Cohesity

What it does: Cohesity Cloud Services (SaaS) and DataProtect back up Azure VMs. FortKnox is Cohesity’s managed vault on Azure for isolated, immutable copies.

Best for: Organizations already on Cohesity or NetBackup that want an isolated vault for Azure data.

Key features:

  • FortKnox keeps WORM copies in Cohesity-managed immutable Azure Blob storage, with quorum approval for changes.
  • Anomaly detection, threat scanning and clean room recovery in FortKnox.
  • Restores to another subscription, region or resource group.

Pros:

  • An isolated vault outside your tenant, with quorum controls

Cons:

  • Cohesity Cloud Services doesn’t make app-consistent backups of Azure VMs
  • FortKnox on Azure offers a warm tier only, with a 30-day minimum retention

Pricing: Quote-based.

Bottom line: Best as an extension of an existing Cohesity estate.

8. Druva

What it does: SaaS backup for Azure VMs, with copies stored outside your Azure tenant in Druva’s cloud.

Best for: Teams that want nothing to deploy and are comfortable with the vendor holding their backups.

Key features:

  • Threat Hunting scans past Azure VM snapshots for indicators of compromise before a restore; Threat Watch scans continuously.
  • Rollback returns encrypted or corrupted disks to a known-good state.
  • Cross-region restore.

Pros:

  • Isolation from your tenant with no infrastructure to run

Cons:

  • Cross-region restore doesn’t support VMs with customer-managed keys or Azure Disk Encryption
  • No Azure Confidential VM support

Pricing: Not published.

Bottom line: The simplest operating model, if the vendor holding your copies suits your audit scope.

Also considered: Zerto

HPE Zerto replicates Azure VMs continuously and keeps a journal of up to 30 days, so you can fail over to a point seconds before an attack. Its real-time encryption detection is not available on Azure (HPE, April 2025), so on Azure you find the clean point yourself. Licensed per VM; no published price. It’s a replication tool, so teams run it alongside a backup.

Which Azure ransomware recovery solution should you choose?

N2W is the better fit when you want backups in your own subscriptions every minute or so, an immutable copy with a second provider, and whole environments recovered in order across regions or subscriptions.

Azure Backup is the better fit when you run only Azure and a 4-hour interval is acceptable and you have a smaller environment. Lock the vault and turn on multi-user authorization either way.

Commvault or Cohesity is the better fit when you want a managed clean room or isolated vault and run an enterprise platform already.

Veeam is the better fit when Veeam Backup & Replication already runs your data center and you want scan-before-restore.

Rubrik is the better fit when the security team owns backup and wants threat hunting in the same platform.

Druva is the better fit when you want nothing to deploy and accept vendor-held copies.

Azure Site Recovery or Zerto is the better fit when fast failover is the goal. Run either alongside a backup.

Where Azure ransomware recovery goes wrong

  • Treating replication as backup. Azure Site Recovery and Zerto copy the encryption too. Once the attack is older than the journal, there’s nothing clean to fail over to.
  • Locks the attacker can remove. A resource lock or an unlocked vault holds against mistakes, not against a stolen Owner account. Lock the vault, require multi-user authorization, and keep one copy outside the tenant.
  • No clean-point plan. Scanning tools help, but someone still decides which point to restore. Know your likely dwell time and keep history that reaches past it.
  • Restoring into the compromised network. Restore into an isolated VNet or subscription first, check it, then cut over.
  • Never testing. A recovery nobody has run takes longer than the plan says. Schedule dry runs and full tests.

What this looks like in practice

Aptean, an enterprise software company, started with N2W on AWS and kept it as it expanded into Azure, adding Wasabi as off-cloud storage independent of both. “My North Star has always been security, availability, and cost,” says Ravi Reddy, Sr Director, Cloud Ops and Technology Transformation. Read Aptean’s story.

On recovery speed, the City of Oakland recovered a full environment with N2W in about 30 seconds. That was an AWS environment; on Azure, restores from snapshots take minutes, set by how fast Azure creates disks and VMs.

Frequently asked questions

Are there cloud backup services that specialize in fast ransomware recovery for Azure?

Yes. Commvault, Rubrik, Cohesity, Veeam and Druva add threat scanning and isolated recovery environments. N2W keeps backups as often as every 60 seconds in your own subscription, with a copy in Wasabi outside Azure, and recovers whole environments in order. Azure Backup’s locked immutable vaults and multi-user authorization are the native baseline.

Is Azure Site Recovery enough for ransomware recovery?

No. Site Recovery replicates changes, including encrypted ones, and its oldest usable recovery point is 15 days old. If an attacker sat in the environment longer than that, no clean replica is left. Use it for fast failover alongside a backup with longer, immutable history.

Can ransomware delete Azure backups?

It can if the attacker holds enough permissions and the copies aren’t locked. A locked immutable vault in Azure Backup can’t be reversed, and multi-user authorization stops one stolen admin account from turning protection off. Resource locks and leases can be removed by an Owner, so keep at least one copy with a different provider under separate credentials.

How often should you back up Azure VMs for ransomware recovery?

As often as the data you can afford to lose. Azure Backup’s Enhanced policy goes down to every 4 hours. Snapshot-based tools such as N2W go as low as every 60 seconds. Keep that frequent history long enough to reach back past a typical attacker dwell time.

Does Azure Backup scan backups for malware?

No. Its threat detection, in preview, marks recovery points as suspicious from Microsoft Defender for Servers alerts on the source VM, and Microsoft states it doesn’t scan the stored recovery points. Veeam, Commvault, Rubrik, Cohesity and Druva offer scanning of backup data in different forms.

How fast can you recover Azure VMs after ransomware?

It depends on where you restore from. A restore from a snapshot in your subscription takes minutes, because Azure attaches the disk right away and hydrates it in the background. Restores from a vault or archive tier take longer. Finding a clean recovery point usually takes longer than the restore itself.

What is the difference between immutable and air-gapped backups on Azure?

An immutable backup can’t be changed or deleted until its retention ends. An air-gapped backup sits where an attacker with your production credentials can’t reach it. In Azure, a locked vault or resource lock gives immutability inside the same tenant. A copy with a separate provider, such as Wasabi, adds the air gap.

You might also like