Study guide
6.4 Web Application Firewall on Azure Front Door
Designing and Implementing Microsoft Azure Networking Solutions AZ-700
Track your progress as you read
Finished sections get a check mark.
1 Introduction & AZ-700 Exam Overview
0.1 About the AZ-700 Exam: Format, Scoring & Skills Measured
2 Chapter 1: Azure Virtual Networks, Addressing & Subnet Architecture
1.1 VNet Planning, IP Addressing & Subnet Design 1.2 Virtual Network Peering & Global Peering 1.3 Azure NAT Gateway & Outbound Connectivity 1.4 Azure Virtual Network Manager (AVNM) & Network Groups 1.5 Public IP Addresses, Public IP Prefixes & Custom IP Prefixes (BYOIP)
3 Chapter 2: Azure Name Resolution & Core Routing
2.1 Azure DNS & Private DNS Zones 2.2 Azure Private DNS Resolver & Hybrid Name Resolution 2.3 System Routes & User-Defined Routes (UDR) 2.4 BGP & Custom Route Propagation 2.5 Azure Route Server & Dynamic NVA Route Exchange
4 Chapter 3: Hybrid Connectivity with Azure VPN Gateway
3.1 Azure VPN Gateway Architecture & SKUs 3.2 Site-to-Site (S2S) VPN & High Availability 3.3 Point-to-Site (P2S) VPN & Client Authentication 3.4 Azure Extended Network, Always On VPN & Azure Network Adapter
5 Chapter 4: Azure ExpressRoute & Virtual WAN
4.1 Azure ExpressRoute Architecture & Peering Models 4.2 ExpressRoute Routing, Resiliency & Global Reach 4.3 Azure Virtual WAN Architecture & Hub Routing 4.4 ExpressRoute BFD, Monitoring & Connection Troubleshooting
6 Chapter 5: Regional Load Balancing & Application Gateway
5.1 Azure Load Balancer Architecture & Rules 5.2 Azure Application Gateway Architecture & Routing 5.3 Web Application Firewall (WAF) on Application Gateway 5.4 Inbound NAT Rules, Port Forwarding & Health Probe Design
7 Chapter 6: Global Traffic Management & Azure Front Door
6.1 Azure Front Door Architecture & Routing 6.2 Azure Traffic Manager & DNS Load Balancing 6.3 Load Balancing Decision Matrix & Multi-Tier Design 6.4 Web Application Firewall on Azure Front Door
8 Chapter 7: Azure Private Link & Service Endpoints
7.1 Virtual Network Service Endpoints & Policies 7.2 Azure Private Endpoints & Private Link Architecture 7.3 Private Endpoint DNS Integration & Hybrid Resolution 7.4 Azure Private Link Service for Multi-Tenant Solutions
9 Chapter 8: Network Security Groups & Azure Bastion
8.1 Network Security Groups (NSGs) & Application Security Groups (ASGs) 8.2 Azure Bastion Architecture & Secure Remote Access 8.3 Azure Virtual Network Manager Security Admin Rules
10 Chapter 9: Azure Firewall & Security Policies
9.1 Azure Firewall Architecture & Rule Processing 9.2 Azure Firewall Manager & DDoS Protection
11 Chapter 10: Azure Network Observability & Troubleshooting
10.1 Network Watcher Diagnostic Tools 10.2 NSG Flow Logs, VNet Flow Logs & Traffic Analytics 10.3 Network Troubleshooting Scenarios & End-to-End Connectivity 10.4 Azure Monitor Network Insights & Defender for Cloud Network Posture
6.4 Web Application Firewall on Azure Front Door
Key Takeaways Explain This Topic AI
Azure WAF is natively integrated with Front Door Premium with full capabilities; on Front Door Standard only custom rules are supported, so managed rule sets and bot protection require the Premium tier.
Custom rules are always processed before managed rule sets, and custom rule actions are Allow, Block, Log, and Redirect.
Default Rule Set 2.0 and later use anomaly scoring: Critical contributes 5, Error 4, Warning 3, and Notice 2, and the WAF acts when a request reaches a score of 5 or greater.
DRS 2.2 contains 18 rule groups and is baselined on OWASP CRS 3.3.4 at Paranoia Level 1 with all PL2 rules disabled by default, while DRS 2.1 contains 17 rule groups and is baselined on CRS 3.3.2.
A Front Door WAF policy is associated with domains on a Front Door profile, whereas an Application Gateway WAF policy is associated globally or per listener or per URI path map.
Last updated: August 2026
Web Application Firewall on Azure Front Door
The AZ-700 security objective asks you to configure rule sets for WAF on Azure Front Door and, separately, for WAF on Application Gateway . They share a name and an OWASP heritage, but they differ in tier gating, rule set versions, and association model — and the exam tests exactly those differences.
- Dimension WAF on Application Gateway WAF on Azure Front Door
- Scope Regional, in front of a regional backend pool Global , at the Microsoft edge PoPs
- Tier gate Requires the WAF_v2 SKU Full WAF requires Front Door Premium ; Standard supports custom rules only
- Managed rule sets OWASP CRS 3.2 / 3.1 / 3.0 and DRS DRS 2.2 / 2.1 / 2.0 / 1.1 / 1.0 and Bot Manager 1.0 / 1.1
- Association target Globally, per listener , or per URI path map Per domain on a Front Door profile
Blocks where? At the regional gateway, after the traffic has crossed to your region At the edge , before traffic enters your infrastructure
Important
The tier gate is the single most tested Front Door WAF fact. Azure WAF is natively integrated with Front Door Premium with full capabilities ; for Front Door Standard, only custom rules are supported . Any scenario requiring managed OWASP protection, Microsoft Threat Intelligence rules, or bot protection at the edge requires Premium .
1. WAF Policy Structure
A Front Door WAF policy contains two kinds of security rules:
Custom rules that you author.
Managed rule sets — Azure-maintained collections of preconfigured rules.
When both are present, custom rules are processed first , then the managed rule set. Custom rule actions are Allow, Block, Log, and Redirect . This ordering is what makes a custom allow-list rule an effective way to bypass a managed rule that produces a false positive for a known-good source.
Modes
- Mode Behaviour
- Detection Matches are logged only; nothing is blocked. Use this for the initial baseline period
- Prevention The configured action is enforced on matching traffic
- 2. Anomaly Scoring — DRS 2.0 and Later
DRS versions 2.0 and above use anomaly scoring . A rule match does not block the request on its own, even in Prevention mode. Instead each rule carries a severity that contributes a numeric value to the request's anomaly score .
- Rule severity Value contributed to the anomaly score
- Critical 5
- Error 4
- Warning 3
- Notice 2
When a request accumulates an anomaly score of 5 or greater , the WAF takes the configured anomaly score action , which is one of Block, Log, or Redirect . The default anomaly score action is Block .
Working the arithmetic
A single Critical match scores 5, which alone reaches the threshold and blocks in Prevention mode with the default action.
A single Warning match scores 3 — not enough on its own. Two Warning matches score 6 and do reach the threshold.
In Detection mode , a request scoring 5 or more is logged with the action blocked recorded by rule ID 949110 ( Inbound Anomaly Score Exceeded ) but is not actually blocked.
Note
Rule sets older than DRS 2.0 run in traditional mode , where a match on any single rule is evaluated independently and blocks the request. In traditional mode you have no visibility into the full set of rules a request matched, which is exactly why anomaly scoring was introduced.
3. Managed Rule Set Versions
- Rule set Rule groups Baseline Availability
- DRS 2.2 18 OWASP CRS 3.3.4 plus Microsoft Threat Intelligence rules Front Door Premium
- DRS 2.1 17 OWASP CRS 3.3.2 plus Microsoft Threat Intelligence rules Front Door Premium only
- DRS 2.0 17 OWASP CRS with anomaly scoring Front Door Premium only
- DRS 1.1 / 1.0 Legacy Traditional (non-anomaly) mode Legacy / classic
- Bot Manager 1.0 BadBots, GoodBots, UnknownBots Bot categorisation Front Door Premium
Bot Manager 1.1 BadBots, GoodBots, UnknownBots Enhanced malicious-bot protection and improved good-bot detection Front Door Premium
All DRS versions include the Microsoft Threat Intelligence Collection rules, written in partnership with the Microsoft Threat Intelligence team to add coverage, patch specific vulnerabilities, and reduce false positives.
Paranoia levels
Every rule is assigned a Paranoia Level (PL) .
PL1 rules are less aggressive and rarely produce false positives; they provide baseline security with minimal tuning.
PL2 rules detect more attacks but are expected to produce false positives that need tuning.
DRS 2.2 is configured at PL1 by default, with all PL2 rules disabled. You enable PL2 rules manually when you want deeper inspection.
DRS 2.1 and CRS 3.2 include PL2 rules enabled ; to run strictly at PL1 you disable specific PL2 rules or set their action to Log.
Paranoia Levels 3 and 4 are not supported in Azure WAF.
Caution
Changing rule set version in the portal resets your tuning. If you assign a new managed rule set through the Azure portal, all previous customisations — rule state, rule actions, and rule-level exclusions — are reset to the new rule set's defaults. Custom rules and policy settings survive. To preserve overrides and exclusions, make the version change with PowerShell, CLI, REST API, or a template.
4. A Safe Rollout Sequence
Create the WAF policy on a Premium profile and assign the current DRS in Detection mode.
Run for one to two weeks and analyse WAF logs for false positives — typically JSON payloads containing SQL-like keywords, or rich-text fields tripping XSS rules.
Add exclusions for the specific request attributes causing false positives, and add custom Allow rules ahead of the managed set for known-good sources.
Switch to Prevention mode with the anomaly score action set to Block .
Associate the policy with the Front Door domains that need it.
Layer Bot Manager and rate-limiting custom rules once the baseline is stable.
Tip
Front Door Premium also allows you to secure the origin with Azure Private Link , so the backend has no public IP at all. Edge WAF plus a Private Link origin is the reference zero-trust pattern: the only path to the application is through the inspected edge.