Build with an Azure free account. Get USD200 credit for 30 days and 12 months of free services.

Start free today

Protect your web applications using WAF with Azure Front Door

Play Protect your web applications using WAF with Azure Front Door

The Discussion

  • User profile image
    Regarding the last side by side comparison, why exactly was going through WAF faster than accessing the site directly?
  • User profile image
    Is there a list of all the Frontdoor entry points available?
  • User profile image
  • User profile image
    Azure Front Door accelerates application delivery due to multiple factors:
    1. Front Door is a globally distributed service, deployed to multiple edge locations, close to end users. Global anycast architecture connects the end user to the nearest AFD site or Point of Presence (POP). Each Front Door edge node knows the fastest and most available backend, and so can send traffic to the fastest backend.
    2. With more and more traffic flowing in, and also by reusing the connection from the health probes, AFD from its POP locations, more often than not finds an existing connection to forward the request to. This further gives a strong performance boost of sorts.
    3. We optimize connections from Front Door edge nodes to application backend, and also constantly monitor Microsoft's global network for best experience.
    4. Support for HTTP/2, SSL resumption and TCP Fast Open ensures faster and more resilient client connectivity.

    As a result, you often see faster response for a request to go through front door with WAF inspection than to go directly to backend without WAF.
  • User profile image
    About Azure API Management and Front Door, would you advise to use both in conjunction? Or would an APIM deployment contain all it needs from a security perspective?

Add Your 2 Cents