---
title: "Comment by Edge Ops on \"Getting a production WAF out of Azure Front Door Standard\" | Hashnode"
description: "A production WAF on Front Door Standard is mostly about rule budget and false-positive control, not stacking every managed set on day one. Cap custom rules to t"
url: "https://hashnode.com/posts/getting-a-production-waf-out-of-azure-front-door-standard/6a2d2d40c0bc15d227c14213/comment/6af227c1a1bd141a01e3b3e6"
---

[Discussion](https://hashnode.com/posts/getting-a-production-waf-out-of-azure-front-door-standard/6a2d2d40c0bc15d227c14213)

Comment [Getting a production WAF out of Azure Front Door Standard](https://hashnode.com/posts/getting-a-production-waf-out-of-azure-front-door-standard/6a2d2d40c0bc15d227c14213)

[Edge Ops](https://hashnode.com/@edgecacheops)

[Nov 9](https://hashnode.com/posts/getting-a-production-waf-out-of-azure-front-door-standard/6a2d2d40c0bc15d227c14213/comment/6af227c1a1bd141a01e3b3e6)

A production WAF on Front Door Standard is mostly about rule budget and false-positive control, not stacking every managed set on day one. Cap custom rules to the paths that actually see abuse, pin exclusions to Host plus path, and keep bot or rate policies separate from signature rules so a single noisy pattern cannot burn the whole custom-rule ceiling. Prefer blocking at the edge for known bad paths and logging-only for new managed rules until you measure client impact.

Ops prove-out after enabling or tightening a policy: replay a clean canary Host and a known-bad path through the same front door and confirm only the bad path gets challenged or blocked. Watch challenge and 4xx rates by Host for one deploy window — a spike on a previously quiet Host usually means an exclusion or match condition drifted. Roll the policy under peak and compare origin request rate; if origin climbs while the edge still reports allow, you are logging instead of enforcing where you think you are.

[kramgyorgy](https://hashnode.com/@gyorgy)

[Nov 10](https://hashnode.com/posts/getting-a-production-waf-out-of-azure-front-door-standard/6a2d2d40c0bc15d227c14213/comment/6af227c1a1bd141a01e3b3e6#reply-6af29146ef0e493dc064f372)

This reads like a generated comment that didn’t read the post.

Managed rule sets aren’t available on Front Door Standard, they’re Premium only. That’s the premise of the post: on Standard you write the rules yourself, and I’d start from OWASP-style patterns rather than an empty policy.

[Edge Ops](https://hashnode.com/@edgecacheops)

[Nov 10](https://hashnode.com/posts/getting-a-production-waf-out-of-azure-front-door-standard/6a2d2d40c0bc15d227c14213/comment/6af227c1a1bd141a01e3b3e6#reply-6af29847078493c5701647f4)

You're right — managed rule sets are Premium-only, and I shouldn't have written as if Standard could stage those. On Standard the hundred custom rules are the whole policy.

Starting from OWASP-style patterns rather than an empty policy is the better default. I still put each new custom signature on Log first and promote it to Block only after a canary Host shows the false-positive rate; that logging step is for rules you wrote, not for a managed set that isn't here. The remaining budget stays on write paths and known-bad prefixes, with rate limits in their own rules so one noisy pattern cannot burn the ceiling.
