{
  "id": 20644678,
  "title": "Edge Meets Region: Securing Global APIs with Azure Front Door Edge Actions and Application Gateway JWT Validation",
  "url": "https://urgent.news/2026/11/18/edge-meets-region-securing-global-apis-with-azure-front-door-edge",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-18T19:31:08.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/passadis/edge-meets-region-securing-global-apis-with-azure-front-door-edge-actions-and-application-gateway-3a8i"
  },
  "original_language": "en",
  "account": "Edge Actions in Azure Front Door allow you to run custom JavaScript code at the edge, near users, before requests reach your backend services. This JavaScript logic helps with A/B testing, manipulating request and response headers, rejecting invalid requests, dynamically selecting origins, rewriting URLs, and even validating JWT tokens. Edge Actions are executed within an isolated sandbox and can only run for up to 10 milliseconds before being stopped. If your code takes longer than that, Front Door stops processing it without executing the Edge Action. The Edge Actions feature provides a way to add custom logic at the edge without needing to deploy code to your backends.\n\nOn the other hand, Azure Application Gateway JWT validation enables you to validate Microsoft Entra ID access tokens in incoming HTTPS requests without writing any code. This feature checks the token's signature, issuer, tenant, audience, and lifetime, and adds an x-msft-entra-identity header to the backend request if the token is valid. This header contains the tenant ID and object ID, which can be used by your services to authenticate the request without needing to handle token parsing themselves. The Application Gateway JWT validation requires a specific SKU, an HTTPS listener, and outbound access to login.microsoftonline.com on port 443.\n\nBy combining Edge Actions in Azure Front Door with JWT validation in Azure Application Gateway, global, high-importance applications can achieve several benefits. First, data residency can be controlled by the token's tenant claim, allowing Edge Actions to route users to the appropriate regional Application Gateway based on their tenant. Second, requests with invalid or malformed JWTs can be rejected at the edge, reducing the load on your Application Gateway and origin services during credential stuffing attacks or misbehaving clients. Third, Application Gateway provides full cryptographic validation of JWTs and passes a verified x-msft-entra-identity header to your backends, enabling Zero Trust identity for every microservice without each team implementing token validation independently. Fourth, Edge Action execution filters allow for safe, tenant-aware rollouts of new backend versions, enabling canary releases and instant rollbacks. Finally, the combination of these two features provides defense in depth, as the edge layer fails open on timeout while the regional gateway fails closed, ensuring that invalid requests are stopped before reaching your backends.",
  "summary": "Why This Matters Global, business-critical applications need two things from their front door: speed and smart routing close to the user, and strict enforcement close to the workload. Until recently, getting both on Azure meant custom code in every backend, or extra services in front of them. Two new previews change that. Azure Front Door Edge Actions brings programmable logic to Microsoft's…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}