Whats up People
If in case you have ever stared at a multi-tier app in Azure and requested your self, “Is that this truly going to outlive a zone outage?”, you aren’t alone. In session MAIS23 of the Microsoft Azure Infra Summit 2026, Bhavya, Aditya, and Chaya from the Azure Resiliency product staff walked us by means of the brand new Resiliency in Azure experiences (previously Azure Enterprise Continuity Middle) and confirmed the way to cease treating resiliency as a per-resource checkbox and begin treating it as an application-level final result.
Most of us have lived this story. An app is “within the cloud”, unfold throughout IaaS VMs, PaaS databases, an app service plan, and a shared Azure Firewall managed by another staff. Then a zonal blip hits, and instantly no person can reply the straightforward query: was this app alleged to be zone resilient or not?
The session opened with a buyer state of affairs known as Zava, a fast-growing insurance coverage firm working a claims app at 99.9 p.c availability that simply misplaced greater than $40,000 in income in a single week due to zonal outages. That’s the price ticket the audio system placed on the issue, and it strains up with the patterns I see each week.
Right here is why this issues to IT execs:
- You lastly get a single pane to see zonal resiliency posture throughout IaaS, PaaS, and shared providers.
- Resiliency objectives are set on the software degree, not buried inside every useful resource blade.
- You get tailor-made Azure Advisor suggestions plus an Azure Copilot guided circulate that emits remediation scripts.
- You’ll be able to run zone-down drills powered by Azure Chaos Studio with out stitching collectively 5 totally different instruments.
- Restoration plans orchestrate failover in an outlined order, with on-demand readiness checks earlier than the following actual outage.
In brief, much less guessing, much less spreadsheet bookkeeping, and much more confidence that the app will behave the best way you advised the enterprise it might.
The staff has rebranded Azure Enterprise Continuity Middle to Resiliency in Azure. It’s a unified resolution that covers infra, knowledge, and cyber resiliency in a single place. Immediately the main focus is zonal resiliency, with regional catastrophe restoration (and correct RPO/RTO objectives) on the roadmap.
The central idea is the service group. A service group is a logical software unit that may span subscriptions and useful resource teams. You add the VMs, databases, app service plans, Redis caches, and different Azure assets that make up an software, and from that time on, resiliency operations work in opposition to the entire app, not one useful resource at a time.
There are two views you’ll spend most of your time in:
- Useful resource resiliency, a zonal configuration abstract throughout the (roughly 20) useful resource varieties supported in the present day.
- Service group resiliency, the identical abstract however pivoted to the appliance degree, so you may prioritize the apps that want consideration first.
The audio system had been trustworthy about scope. Targets in the present day are a easy intent (“this service group needs to be evaluated for zonal resilience”). As soon as further pillars like regional DR ship, objectives will increase to incorporate RPO and RTO targets. I recognize that they didn’t oversell it.
As soon as a service group exists, the workflow has three huge constructing blocks. Every one solves an issue I wager you have got hit.
- Targets and suggestions. You assign a zonal resiliency purpose to the service group, and Azure Advisor surfaces tailor-made suggestions for the assets inside it. Two particulars I preferred:
- The view exhibits value implications earlier than you flip the change. Some Azure providers haven’t any value delta for zone redundancy. Others do. You see it inline, not in a separate calculator tab.
- There’s an Azure Copilot guided remediation circulate that walks you thru the advice and, on the finish, emits a script. That script accounts for resource-type nook circumstances (SKU adjustments, redeploys, and so forth) and is supposed to be run by means of your automation pipeline.
You can too exclude a useful resource with a cause (“not important, zonal redundancy not required”) or manually attest a useful resource when your personal customized resolution already offers resiliency that the platform can’t auto-detect. That escape hatch is vital, as a result of actual environments at all times have a number of bizarre circumstances.
- Utility-centric restoration plans. As an alternative of failing over one useful resource at a time, a restoration plan orchestrates the whole app. It auto-detects current options (Azure Web site Restoration for VMs, for instance), helps you to group and order the assets for failover, and excludes assets which are already configured for prime availability (no level failing them over if they didn’t go down). You’ll be able to run an on-demand readiness verify any time the app construction adjustments, so you discover configuration drift earlier than an outage finds it for you.
- Zone-down drills powered by Azure Chaos Studio. A zone-down drill template identifies the service group assets, pre-populates the precise native faults per useful resource kind (suppose a Redis cache fault, a VM scale set shutdown, and so forth), bundles in identification and permission checks, monitoring, and the restoration plan you already constructed. Once you execute, you decide the area and the goal zone, the drill runs a pre-validation verify, injects the fault, runs failover, then reprotection and failback, and tracks all of it as a single job within the execution report. Per-resource metrics allow you to visualize the precise downtime every part skilled. If a local fault will not be what you need, you may override with a customized runbook.
That final level is the half I feel a whole lot of of us miss. A drill is not only fault injection. It’s fault injection plus failover plus reprotection plus failback, all measured and attestable in a single place.
Again to Zava. They wanted to reply three questions: what’s our present zonal resiliency posture throughout these Azure providers, what ought to we prioritize in opposition to our 99.9 p.c goal, and the way will we validate that we are going to truly carry out throughout an outage? Resiliency in Azure solutions all three with out forcing the platform staff to write down a 200-line PowerShell script.
Use circumstances that needs to be in your shortlist:
- Regulated workloads (insurance coverage, healthcare, monetary providers) that must proof drills for compliance. The notes and handbook attestation options had been clearly designed with auditors in thoughts.
- Apps with combined estates, the place a central platform staff owns shared providers (firewalls, identification) and app groups personal every thing else. Service teams will be parented to reflect that org construction.
- Apps with customized resiliency options that the platform can’t detect. Guide attestation retains the dashboard trustworthy with out forcing you to refactor.
- Recreation-day rehearsals. The pre-built zone-down template means you may run a significant drill in a day as an alternative of standing up a customized Chaos Studio experiment from scratch.
The trustworthy tradeoff: zone redundancy will not be free for each service, and never each useful resource kind is in scope but (round 20 in the present day). Plan accordingly, exclude what will not be important, and attest what is roofed by one thing else.
Right here is the trail I’d tackle a Monday morning:
- Open the Azure portal and seek for Resiliency. You’ll land on the Resiliency in Azure web page that replaces the outdated Enterprise Continuity Middle.
- Create a service group. Add assets instantly, or add useful resource teams if every useful resource group is already an software boundary in your setting.
- Assign the zonal resiliency purpose to the service group.
- Assessment the abstract tiles. Exclude or manually attest the assets that want it.
- Stroll the Advisor suggestions. Use the Copilot guided circulate to generate a remediation script and run it by means of your automation.
- Construct an application-centric restoration plan, group and order the assets, run an on-demand readiness verify.
- Create a zone-down drill from the template, validate identification, monitoring, and faults, then execute the drill in a non-production zone first.
Catch the total Microsoft Azure Infra Summit 2026 session playlist right here: https://www.youtube.com/playlist?checklist=PLjt5SKzX1iI8con7FJDB56G6hHqxGm7ki
Cheers!
Pierre Roman
