Skip to content

Commit 639f33b

Browse files
Update upgrade-ag-waf-policy.md
1 parent ee491d1 commit 639f33b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.custom:
1414

1515
**Applies to:** Application Gateway WAF v2 Configuration deployments
1616

17-
We announced the deprecation of WAF configuration on Application Gateway WAF V2 SKU on **March 15, 2024**. Starting from **March 15, 2027** we are retiring WAF configuration on Application Gateway WAF V2 SKU. This means that the service is not supported after this date. If you use WAF configuration on Application Gateway WAF V2 SKU, start planning your migration to WAF policy now. Complete it by March 15, 2027 to take advantage of Application Gateway V2.
17+
We announced the deprecation of WAF configuration on Application Gateway WAF V2 SKU on **March 15, 2024**. Starting from **March 15, 2027** we are retiring WAF configuration on Application Gateway WAF V2 SKU. This means that the WAF configuration is not supported after this date. If you use WAF configuration on Application Gateway WAF V2 SKU, start planning your migration to WAF policy now. Complete it by March 15, 2027 to take advantage of Application Gateway V2.
1818

1919
Azure Web Application Firewall (WAF) provides centralized protection of your web applications from common exploits and vulnerabilities. Web Application Firewall Policies contain all the WAF settings and configurations. This includes exclusions, custom rules, managed rules, and so on. These policies are then associated with an application gateway (global), a listener (per-site), or a path-based rule (per-URI) for them to take effect.
2020

0 commit comments

Comments
 (0)