Merge pull request #103641 from vhorne/waf-policy

remove note

Author: PRMerger10

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

@@ -5,17 +5,14 @@ services: web-application-firewall
 ms.topic: conceptual
 author: vhorne
 ms.service: web-application-firewall
-ms.date: 11/19/2019
+ms.date: 02/08/2020
 ms.author: victorh
 ---
 
 # Create Web Application Firewall policies for Application Gateway
 
 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. 
 
-   > [!NOTE]
-   > 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.  
-
 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. 
 
 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.