Skip to content

Commit 044d7f4

Browse files
Update articles/frontdoor/high-availability.md
Co-authored-by: John Downs <[email protected]>
1 parent 8b1ab03 commit 044d7f4

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

articles/frontdoor/high-availability.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.date: 01/23/2026
1515

1616
Azure Front Door is designed to provide exceptional resiliency and availability for both external customers and Microsoft's internal properties. While Front Door's architecture meets or exceeds the needs of most production workloads, it's important to acknowledge that no distributed system is immune to failure.
1717

18-
This article provides high‑level, step‑by‑step instructions for implementing Azure Traffic Manager to enable manual failover from Front Door to either an alternate CDN or Application Gateway WAF during rare Front Door service interruptions. It supplements the guidance in [Global routing redundancy for mission-critical web applications](/azure/architecture/guide/networking/global-web-applications/overview?tabs=cli).
18+
This article provides high‑level, step‑by‑step instructions for implementing Azure Traffic Manager to enable manual failover from Front Door to either an alternate CDN or Application Gateway WAF during rare Front Door service interruptions. It supplements the guidance in [Global routing redundancy for mission-critical web applications](/azure/architecture/guide/networking/global-web-applications/overview).
1919

2020
Multiple strategies exist within the industry for achieving high availability (HA) in CDN and web application architectures. The approach outlined in this article focuses on a straightforward, manual **“break‑glass” failover pattern** that allows customers to quickly redirect traffic during an outage and seamlessly restore routing back to Front Door once service health is confirmed.
2121

0 commit comments

Comments
 (0)