Study guide
6.1 Azure Front Door Architecture & Routing
Designing and Implementing Microsoft Azure Networking Solutions AZ-700
Track your progress as you read
Finished sections get a check mark.
1 Introduction & AZ-700 Exam Overview
0.1 About the AZ-700 Exam: Format, Scoring & Skills Measured
2 Chapter 1: Azure Virtual Networks, Addressing & Subnet Architecture
1.1 VNet Planning, IP Addressing & Subnet Design 1.2 Virtual Network Peering & Global Peering 1.3 Azure NAT Gateway & Outbound Connectivity 1.4 Azure Virtual Network Manager (AVNM) & Network Groups 1.5 Public IP Addresses, Public IP Prefixes & Custom IP Prefixes (BYOIP)
3 Chapter 2: Azure Name Resolution & Core Routing
2.1 Azure DNS & Private DNS Zones 2.2 Azure Private DNS Resolver & Hybrid Name Resolution 2.3 System Routes & User-Defined Routes (UDR) 2.4 BGP & Custom Route Propagation 2.5 Azure Route Server & Dynamic NVA Route Exchange
4 Chapter 3: Hybrid Connectivity with Azure VPN Gateway
3.1 Azure VPN Gateway Architecture & SKUs 3.2 Site-to-Site (S2S) VPN & High Availability 3.3 Point-to-Site (P2S) VPN & Client Authentication 3.4 Azure Extended Network, Always On VPN & Azure Network Adapter
5 Chapter 4: Azure ExpressRoute & Virtual WAN
4.1 Azure ExpressRoute Architecture & Peering Models 4.2 ExpressRoute Routing, Resiliency & Global Reach 4.3 Azure Virtual WAN Architecture & Hub Routing 4.4 ExpressRoute BFD, Monitoring & Connection Troubleshooting
6 Chapter 5: Regional Load Balancing & Application Gateway
5.1 Azure Load Balancer Architecture & Rules 5.2 Azure Application Gateway Architecture & Routing 5.3 Web Application Firewall (WAF) on Application Gateway 5.4 Inbound NAT Rules, Port Forwarding & Health Probe Design
7 Chapter 6: Global Traffic Management & Azure Front Door
6.1 Azure Front Door Architecture & Routing 6.2 Azure Traffic Manager & DNS Load Balancing 6.3 Load Balancing Decision Matrix & Multi-Tier Design 6.4 Web Application Firewall on Azure Front Door
8 Chapter 7: Azure Private Link & Service Endpoints
7.1 Virtual Network Service Endpoints & Policies 7.2 Azure Private Endpoints & Private Link Architecture 7.3 Private Endpoint DNS Integration & Hybrid Resolution 7.4 Azure Private Link Service for Multi-Tenant Solutions
9 Chapter 8: Network Security Groups & Azure Bastion
8.1 Network Security Groups (NSGs) & Application Security Groups (ASGs) 8.2 Azure Bastion Architecture & Secure Remote Access 8.3 Azure Virtual Network Manager Security Admin Rules
10 Chapter 9: Azure Firewall & Security Policies
9.1 Azure Firewall Architecture & Rule Processing 9.2 Azure Firewall Manager & DDoS Protection
11 Chapter 10: Azure Network Observability & Troubleshooting
10.1 Network Watcher Diagnostic Tools 10.2 NSG Flow Logs, VNet Flow Logs & Traffic Analytics 10.3 Network Troubleshooting Scenarios & End-to-End Connectivity 10.4 Azure Monitor Network Insights & Defender for Cloud Network Posture
6.1 Azure Front Door Architecture & Routing
Key Takeaways Explain This Topic AI
Azure Front Door is a global Layer 7 reverse proxy and content delivery network (CDN) operating across hundreds of global Points of Presence (PoPs) using Anycast routing and Split TCP to accelerate HTTP/HTTPS application delivery.
Front Door Standard SKU provides dynamic content acceleration, global load balancing, and basic custom WAF rules; Front Door Premium SKU adds managed OWASP core rule sets, Microsoft Threat Intelligence Bot Protection, and secure Private Link connectivity to origin backends without public IPs.
The core Front Door resource model comprises Endpoints (*.azurefd.net), Routes (matching domains, patterns, and HTTP methods), Origin Groups (defining origin sets, health probes, and load balancing algorithms), and Origins (specifying FQDNs/IPs and Private Link integration).
Health probes evaluate origin availability via configurable HTTP HEAD or GET requests; routing decisions consider probe health, priority numbers (active vs standby), weight (traffic splitting), and latency sensitivity (sample window in milliseconds).
Front Door supports seamless SSL offloading, end-to-end TLS 1.2/1.3, automated free Azure-managed certificate renewal with DNS validation, and advanced URL routing including 301/302/307/308 redirects and internal URL rewrites.
Last updated: August 2026
Azure Front Door Architecture & Routing
Modern cloud-native applications serve globally distributed user bases where performance, availability, and edge security are critical. Azure Front Door (AFD) is Microsoft's global, scalable entry point that combines Layer 7 reverse proxying, content delivery network (CDN) caching, dynamic traffic acceleration, and Web Application Firewall (WAF) capabilities into a unified software-defined platform.
Front Door operates at the edge of Microsoft's global network, which consists of hundreds of Points of Presence (PoPs) distributed worldwide. By terminating client TCP/TLS connections at the closest edge PoP using BGP Anycast , Front Door drastically reduces round-trip times (RTT) and shields origin infrastructure from direct internet exposure.
1. Global Anycast Architecture & Split TCP
Traditional DNS-based load balancing routes users directly to a regional origin IP address. If a user in London connects to a backend hosted in East US (Virginia), the three-way TCP handshake and multi-step TLS 1.3 handshake must traverse the entire trans-Atlantic public internet, incurring high latency, packet loss, and jitter. +-----------------------------------------------------------------------------+
- | TRADITIONAL ROUTING VS. SPLIT TCP (AFD) |
- | |
- | TRADITIONAL DIRECT ROUTING: |
- | [Client: London] ====( High Latency WAN Handshake across Internet )====> [Origin: East US]
- | - Latency: 3x-4x trans-Atlantic RTT (~300ms) before first byte sent |
- | |
- | AZURE FRONT DOOR WITH SPLIT TCP: |
- | [Client: London] ==( Rapid Local Handshake < 5ms )==> [AFD Edge PoP: London]
- | | |
- | (Pre-warmed Pooled) |
- | (Connections over ) |
- | (Microsoft WAN ) |
- | v |
- | [Origin: East US] |
- +-----------------------------------------------------------------------------+
How Anycast and Split TCP Accelerate Traffic:
Anycast IP Advertising: All Front Door edge PoPs advertise the exact same public IPv4 and IPv6 Anycast address prefixes via BGP. Client DNS lookups for an Azure Front Door hostname resolve to this Anycast VIP, and internet routers automatically steer the client packets to the topologically closest edge PoP.
Split TCP Connection Termination: The client establishes a short-haul TCP connection and completes the TLS handshake directly with the local edge PoP. This local handshake completes within milliseconds.
Pre-Warmed Connection Pooling: The edge PoP maintains pre-established, warmed TCP/TLS connection pools across the ultra-low-latency Microsoft Global Backbone to the origin servers. Data is transported across Microsoft's private dark fiber, bypassing public internet congestion and packet loss.
SSL Offloading: Front Door decrypts client HTTPS traffic at the edge PoP, inspects payloads for security threats via WAF, applies routing rules and URL rewrites, and forwards requests to the origin over HTTP or re-encrypted HTTPS.
Loading diagram... Azure Front Door Anycast Edge and Microsoft Global Backbone Architecture
2. Standard vs. Premium SKU Comparison
Azure Front Door is offered in two production tiers: Standard and Premium . Both tiers share the same core Layer 7 Anycast routing fabric, dynamic site acceleration, and custom domain management, but differ substantially in security controls, Private Link origin connectivity, and enterprise rules engine limits.
Architectural Feature Front Door Standard SKU Front Door Premium SKU
Core Routing & CDN Layer 7 Anycast, dynamic routing, SSL offload, caching Layer 7 Anycast, dynamic routing, SSL offload, caching
WAF Capabilities Custom WAF rules and Rate Limiting only Managed OWASP Core Rule Sets (CRS 3.2+), Custom Rules, Rate Limiting
Bot Protection Not supported Microsoft Threat Intelligence Bot Protection (good bots vs malicious bots)
Backend Origin Security Public IPs, public FQDNs, or IP allowlisting only Azure Private Link integration to origins (no public IP required on origins)
Analytics & Reports Built-in traffic and health-probe reports, access logs, WAF logs Same reports plus the WAF security report (managed-rule match breakdown, bot traffic patterns)
Rules Engine Available on both tiers, with server variables and regular-expression support Identical rules-engine capability; the tier difference is security, not rule quotas
Target Workload Profile Content-heavy web apps, basic API routing, small/medium business Enterprise multi-tier apps, regulated finance/healthcare, zero-trust private origins
Important
Exam Tip: Private Link Origin Reachability: If an exam scenario requires connecting Front Door to backend App Services, Internal Load Balancers (ILB), or Storage Accounts that have no public endpoints and no internet ingress , you must select Azure Front Door Premium . Standard SKU cannot initiate Private Link connections to origins.
3. Core Resource Hierarchy & Routing Engine
Configuring Azure Front Door involves creating a structured resource hierarchy that defines how traffic enters the edge, how it is processed, and where it is dispatched. +-----------------------------------------------------------------------------+
- | AZURE FRONT DOOR RESOURCE HIERARCHY |
- | |
- | +---------------------------------------------------------------------+ |
- | | Front Door Profile (Standard or Premium SKU) | |
- | | | |
- | | +-------------------------------------------------------------+ | |
- | | | Front Door Endpoint (e.g., app-prod-xyz.azurefd.net) | | |
- | | | - Custom Domains: www.contoso.com, api.contoso.com | | |
- | | +-------------------------------------------------------------+ | |
- | | | | |
- | | v | |
- | | +-------------------------------------------------------------+ | |
- | | | Routing Rules | | |
- | | | - Match: Domain + Path Pattern (/api/*, /images/*, /*) | | |
- | | | - Action: Forward to Origin Group, Redirect, or Rewrite | | |
- | | | - Attachments: Rules Engine Sets, Caching Configurations | | |
- | | +-------------------------------------------------------------+ | |
- | | | | |
- | | v | |
- | | +-------------------------------------------------------------+ | |
- | | | Origin Group (Logical grouping of backend endpoints) | | |
- | | | - Health Probe Settings (Protocol, Interval, Method) | | |
- | | | - Load Balancing Settings (Sample Size, Latency Sensitivity)| | |
- | | | - Session Affinity (Cookie-based routing) | | |
- | | +-------------------------------------------------------------+ | |
- | | | | | |
- | | v v | |
- | | +-------------------+ +-------------------+ | |
- | | | Origin 1 (East US)| | Origin 2 (W Europe)| | |
- | | | Host: app1.azure..| | Host: app2.azure..| | |
- | | | Priority: 1 | | Priority: 2 (Fail)| | |
- | | | Weight: 50 | | Weight: 50 | | |
- | | | Private Link: Yes | | Private Link: Yes | | |
- | | +-------------------+ +-------------------+ | |
- | +---------------------------------------------------------------------+ |
- +-----------------------------------------------------------------------------+
- Health Probes and Traffic Routing Algorithms
When Front Door processes an incoming request matched by a routing rule, it selects the target origin within the designated Origin Group using a multi-step evaluation algorithm:
Health Probe Evaluation:
Front Door sends synthetic health probes from multiple edge locations to each origin.
Probe Protocols: HTTP or HTTPS.
Probe Methods: HEAD (recommended to save bandwidth) or GET .
Probe Interval: Frequency of probe transmissions (e.g., every 30 seconds, or down to 5 seconds for critical backends).
Health Evaluation Window: Defined by two parameters: Sample Size (e.g., 4 probe samples) and Successful Samples Required (e.g., 3 successful HTTP 200 responses). If 3 out of 4 probes succeed, the origin is considered healthy.
Priority-Based Filtering:
Each origin is assigned an integer Priority (e.g., 1 for primary, 2 for standby/failover).
Front Door filters the origin pool to only include healthy origins that have the lowest priority number (Priority 1).
If all Priority 1 origins become unhealthy, Front Door automatically fails over to healthy Priority 2 origins.
Latency Sensitivity Filtering:
Among the healthy, lowest-priority origins, Front Door measures the network latency from the specific edge PoP processing the request.
Front Door defines a Latency Sensitivity (Additional Acceptable Latency Window) in milliseconds (default: 0 ms; commonly set to 15–50 ms).
If Origin A has 10 ms latency and Origin B has 25 ms latency, and Latency Sensitivity is set to 20 ms, both origins fall within the acceptable latency band (10 ms + 20 ms = 30 ms maximum) and will receive traffic.
Weighted Round-Robin Distribution:
Among all origins that survive the priority and latency filters, traffic is distributed proportionally according to their assigned integer Weight (1–1000).
4. Dynamic Site Acceleration (DSA), Caching & Compression
Front Door provides native CDN capabilities, allowing organizations to accelerate dynamic content while offloading static file delivery.
Dynamic Site Acceleration (DSA)
For dynamic, non-cacheable API calls and database-driven web pages, Front Door utilizes DSA techniques:
Route Optimization: Real-time BGP routing telemetry identifies the fastest network path across the Microsoft backbone.
TCP Parameter Tuning: Window scaling, initial congestion window size optimization, and selective acknowledgments (SACK).
TLS Session Resumption: Reusing cryptographic parameters to avoid redundant TLS handshakes.
Caching Behaviors & Query String Configurations
When caching is enabled on a routing rule, Front Door inspects incoming requests against its edge cache before forwarding to origins: +-----------------------------------------------------------------------------+
- | FRONT DOOR QUERY STRING CACHING MODES |
- | |
- | Mode Incoming Request Cached As |
- | ----------------------- --------------------------- --------------- |
- | Ignore Query String /catalog/item?color=blue /catalog/item |
- | (Returns same cached /catalog/item?color=red /catalog/item |
- | object for all params) |
- | |
- | Cache Every Unique URL /catalog/item?color=blue /catalog/item?b.. |
- | (Each parameter variant /catalog/item?color=red /catalog/item?r.. |
- | cached separately) |
- | |
- | Use Query String (Custom caching based on specific designated |
- | (Selective parameters) query string keys while ignoring others) |
- +-----------------------------------------------------------------------------+
Cache Purging and Compression:
Cache Purge: When backend content updates, administrators can trigger an on-demand cache purge via the Azure Portal, Azure CLI ( az afd endpoint purge-content ), or REST API. Purge paths can be explicit ( /images/logo.png ) or wildcard-based ( /images/* ).
Dynamic Compression: Front Door can compress content at the edge using Gzip or Brotli before delivering it to the client, even if the origin served uncompressed responses. Content types (MIME types) eligible for compression are customizable (e.g., text/html , application/json , text/css ).
5. URL Redirection vs. URL Rewriting
A critical requirement on the AZ-700 exam is distinguishing between URL Redirection and URL Rewriting within Front Door routing rules.
Dimension URL Redirection URL Rewriting
Client Visibility Visible: Client receives an HTTP 3xx status code and initiates a new request to the target URL. Invisible (Internal): Front Door modifies the request path before forwarding to origin; client URL stays unchanged.
HTTP Status Code 301 (Moved Permanently), 302 (Found), 307 (Temporary Redirect), or 308 (Permanent Redirect). None (200 OK / direct backend response).
Typical Use Case Enforcing HTTP to HTTPS redirection, moving legacy domains ( old.com -> new.com ). Directing /api/v2/products to an internal backend directory /microservices/catalog .
Origin Interaction Edge PoP immediately responds to client; no traffic touches the origin . Edge PoP rewrites request path and forwards payload to backend origin.
Host Header Behavior Changes client browser address bar to new destination host. Can preserve incoming client host header or override with origin FQDN.
Tip
Host Header Preservation vs. Override: When forwarding traffic to multi-tenant PaaS origins (such as Azure App Service or Azure Functions), the backend requires the HTTP Host header to match its default service FQDN (e.g., app-backend.azurewebsites.net ), unless a custom domain is explicitly bound in the App Service. Front Door allows configuring the Origin Host Header override per origin.
6. Custom Domains, DNS Validation & End-to-End TLS
Deploying enterprise applications on Azure Front Door requires mapping vanity custom domains (e.g., www.contoso.com or root apex contoso.com ) and securing communication with TLS. +-----------------------------------------------------------------------------+
- | CUSTOM DOMAIN VALIDATION WORKFLOW |
- | |
- | 1. Admin adds Custom Domain 'www.contoso.com' in Azure Front Door |
- | 2. AFD generates TXT Validation Token: _dnsauth.www.contoso.com |
- | 3. Admin creates DNS TXT Record in public DNS registrar / Azure DNS |
- | 4. AFD auto-validates ownership and provisions TLS Certificate |
- | 5. Admin creates CNAME (or Azure DNS Alias Record for Root Apex) |
- | pointing 'www.contoso.com' -> 'app-endpoint.azurefd.net' |
- | 6. Domain state transitions to 'Approved' and 'Deployed' |
- +-----------------------------------------------------------------------------+
- Custom Domain Validation and Apex Support
Validation via DNS TXT Record: To prove ownership of a domain before shifting production traffic, Front Door generates a unique validation token. You create a _dnsauth.<subdomain> TXT record in your DNS zone.
CNAME Mapping for Subdomains: For standard subdomains (e.g., portal.contoso.com ), create a DNS CNAME record pointing to the Front Door endpoint ( <endpoint-name>.azurefd.net ).
Root Apex Domain Support ( contoso.com ): Standard DNS specifications (RFC 1034/1035) prohibit CNAME records at the zone apex ( @ ). To host a root domain on Front Door, you must host your DNS zone in Azure DNS and create an Alias record pointing directly to the Front Door profile resource.
TLS Certificate Management Models
Front Door enforces TLS 1.2 or TLS 1.3 and offers two certificate management models:
Azure-Managed Certificate: Microsoft automatically provisions, validates, and rotates the SSL/TLS certificate at zero additional cost using DigiCert. Rotation occurs automatically ~45 days before certificate expiration.
Bring Your Own Certificate (BYOC) with Azure Key Vault: Organizations upload their private certificate (PFX) to an Azure Key Vault. Front Door accesses the Key Vault via a managed identity or service principal. When the certificate is updated in Key Vault, Front Door automatically detects the new version and deploys it across all global PoPs within 24 hours.
End-to-End TLS Security
For strict regulatory compliance, Front Door supports End-to-End TLS :
Frontend TLS: Secures communication between client browsers and the edge PoP.
Backend TLS: Front Door establishes a new, dedicated TLS session from the edge PoP to the backend origin. The origin certificate must be issued by a trusted public Certificate Authority (CA) and contain a Common Name (CN) or Subject Alternative Name (SAN) matching the origin host header.