Blog Post

Reliability and Resiliency in Azure
5 MIN READ

Azure Backup: Logically air-gapped vault and cyber recovery readiness

kirushk's avatar
kirushk
Icon for Microsoft rankMicrosoft
Nov 17, 2026

Beyond backup: Advancing cyber recovery readiness with Azure Backup

It’s 3 a.m., and your Microsoft Entra tenant has been compromised. Your admins are locked out. You have backups, but now the harder questions start: can you reach them, where do you restore, and how quickly can your critical systems come back? 

We’re hearing this from customers more often. Ransomware groups now routinely target identity and backup infrastructure together, because blocking recovery is the fastest way to force a payment. Regulations such as the EU’s Digital Operational Resilience Act (DORA) are also raising expectations. Organizations increasingly need to show that their backups are tamper-resistant and that critical workloads can be restored within a defined recovery window. 

Having a backup is no longer enough. You also need to be ready to recover. 

At Ignite 2026, we’re bringing Azure Backup’s cyber resilience capabilities together under two areas. Logically air-gapped vault protects your recovery points from being deleted, altered, or disabled during an attack. Cyber recovery readiness helps you find clean recovery points and restore them to a safe location, at scale. 

 

 

 

Cyber recovery readiness: what recovery looks like during an attack 

The 3 a.m. tenant lockout doesn't happen all at once. Attacks usually escalate in stages, and the right recovery move depends on how far the attacker got. Let's follow one from the first foothold. 

Malware in production. It starts small, with a phished credential for an account that has access to a production subscription. The attacker moves laterally and plants malware across VMs, often days or weeks before triggering it. By the time it goes off, your latest recovery point may already contain the malware, and restoring it brings the infection straight back. Threat detection uses signals from Microsoft Defender for Cloud to flag recovery points that may be affected, so your team can pick the most recent clean one instead of guessing. 

A compromised subscription. Knowing which recovery point to use is only half the problem. You also need a safe place to restore it. If the attacker still has a hold on the production subscription, or it's locked down for forensic investigation, you can't restore back into it. Cross-subscription restore lets you recover into a separate, clean subscription outside the attacker's reach while the investigation continues. 

A compromised tenant. Now the worst case, the one we started with. The attacker escalates to global administrator and takes control of your Microsoft Entra tenant. Your admins can't sign in, and every subscription in the tenant is now suspect. Any recovery plan that depends on that tenant has stopped working. With cross-tenant restore, you can restore vaulted recovery points into a separate, trusted tenant, so you can get back to business without first regaining control of the compromised one. 

Recovery at scale. Wherever you restore to, it rarely stops at one VM. When hundreds of machines need to come back, restoring them one by one isn't practical. Safe restore at-scale lets you restore many clean recovery points to an isolated environment in a single operation and track progress in one place. 

 

 

 

 

Logically air-gapped vault: Protecting your backups before an attack 

Now go back a few days, to the same attacker. Before triggering the malware, they take their time looking around your environment. They find your backup vaults, and they know that if the recovery points disappear, you'll have little choice but to negotiate. So, they go after the backups first. 

Deleting the backups. The first move is the obvious one: delete the recovery points. Soft delete catches this by keeping deleted backup data for a set period, so you can still bring it back. A careful attacker will then try to switch soft delete off. Soft delete is on by default for your vaults, and once you set it to always-on, no one can turn it off. 

Shortening retention. When deleting doesn't work, the attacker tries something quieter. They cut retention from months to a single day and let the recovery points expire on their own. Nothing is deleted, so nothing looks unusual. Locked immutability stops this. With WORM (write once, read many) immutability locked on the vault, no one can delete recovery points or shorten their retention before they expire, including admins with full permissions. Once it's locked, it stays locked. 

Turning off protections. Next, the attacker uses the compromised admin account to change the vault's security settings directly. With multi-user authorization (MUA), critical operations like reducing protection need approval through a resource guard. That approval is owned by a separate team, and it can sit in a different subscription or tenant. One stolen credential isn't enough to get the change through. 

Limiting what one account can do. Throughout all of this, the attacker can only do what the stolen account is allowed to do. When you scope backup permissions with Azure RBAC, only a small set of identities can manage vaults and backup policies, which limits how far a single compromised account can reach. Encryption with customer-managed keys gives you a further say over who can access the data. 

Keeping the data out of reach. Finally, there's the question of where the backup data actually lives. Vaulted backups are stored in Microsoft-managed storage, in a separate tenant from your production workloads. An attacker who controls your subscription can't reach that storage directly. For long-term retention, the archive tier adds another copy, kept offsite. 

By the time the attacker triggers the malware, your recovery points are still there and unchanged. That's what makes the recovery steps in the previous section possible. If you do one thing after reading this post, check that your vaults have immutability locked, soft delete set to always-on, and MUA enabled. 

 

 

 

Get started 

Cyber recovery is something you plan before an incident, not during one. To get started:

We'd love to hear how you're approaching cyber recovery. Share your feedback in the comments below. 

Updated Nov 16, 2026
Version 1.0
No CommentsBe the first to comment