Skip to content

Commit 6708f18

Browse files
Update articles/frontdoor/high-availability.md
Co-authored-by: John Downs <[email protected]>
1 parent 9faa0f0 commit 6708f18

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
@@ -84,7 +84,7 @@ This DNS-based load balancing solution uses multiple Azure Traffic Manager profi
8484
It's important to understand the feature differences between Front Door and Application Gateway WAF in case you're utilizing any features Application Gateway WAF doesn't offer. The following two tables provide an overview.
8585

8686
> [!IMPORTANT]
87-
> This solution assumes you are currently using Azure Front Door to serve traffic across multiple regions or globally. In this design, the steps below introduce a **secondary Azure Traffic Manager configured with Performance routing between the primary Traffic Manager and regional Application Gateway instances**. This approach is necessary because Azure Front Door is a global Layer‑7 service, so the secondary Traffic Manager effectively replaces Front Door's global latency‑based routing by acting as the global load‑balancing layer. As a result, **Traffic Manager preserves latency‑optimized user routing for a geographically distributed audience**. Given this architectural shift, **you must evaluate global traffic patterns and delploy Application Gateway instances in regions that have meaningful user volume to ensure optimal performance and resilience**.
87+
> This solution assumes you are currently using Azure Front Door to serve traffic across multiple regions or globally. In this design, the steps below introduce a **secondary Azure Traffic Manager configured with Performance routing between the primary Traffic Manager and regional Application Gateway instances**. This approach is necessary because Azure Front Door is a global Layer‑7 service, so the secondary Traffic Manager effectively replaces Front Door's global latency‑based routing by acting as the global load‑balancing layer. As a result, **Traffic Manager preserves latency‑optimized user routing for a geographically distributed audience**. Given this architectural shift, **you must evaluate global traffic patterns and deploy Application Gateway instances in regions that have meaningful user volume to ensure optimal performance and resilience**.
8888
8989
#### Features differences
9090

0 commit comments

Comments
 (0)