Azure Front Door
What it is
Azure Front Door is a global, HTTP(S)/Layer-7 accelerator that combines intelligent routing (to the nearest/healthiest origin) with global delivery (CDN-style caching), SSL termination at the edge, and an optional Web Application Firewall (WAF). It’s the modern standard global front-end for web applications.
Why it exists
Global web apps need to route users to the right region for both performance and availability, while caching static content at the edge and protecting against web attacks (WAF). Traffic Manager only does DNS; Load Balancer/App Gateway are regional. Front Door combines global L7 routing + CDN + WAF in one managed edge service.
Key ideas
- Front Door profile + endpoints — routes traffic to origin groups (backends) across regions with health probes and session affinity / affinity (sticky), plus global anycast routing.
- SSL/TLS termination & end-to-end at edge; path-based / host-based routing just like App Gateway but globally.
- Caching static content on Azure’s edge network (CDN component).
- WAF policy, managed rules (OWASP), rate limiting.
- Routing rules/reconfiguration with low latency (failover in seconds).
- Standard vs Premium tiers (Premium adds Private Link origin, edge rules richer).
How it fits
[users] → [Azure Front Door edge (global anycast)]
│ L7 + WAF + SSL + caching
│ latency/health-based routing
┌───────┴────────┐
[origin A region] [origin B region]
Diagrams courtesy of Microsoft Learn / Azure docs: frontdoor/front-door-overview
Exam notes
- Front Door = global L7 proxy + CDN + WAF; Traffic Manager = DNS-only global routing; App Gateway = regional L7; Load Balancer = regional L4.
- Memorize the four-way comparison (LD: L4 regional, App GW: L7 regional, Traffic Manager: DNS global, Front Door: L7 global + CDN/WAF).
- Standard vs Premium tier distinction (Premium: Private Link origins, advanced edge operations).
Related
Home · traffic-manager · application-gateway · load-balancer · azure-dns · azure-firewall
📘 Source: Microsoft Learn — Azure Front Door