Follow a public API request from Azure Front Door to AKS
Send a simulated orders API request through Azure Front Door, Application Gateway and API Management. Change the request or the policy to see who responds and whether the request reaches the orders container.
Ready to run
Select Run request to see which service responds.
Request journey
-
Public internet
API client
GET /api/ordersReady
-
Azure global edge
Azure Front Door
Premium · edge WAF
Pending
-
UK South · Azure region
Application Gateway
Private Link origin · routes
/api/*Pending
-
Azure API Management
Private gateway · inbound policies
Pending
-
Azure Kubernetes Service
Internal load balancer · orders pod
Pending
Response path Shown after the request runs.
Lab assumptions. Front Door caching is disabled for the API route. Application Gateway handles routing only. API Management Premium (classic) runs in internal VNet mode, and an internal load balancer serves the AKS backend.
Configuration
Request trace · simulated
Run a request to see each decision.
Notes
- Global and regional ingress. Front Door Premium is the public endpoint. It uses an approved Private Link connection to an Application Gateway v2 frontend in UK South. Application Gateway forwards
/api/*to the private API Management gateway. A separately configured regional WAF can make its own decision. Match the HTTPS origin hostname and certificate to the Application Gateway listener, and configure private DNS, backend TLS and health probes for the API Management gateway. - Single-region deployment. The lab shows one regional stack in UK South behind the global Azure Front Door endpoint. For regional redundancy, a second region such as UK West could host an equivalent stack of Application Gateway, API Management and AKS. Both Application Gateways would be origins in the same Front Door origin group. With health probes and origin priorities configured for failover, Front Door can route requests to the healthy standby origin when the primary is unhealthy.
- Edge inspection. The modeled policy checks the custom Block at priority 10 and custom Allow at priority 20, before the managed Default Rule Set. In Prevention mode a matching Allow ends evaluation of the remaining custom and Default Rule Set rules. The separate HTTP DDoS ruleset, when enabled, runs before custom rules. The simulated DRS 2.0+ policy uses an anomaly threshold of 5 and a Block action. In Detection mode the request is forwarded and Azure can log matches when diagnostics are enabled. The trace shows modeled matches.
- API access. The example uses
validate-azure-ad-tokenwith its default 401 on failure, then a separate role condition usingreturn-responsefor 403.rate-limit-by-keyuses a verified client identity and returns 429 when its counter is over limit. The demo skips the counter when token validation is disabled and rejects requests if a role is required without a verified identity. - Private backend. The Kubernetes Service exposes an internal Azure load balancer and forwards to an orders pod. The topology assumes private network reachability from API Management to that Service. Authenticate the API Management-to-backend hop as appropriate.
- Find the source of a 403. For an edge decision, look up the response's
X-Azure-Refin Front Door WAF logs with diagnostics enabled. For an API decision, use an authorized API Management request trace to inspect the inbound role check.
Microsoft Learn references
- Front Door WAF evaluation and modes
- Front Door WAF custom rules and actions
- Front Door managed rules and anomaly scoring
- Front Door caching for authenticated API routes
- Connect Front Door Premium to Application Gateway using Private Link
- Application Gateway path-based routing
- Connect Application Gateway to internal API Management
- Expose an AKS Service through an internal load balancer
- Front Door WAF logging and request references
- API Management request tracing