You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/web-application-firewall/afds/afds-overview.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,8 @@ author: halkazwini
5
5
ms.author: halkazwini
6
6
ms.service: azure-web-application-firewall
7
7
ms.topic: concept-article
8
-
ms.date: 01/14/2025
8
+
ms.date: 02/25/2026
9
+
9
10
# Customer intent: As a security administrator, I want to configure Azure Web Application Firewall policies on Azure Front Door, so that I can protect my web applications from malicious attacks and ensure compliance with security standards while maintaining high availability.
10
11
---
11
12
@@ -17,7 +18,7 @@ Azure Web Application Firewall on Azure Front Door is a global and centralized s
17
18
18
19
A WAF prevents malicious attacks close to the attack sources before they enter your virtual network. You get global protection at scale without sacrificing performance. A WAF policy easily links to any Azure Front Door profile in your subscription. New rules can be deployed within minutes, so you can respond quickly to changing threat patterns.
19
20
20
-

21
+
:::image type="content" source="../media/overview/wafoverview.png" alt-text="Screenshot that shows Azure Web Application Firewall.":::
@@ -114,7 +115,7 @@ Three bot categories are supported: *Bad*, *Good*, and *Unknown*. The WAF platfo
114
115
115
116
The WAF platform manages and dynamically updates bot signatures. You can set custom actions to block, allow, log, or redirect for different types of bots.
116
117
117
-

