Skip to content

Commit 6db25ec

Browse files
Merge pull request #247062 from Miskatonic-Electronic/patch-2
Update geomatch-custom-rules.md
2 parents ffde0de + d070aa5 commit 6db25ec

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/web-application-firewall/ag/geomatch-custom-rules.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,9 @@ To create a geo-filtering custom rule in the Azure portal, select *Geo location*
1818
> [!NOTE]
1919
> Geo-filtering works based on mapping each request's IP address to a country or region. There might be some IP addresses in the data set that are not yet mapped to a country or region. To avoid accidentally blocking legitimate users, Application Gateway's WAF allows requests from unknown IP addresses.
2020
21+
> [!IMPORTANT]
22+
> Include the country code **ZZ** whenever you use geo-filtering. The **ZZ** country code (or *Unknown* country) captures IP addresses that are not yet mapped to a country in our dataset. This avoids false positives.
23+
2124
## Country/Region codes
2225

2326
If you're using the Geomatch operator, the selectors can be any of the following two-digit country/region codes.

0 commit comments

Comments
 (0)