Azure WAF tuning adjusts Azure Front Door WAF behavior so legitimate application requests remain available while matching attack rules can still be detected or blocked. Detection mode records matches without blocking; prevention mode blocks matching requests. Because Front Door WAF lacks Application Gateway's anomaly scoring, switching modes requires application-specific validation. section 3.3.2
A practical tuning workflow uses Azure CLI to:
- Review behavior before enabling prevention, then confirm that legitimate traffic is not blocked. section 3.3.2
Front Door policy baseline
Create AzFrontDoorWafPolicy in myResourceGroup with the Premium_AzureFrontDoor SKU, disabled state, and Detection mode; add Microsoft_DefaultRuleSet version 1.1 and Microsoft_BotManagerRuleSet version 1.0, then associate the policy with the Front Door endpoint.
