Skip to content

Commit 75a8de9

Browse files
authored
Merge pull request #94636 from winthrop28/patch-65
adding regions and portal link
2 parents 5e93c46 + 342a0eb commit 75a8de9

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/web-application-firewall/ag/create-waf-policy-ag.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,9 @@ ms.author: victorh
1313

1414
Associating a WAF policy with listeners allows for multiple sites behind a single WAF to be protected by different policies. For example, if there are five sites behind your WAF, you can have five separate WAF policies (one for each listener) to customize the exclusions, custom rules, and managed rulesets for one site without effecting the other four. If you want a single policy to apply to all sites, you can just associate the policy with the Application Gateway, rather than the individual listeners, to make it apply globally. Policies can also be applied to a path-based routing rule.
1515

16+
> [!NOTE]
17+
> Per-site WAF Policy is available in South Central US and North Europe. To access them in the portal, please use [this link](https://aka.ms/AppgwwafWithAllFeatureFlags) until it goes live for everyone.
18+
1619
You can make as many policies as you want. Once you create a policy, it must be associated to an Application Gateway to go into effect, but it can be associated with any combination of Application Gateways and listeners.
1720

1821
If your Application Gateway has a policy applied, and then you apply a different policy to a listener on that Application Gateway, the listener's policy will take effect, but just for the listener(s) 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.

0 commit comments

Comments
 (0)