118
+
:::image type="content" source="../media/afds-overview/botprotect2.png" alt-text="Screenshot that shows a bot protection rule set." lightbox="../media/afds-overview/botprotect2.png":::
118
119
119
120
If bot protection is enabled, incoming requests that match bot rules are blocked, allowed, or logged based on the configured action. Bad bots are blocked, good bots are allowed, and unknown bots are logged by default. You can set custom actions to block, allow, log, or JS challenge for different types of bots. You can access WAF logs from a storage account, event hub, log analytics, or send logs to a partner solution.
Copy file name to clipboardExpand all lines: articles/web-application-firewall/afds/waf-front-door-custom-rules.md
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,12 @@
1
1
---
2
-
title: Web application firewall custom rule for Azure Front Door
2
+
title: WAF Custom Rule for Azure Front Door
3
3
description: Learn how to use web application firewall (WAF) custom rules to protect your web applications from malicious attacks.
4
4
author: halkazwini
5
5
ms.author: halkazwini
6
6
ms.service: azure-web-application-firewall
7
7
ms.topic: concept-article
8
-
ms.date: 05/31/2024
8
+
ms.date: 02/25/2026
9
+
9
10
# Customer intent: "As a security administrator, I want to configure custom rules for a web application firewall, so that I can protect my web applications from various types of malicious attacks and control access based on defined conditions."
10
11
---
11
12
@@ -230,7 +231,8 @@ Here's an example JSON description of the custom rule:
230
231
231
232
Custom rules can be duplicated within a given policy. When duplicating a rule, you need to specify a unique name for the rule and a unique priority value. Additionally, custom rules can be copied from one Azure Front Door WAF policy to another as long as the policies are both in the same subscription. When copying a rule from one policy to another, you need to select the Azure Front Door WAF policy you wish to copy the rule into. Once you select the WAF policy you need to give the rule a unique name, and assign a priority rank.
232
233
233
-
## Next steps
234
-
-[Configure a WAF policy by using Azure PowerShell](waf-front-door-custom-rules-powershell.md).
235
-
- Learn about [Azure Web Application Firewall on Azure Front Door](afds-overview.md).
236
-
- Learn how to [create an Azure Front Door instance](../../frontdoor/quickstart-create-front-door.md).
234
+
## Related content
235
+
236
+
-[Configure a WAF policy by using Azure PowerShell](waf-front-door-custom-rules-powershell.md)
237
+
-[Azure Web Application Firewall on Azure Front Door](afds-overview.md)
238
+
-[Create an Azure Front Door instance](../../frontdoor/quickstart-create-front-door.md)
Copy file name to clipboardExpand all lines: articles/web-application-firewall/afds/waf-front-door-monitor.md
+9-4Lines changed: 9 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,15 @@
1
1
---
2
-
title: Azure Web Application Firewall monitoring and logging
2
+
title: Monitoring and Logging
3
+
titleSuffix: Azure Web Application Firewall
3
4
description: Learn about Azure Web Application Firewall in Azure Front Door monitoring and logging.
4
5
author: halkazwini
5
6
ms.author: halkazwini
6
7
ms.service: azure-web-application-firewall
7
8
ms.topic: how-to
8
-
ms.date: 05/23/2024
9
+
ms.date: 02/25/2026
9
10
ms.custom: devx-track-js
10
11
zone_pivot_groups: front-door-tiers
12
+
11
13
# Customer intent: As a security analyst, I want to monitor and analyze Azure Web Application Firewall logs and metrics, so that I can ensure my application's security and identify any potential threats to its integrity.
12
14
---
13
15
@@ -185,6 +187,9 @@ The following snippet shows an example log entry, including the reason that the
185
187
186
188
For more information about the other Azure Front Door logs, see [Monitor metrics and logs in Azure Front Door](../../frontdoor/front-door-diagnostics.md#logs).
187
189
188
-
## Next step
190
+
## Related content
191
+
192
+
-[Best practices for Azure Front Door WAF](waf-front-door-best-practices.md)
193
+
-[Create a WAF policy on Azure Front Door](waf-front-door-create-portal.md)
194
+
-[Azure Web Application Firewall on Azure Front Door](afds-overview.md)
189
195
190
-
Learn more about [Azure Front Door](../../frontdoor/front-door-overview.md).
Copy file name to clipboardExpand all lines: articles/web-application-firewall/afds/waf-front-door-rate-limit.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,12 @@
1
1
---
2
-
title: Web application firewall rate limiting for Azure Front Door
2
+
title: WAF Rate Limiting for Azure Front Door
3
3
description: Learn how to use web application firewall rate limiting to protect your web applications from malicious attacks.
4
4
author: halkazwini
5
5
ms.author: halkazwini
6
6
ms.service: azure-web-application-firewall
7
7
ms.topic: concept-article
8
-
ms.date: 07/29/2024
8
+
ms.date: 02/25/2026
9
+
9
10
# Customer intent: As a web application administrator, I want to implement rate limiting using a web application firewall, so that I can protect my applications from denial-of-service attacks and manage traffic effectively.
10
11
---
11
12
@@ -43,7 +44,7 @@ A few considerations to keep in mind while you determine threshold values and ti
43
44
- Setting larger time window sizes (for example, five minutes over one minute) and larger threshold values (for example, 200 over 100) tend to be more accurate in enforcing close to rate limit's thresholds than using the shorter time window sizes and lower threshold values.
44
45
- Azure Front Door WAF rate limiting operates on a fixed time period. Once a rate limit threshold is breached, all traffic matching that rate limiting rule is blocked for the remainder of the fixed window.
45
46
46
-
## Next steps
47
+
## Related content
47
48
48
-
- Configure [rate limiting on your Azure Front Door WAF](waf-front-door-rate-limit-configure.md).
49
-
-Review [rate limiting best practices](waf-front-door-best-practices.md#rate-limiting-best-practices).
49
+
-[Configure rate limiting on your Azure Front Door WAF](waf-front-door-rate-limit-configure.md).
50
+
-[Rate limiting best practices](waf-front-door-best-practices.md#rate-limiting-best-practices).
Copy file name to clipboardExpand all lines: articles/web-application-firewall/ag/application-gateway-waf-configuration.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,13 @@
1
1
---
2
-
title: Web application firewall exclusion lists in Azure Application Gateway - Azure portal
2
+
title: WAF Exclusion Lists in Azure Application Gateway
3
3
description: This article provides information on Web Application Firewall exclusion lists configuration in Application Gateway with the Azure portal.
4
4
author: halkazwini
5
5
ms.author: halkazwini
6
6
ms.service: azure-web-application-firewall
7
7
ms.topic: concept-article
8
-
ms.date: 01/13/2025
8
+
ms.date: 02/25/2026
9
9
ms.custom: devx-track-azurepowershell
10
+
10
11
# Customer intent: As a web application administrator, I want to configure exclusion lists for my Web Application Firewall, so that I can prevent false positives and ensure legitimate traffic is not blocked by security rules.
So if the URL `http://www.contoso.com/?user%3c%3e=joe` is scanned by the WAF, it doesn't evaluate the string **joe**, but it still evaluates the parameter name **user%3c%3e**.
530
530
531
-
## Next steps
531
+
## Related content
532
532
533
-
- After you configure your WAF settings, you can learn how to view your WAF logs. For more information, see [Application Gateway diagnostics](../../application-gateway/application-gateway-diagnostics.md#diagnostic-logging).
534
-
-[Learn more about Azure network security](../../networking/security/index.yml)
533
+
-[WAF DRS and CRS rule groups and rules](application-gateway-crs-rulegroups-rules.md)
Copy file name to clipboardExpand all lines: articles/web-application-firewall/ag/application-gateway-waf-request-size-limits.md
+7-8Lines changed: 7 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,22 +1,21 @@
1
1
---
2
-
title: Web application firewall request size limits in Azure Application Gateway - Azure portal
2
+
title: WAF Request Size Limits in Azure Application Gateway
3
3
description: This article provides information on Web Application Firewall request size limits in Application Gateway with the Azure portal.
4
4
author: halkazwini
5
5
ms.author: halkazwini
6
6
ms.service: azure-web-application-firewall
7
7
ms.topic: concept-article
8
-
ms.date: 07/16/2024
8
+
ms.date: 02/25/2026
9
+
9
10
# Customer intent: "As a security administrator, I want to configure the request and file upload size limits in the Web Application Firewall, so that I can optimize security policies and prevent unauthorized large requests or file uploads affecting application performance."
10
11
---
11
12
12
13
# Web Application Firewall request and file upload size limits
13
14
14
15
Web Application Firewall allows you to configure request size limits within a lower and upper boundary. Application Gateways Web Application Firewalls running Core Rule Set 3.2 or later have more request and file upload size controls, including the ability to disable max size enforcement for requests and/or file uploads.
15
16
16
-
17
17
> [!IMPORTANT]
18
-
> We are in the process of deploying a new feature for Application Gateway v2 Web Application Firewalls running Core Rule Set 3.2 or later that allows for greater control of your request body size, file upload size, and request body inspection. If you're running Application Gateway v2 Web Application Firewall with Core Rule Set 3.2 or later, and you notice requests getting rejected (or not getting rejected) for a size limit please refer to the troubleshooting steps at the bottom of this page.
19
-
18
+
> We are in the process of deploying a new feature for Application Gateway v2 Web Application Firewalls running Core Rule Set 3.2 or later that allows for greater control of your request body size, file upload size, and request body inspection. If you're running Application Gateway v2 Web Application Firewall with Core Rule Set 3.2 or later, and you notice requests getting rejected (or not getting rejected) for a size limit, refer to the [troubleshooting](#troubleshooting) steps in this article.
20
19
21
20
## Limits
22
21
@@ -33,7 +32,7 @@ Only requests with Content-Type of *multipart/form-data* are considered for file
33
32
>**Example:** If you have a custom rule with priority 0 (the highest priority) set to allow a request with the header xyz, even if the request's size is larger than your maximum request size limit, it will get allowed before the max size limit is enforced
34
33
35
34
>[!NOTE]
36
-
>There is a 4 KB buffer on the file upload limit. The file size restriction won't be enforced until the file upload exceeds your set limit plus this buffer.
35
+
>There's a 4 KB buffer on the file upload limit. The file size restriction won't be enforced until the file upload exceeds your set limit plus this buffer.
37
36
38
37
## Request body inspection
39
38
@@ -64,7 +63,7 @@ If you're an Application Gateway v2 Web Application Firewall customer running Co
64
63
**Enforce maximum request body limit**
65
64
- PowerShell: "RequestBodyEnforcement"
66
65
- CLI: "request_body_enforcement"
67
-
- Control if your Web Application Firewall enforces a max size limit on request bodies; when turned off it does not reject any requests for being too large.
66
+
- Control if your Web Application Firewall enforces a max size limit on request bodies; when turned off it doesn't reject any requests for being too large.
68
67
69
68
**Maximum request body size (KB)**
70
69
- PowerShell: "MaxRequestBodySizeInKB"
@@ -74,7 +73,7 @@ If you're an Application Gateway v2 Web Application Firewall customer running Co
74
73
**Enforce maximum file upload limit**
75
74
- PowerShell: "FileUploadEnforcement"
76
75
- CLI: "file_upload_enforcement"
77
-
- Controls if your Web Application Firewall enforces a max size limit on file uploads; when turned off it does not reject any file uploads for being too large.
76
+
- Controls if your Web Application Firewall enforces a max size limit on file uploads; when turned off it doesn't reject any file uploads for being too large.
Copy file name to clipboardExpand all lines: articles/web-application-firewall/ag/application-gateway-web-application-firewall-portal.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,13 @@
1
1
---
2
-
title: 'Tutorial: Create an application gateway with a Web Application Firewall using the Azure portal'
2
+
title: 'Tutorial: Create an Application Gateway With a Web Application Firewall Using the Azure Portal'
3
3
description: In this tutorial, you learn how to create an application gateway with a Web Application Firewall by using the Azure portal.
4
4
author: halkazwini
5
5
ms.author: halkazwini
6
6
ms.service: azure-web-application-firewall
7
7
ms.topic: tutorial
8
-
ms.date: 05/23/2024
8
+
ms.date: 02/25/2026
9
9
ms.custom: sfi-image-nochange
10
-
#Customer intent: As an IT administrator, I want to use the Azure portal to set up an application gateway with Web Application Firewall so I can protect my applications.
10
+
11
11
# Customer intent: As an IT administrator, I want to configure an application gateway with a Web Application Firewall through the cloud portal so that I can ensure my web applications are protected against cybersecurity threats.
Copy file name to clipboardExpand all lines: articles/web-application-firewall/ag/create-waf-policy-ag.md
+8-5Lines changed: 8 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,13 @@
1
1
---
2
-
title: Create Web Application Firewall (WAF) policies for Application Gateway
2
+
title: Create WAF Policies for Application Gateway
3
+
titleSuffix: Azure Web Application Firewall
3
4
description: Learn how to create Web Application Firewall policies for Application Gateway.
4
5
author: halkazwini
5
6
ms.author: halkazwini
6
7
ms.service: azure-web-application-firewall
7
8
ms.topic: concept-article
8
-
ms.date: 01/15/2025
9
+
ms.date: 02/25/2026
10
+
9
11
# Customer intent: "As a cloud administrator, I want to create and manage Web Application Firewall policies for the Application Gateway, so that I can customize security settings for multiple sites efficiently and ensure each site is protected according to its specific requirements."
10
12
---
11
13
@@ -17,8 +19,8 @@ You can make as many policies as you want. Once you create a policy, it must be
17
19
18
20
If your Application Gateway has an associated policy, and then you associate a different policy to a listener on that Application Gateway, the listener's policy takes effect, but just for the listeners that they're assigned to. The Application Gateway policy still applies to all other listeners that don't have a specific policy assigned to them.
19
21
20
-
> [!NOTE]
21
-
> Once a Firewall Policy is associated to a WAF, there must always be a policy associated to that WAF. You can overwrite that policy, but disassociating a policy from the WAF entirely isn't supported.
22
+
> [!NOTE]
23
+
> Once a Firewall Policy is associated to a WAF, there must always be a policy associated to that WAF. You can overwrite that policy, but disassociating a policy from the WAF entirely isn't supported.
22
24
23
25
All new Web Application Firewall's WAF settings (custom rules, managed ruleset configurations, exclusions, etc.) live inside of a WAF Policy. If you have an existing WAF, these settings might still exist in your WAF config. For steps on how to move to the new WAF Policy, see [Upgrade your WAF Config to a WAF Policy](#upgrade) later in this article.
24
26
@@ -105,4 +107,5 @@ Then proceed with the steps to associate a WAF Policy to your application gatewa
105
107
106
108
## Next step
107
109
108
-
Learn more about [Web Application Firewall CRS rule groups and rules](application-gateway-crs-rulegroups-rules.md).
110
+
> [!div class="nextstepaction"]
111
+
> [Web Application Firewall CRS rule groups and rules](application-gateway-crs-rulegroups-rules.md)
Copy file name to clipboardExpand all lines: articles/web-application-firewall/ag/policy-overview.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,12 @@
1
1
---
2
-
title: Azure Web Application Firewall (WAF) policy overview
2
+
title: WAF Policy Overview
3
3
description: This article is an overview of Web Application Firewall (WAF) global, per-site, and per-URI policies.
4
4
author: halkazwini
5
5
ms.author: halkazwini
6
6
ms.service: azure-web-application-firewall
7
7
ms.topic: concept-article
8
-
ms.date: 01/14/2025
8
+
ms.date: 02/25/2026
9
+
9
10
# Customer intent: "As a cloud security administrator, I want to create and manage Web Application Firewall policies for different application gateways, so that I can customize security settings based on the specific needs of each site and URI. "
10
11
---
11
12
@@ -16,7 +17,7 @@ Web Application Firewall Policies contain all the WAF settings and configuration
16
17
There's no limit on the number of policies you can create. When you create a policy, it must be associated to an application gateway to take effect. It can be associated with any combination of application gateways, listeners, and path-based rules.
17
18
18
19
> [!Note]
19
-
> Application Gateway has two versions of the WAF sku: Application Gateway WAF_v1 and Application Gateway WAF_v2. WAF policy associations are only supported for the Application Gateway WAF_v2 sku.
20
+
> Application Gateway has two versions of the WAF SKU: Application Gateway WAF_v1 and Application Gateway WAF_v2. WAF policy associations are only supported for the Application Gateway WAF_v2 SKU.
20
21
21
22
## Global WAF policy
22
23
@@ -38,7 +39,7 @@ As with per-site WAF policies, more specific policies override less specific one
38
39
39
40
### Example
40
41
41
-
Say you have three sites: contoso.com, fabrikam.com, and adatum.com all behind the same application gateway. You want a WAF applied to all three sites, but you need added security with adatum.com because that is where customers visit, browse, and purchase products.
42
+
Say you have three sites: contoso.com, fabrikam.com, and adatum.com all behind the same application gateway. You want a WAF applied to all three sites, but you need added security with adatum.com because that's where customers visit, browse, and purchase products.
42
43
43
44
You can apply a global policy to the WAF, with some basic settings, exclusions, or custom rules if necessary to stop some false positives from blocking traffic. In this case, there's no need to have global SQL injection rules running because fabrikam.com and contoso.com are static pages with no SQL backend. So you can disable those rules in the global policy.
0 commit comments