Azure Front Door
- Free allowance
- No free tier for the L4 question: Front Door terminates SSL at the edge and only supports HTTP/1.1 from the edge to the origin.
- Verdict
- fails: egressdata cannot be read back out at a usable rate or price
- Cost
- no price statedsee Price below
- Identity
- cardcard required, no phone
- Binding limit
- write-gatedthe origin leg is HTTP/1.1 only; there is no protocol field that accepts UDP
- Evidence
- inferred2 sources; reasoned from other evidence
- Freshness
- stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23
| Free tier | No free tier for the L4 question: Front Door terminates SSL at the edge and only supports HTTP/1.1 from the edge to the origin. unit none; metered on none |
|---|---|
| Price | unverified (base and data rates not read) |
| Limits |
|
| Binding | write-gated Volume never becomes the question: the service cannot forward UDP at any tier, so 1 TiB/month of UDP has no path through it. |
| Identity | card An Azure subscription with billing enabled. |
| Egress | No UDP allowance exists. The product is billed per request and per GB of HTTP(S) delivery, with no L4 forwarding at any price.; ingress: http-only free allowance: none published |
| Interface | rest, cli profiles, endpoints, routes and origin groups over HTTP and HTTPS |
| Tooling | Azure portal, CLI or ARM/Bicep |
| Composes with | chains with HTTP origins only; it cannot expose a WireGuard or game UDP endpoint |
| Reliability | none recorded |
| Notes | Every capability on the overview page is HTTP: caching, SSL offload, HTTP/2, rules engine. No L4 listener exists in the model. |
| Evidence note | inferred No Front Door page read states a UDP forwarding feature, and the origin leg is documented as HTTP/1.1 only. Confirming the negative needs the Front Door 'supported protocols' reference, which was not read. |
Evidence 2
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | learn.microsoft.com/en-us/azure/frontdoor/front-door-faq | Currently, Azure Front Door only supports HTTP/1.1 from the edge to the origin. |
| 2026-10-23 | learn.microsoft.com/en-us/azure/frontdoor/front-door-overvie | Accelerate application performance using the Azure Front Door unicast network and split TCP connections; terminate SSL offload at the edge and natively support the HTTP/2 protocol |
More fields 7
{
"wg_path": "none",
"wg_detail": "There is no UDP forwarding to configure, so no WireGuard datagram can be carried.",
"ingress": "http-only",
"volume_tib_month": null,
"volume_stated": "No UDP allowance exists. The product is billed per request and per GB of HTTP(S) delivery, with no L4 forwarding at any price.",
"bytes_transit": "yes",
"transit_note": "HTTP bytes only; UDP is not carried"
}Unknown values 2
$.per_object_cap.statedthe field does not apply to this kind of offer$.retention.statedthe field does not apply to this kind of offer