Skip to content

Commit dea281b

Browse files
committed
Incorp changes from pub PR 92554
1 parent 8311ae1 commit dea281b

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/web-application-firewall/ag/web-application-firewall-troubleshoot.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: This article provides troubleshooting information for Web Applicati
44
services: web-application-firewall
55
author: vhorne
66
ms.service: web-application-firewall
7-
ms.date: 06/09/2022
7+
ms.date: 09/21/2022
88
ms.author: victorh
99
ms.topic: conceptual
1010
---
@@ -154,6 +154,8 @@ In this example, you want to exclude the **Request attribute name** that equals
154154

155155
![WAF exclusion lists](../media/web-application-firewall-troubleshoot/waf-config.png)
156156

157+
You can create exclusions for WAF in Application Gateway at different scope levels. For more information, see [Web Application Firewall exclusion lists](application-gateway-waf-configuration.md#exclusion-scopes).
158+
157159
### Disabling rules
158160

159161
Another way to get around a false positive is to disable the rule that matched on the input the WAF thought was malicious. Since you've parsed the WAF logs and have narrowed the rule down to 942130, you can disable it in the Azure portal. See [Customize web application firewall rules through the Azure portal](application-gateway-customize-waf-rules-portal.md).

0 commit comments

Comments
 (0)