Skip to content

Commit ded87a6

Browse files
committed
Revert "update to add portal configuration reference"
This reverts commit 3dd5b86.
1 parent baf1d01 commit ded87a6

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/web-application-firewall/afds/waf-front-door-geo-filtering.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ By default, Azure Front Door Service responds to user requests regardless of the
1616

1717
A WAF policy usually includes a set of custom rules. A rule consists of match conditions, an action, and a priority. In match condition, you define a match variable, operator, and match value. For geo filtering rule, match variable is REMOTE_ADDR, operator is GeoMatch, value is the two letter country code of interest. You may combine a GeoMatch condition and a REQUEST_URI string match condition to create a path-based geo-filtering rule.
1818

19-
You can configure a geo-filtering policy for your Front Door using the Azure portal, [Azure PowerShell](waf-front-door-tutorial-geo-filtering.md) or our [quickstart template](https://github.com/Azure/azure-quickstart-templates/tree/master/101-front-door-geo-filtering).
19+
You can configure a geo-filtering policy for your Front Door by either using [Azure PowerShell](waf-front-door-tutorial-geo-filtering.md) or by using our [quickstart template](https://github.com/Azure/azure-quickstart-templates/tree/master/101-front-door-geo-filtering).
2020

2121
## Country code reference
2222

0 commit comments

Comments
 (0)