About
Most resiliency tiers get assigned by gut feel, and most claims of "we're geo-redundant" go unverified until the outage that tests them. Azure Resiliency Map exists to close that gap: pick the RPO/RTO a workload actually needs, and see — service by service, sourced against current Microsoft documentation — whether the Azure architecture behind it can really deliver that, or whether the gap is architectural and not just a setting to flip.
What's here
Tier gap dashboard
Pick a resiliency tier — or set your own RPO/RTO — and see PASS/RISK/FAIL for every Azure service's redundancy options against it, at a glance.
Service catalog
Sourced RPO/RTO, failover behavior, SLA, and known gotchas for 16 Azure services, each verified against current Microsoft documentation.
Scenarios
Real architectures combine services, and a tier is only met when every component does. Four starter scenarios show the rolled-up gap, weakest link first.
Your applications
Build your own inventory of what your company actually runs and what it's configured on, evaluated against the same PASS/RISK/FAIL logic. Stored only in your browser.
Guides
How to decide a tier's RPO/RTO, where HA/DR/backup solutions each belong, and how to actually test that any of it works.
Who it's for
Architects and engineers preparing for a design review, cloud consultants building a client's gap-analysis report, and anyone who's inherited a resiliency claim they'd like to actually check before repeating it in a document. It's a starting point for that conversation, not a substitute for a formal audit or the current Azure SLA documents.
How this stays accurate
Every service entry carries a lastVerified date and its source links, and every PASS/RISK/FAIL judgment follows one explicit rule, not a vibe. See methodology for exactly how that works, and how figures get corrected when Azure changes something.