Blog Post

Reliability and Resiliency in Azure
6 MIN READ

Beyond availability zones - Building resilience across regions with Azure

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

When the whole region goes dark: Rethinking business continuity on Azure

Picture a team that did everything right. Their app runs across availability zones, so when a datacenter goes down, customers barely notice. Then leadership asks a bigger question: what happens if we lose the entire region? Where do we recover, will the services we depend on be there, and is our data even allowed to live in that location? 

That question is coming up in more planning meetings. Zone resilience handles failures inside a region, but continuity plans now have to account for losing a much larger footprint, keeping critical data protected, and deciding exactly where that data and recovery capacity sit. 

The answer isn’t as simple as copying everything to a second region. Azure regions don’t all offer the same services, infrastructure, or capacity, so a recovery site that fits one application perfectly can fall short for another. Add data residency, sovereignty rules, and industry regulations, and choosing where to recover becomes a business decision, not just a technical one. 

That’s why business continuity is moving away from fixed region pairs and toward choice. Teams want to decide where each application recovers, where its protected data lives, and how that plan adapts as the business changes. Surviving an outage is the baseline. The real goal is recovering in the right place, with the infrastructure, data, and dependencies ready when you need them.  

At Microsoft Ignite 2026, we’re turning that shift into something you can use. Azure Infrastructure Resiliency Manager is now generally available for zonal resiliency, and we’re starting to bring the same application-first approach to regional resiliency. Azure Backup is moving in the same direction with new region of choice capabilities, so you decide where your recovery data lives and can move it as your business needs change. Together, they move the conversation from simply surviving failures to recovering on your terms.

The foundation: make applications resilient within a region 

The journey starts with the most immediate failure domain: the availability zone. 

With Azure Infrastructure Resiliency Manager, we have been working to make zonal resiliency an application-centric and continuous practice rather than a one-time architecture exercise. 

Customers can automatically discover application boundaries and dependencies, define their applications and resiliency goals, understand their posture, identify gaps, receive recommendations, and validate readiness. Instead of evaluating every Azure resource independently, teams can begin with the business intent of the application: What is critical? What failure should it withstand? And are we actually configured to meet that objective? 

At Ignite, this zonal resiliency experience reaches general availability. That milestone matters because zonal resilience establishes the foundation for a larger idea: the experience customers use to understand and improve resilience shouldn't stop at the boundary of an availability zone. 

From zonal resilience to regional resilience 

For many critical applications, surviving the loss of a zone is only one part of the resilience strategy. Customers also need to ask a harder question: What happens if my application needs to recover in another Azure region? Traditionally, regional disaster recovery has often been approached by resources. Azure Site Recovery provides a proven foundation for cross-region protection and failover of virtual machines. But modern applications rarely consist only of VMs. They span stateful services, stateless components, databases, networking dependencies, and global services. 

At Ignite, we are extending the application-centric model established with zonal resiliency into a new regional resiliency experience in Azure Infrastructure Resiliency Manager, launching in gated preview. We’re starting with 15 services where customers have consistently expressed strong demand for regional resiliency, spanning stateful, stateless, and global services. Azure services provide foundational capabilities for cross-region resiliency. Azure Infrastructure Resiliency Manager brings these capabilities into a unified experience, simplifying how customers configure, manage, and orchestrate resiliency across their critical applications. 

The principle remains the same: start with the application and its business objectives. Customers can define regional resiliency goals such as recovery point objective (RPO), recovery time objective (RTO) and service level objective (SLO), evaluate whether their application is prepared to meet those goals, identify resiliency gaps, and receive contextual recommendations.  

 

 

 

 

 

 

 

The experience also extends into drills and recovery orchestration so that regional resilience becomes something organizations can continuously evaluate and validate, rather than something discovered for the first time during an outage.  You can use the template that we provide or bring your own custom faults too.  

 

 

 

 

 

 

To try the experience hands-on, sign up for Regional Resiliency Preview.  

As resiliency expands across zones and regions, customers also need a simple way to answer an important question: Are my applications actually prepared for the failures I am designing for? Resiliency experience helps turn resiliency posture into tangible evidence. Instead of looking at individual resource configurations, customers can understand resilient and non-resilient resources in a consolidated view, review gaps and recommendations. Just as importantly, we are bringing these signals together. Rather than forcing customers to navigate separate experiences for availability-zone resilience, regional recovery, and data protection, our direction is toward converged application and resource views across zonal resiliency, regional resiliency, and data resiliency using backups.  

 

 

 

 

 

 

This gives customers a more connected picture of resilience: how an application is protected within its primary region, how it is prepared to recover across regions, and how its data is protected for recovery. This is an important evolution. The failure boundary changes, but the customer experience should remain connected. 

Regional resilience is also about choice 

Preparing an application to recover across regions raises another increasingly important question: 

Which region should hold my recovery data? 

For many organizations, that answer is shaped by much more than physical distance. Data residency requirements, regulatory policies, sovereignty considerations, geopolitical risk, and organizational recovery strategies can all influence where a secondary copy of data should live. 

Historically, geo-redundant backup strategies have often relied on Azure-defined regional pairings. That remains valuable for many customers, but increasingly organizations want greater control over the geography of their resilience strategy. 

With Region of choice for Azure Backup, now in preview, we are beginning to give customers greater flexibility to select a secondary Azure region based on their business and regulatory requirements rather than relying solely on predefined regional pairs. This is a subtle but important shift from Azure-defined recovery placement toward customer-defined recovery placement. 

 

Organizations can align the location of their protected backup data more closely with their own requirements around residency, regulation, risk, and business continuity. As regional architectures evolve, the recovery destination itself becomes part of the resiliency design. 

But choice alone isn't enough. Data needs mobility. 

Choosing a different destination solves the problem of new protection. But what happens when an organization's requirements change? 

A customer may already have years of recovery points in one region when a regulatory requirement, organizational strategy, or risk model changes. Simply placing future recovery points somewhere else can leave protection fragmented across locations. 

That is where cross-region data mobility becomes an important part of the region of choice story. Azure Backup is bringing capabilities that enable existing recovery points to move across regions and vaults, helping customers adapt their protection strategy as their requirements evolve. 

Think about the progression: Choose where recovery data should live. Protect data in that region. Move existing recovery points when requirements change. Recover from the location that aligns with the organization's strategy. 

Region of choice therefore becomes more than a destination selector. Combined with data mobility, it starts to establish a more flexible foundation for cross-region data resilience. 

To try the experience hands-on, sign up for Region of Choice Preview. 

One resilience journey, across multiple failure boundaries 

Taken individually, each of these capabilities solves a different customer problem. But the more important story is how they fit together. An application's resilience strategy should not be defined by individual Azure constructs. It should be defined by the business outcomes the application needs to achieve. 

For one workload, surviving a zone failure may be sufficient. For another, a regional outage may need to trigger recovery of the critical application stack in another Azure region. For regulated or geographically distributed organizations, the strategy may also specify exactly where recovery data must reside. And those requirements may change over time. Our goal is to make these decisions part of a connected resilience lifecycle rather than separate infrastructure exercises. 

That is the direction we're building towards Resiliency in Azure. 

Resources 

  1. Learn more about Azure Infrastructure Resiliency Manager 
  1. Learn more about Resiliency Agent 
  1. Blog on Azure Infrastructure Resiliency Manager General Availability 
  1. To try the experience hands-on, sign up for Region of Choice Preview. 
  1. To try the experience hands-on, sign up for Regional Resiliency Preview. 

 

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