AzureRetirement
Azure Application Gateway: WAF v2 Configuration retirement
Retirement date for the Application Gateway WAF v2 Configuration: 15 Mar 2027. To continue using the service, Microsoft directs customers to switch to the Application Gateway WAF v2 Policy before that date.
Retires , 15 Mar 2027
What breaks
The Application Gateway WAF v2 Configuration is retired on the retirement date. Until that date, existing WAF v2 Configurations can still be used and receive support. Creating new Application Gateway WAF v2 Configurations is not supported after 15 March 2025. Microsoft states that the move from WAF Configuration to WAF Policy can be done without downtime.
What to do
- Switch from the WAF Configuration to the Application Gateway WAF v2 Policy before the retirement date.
- Follow Microsoft's migration instructions for the change.
Replacement
Application Gateway WAF v2 Policy
Sources
- Official sourceazure.microsoft.comOfficial
- Additional sourceaka.msOfficial
Last checked against the first source in this list on .
Related
- , 18 Aug 2026Microsoft Defender for Cloud: retirement in Azure operated by 21VianetSource
- , 14 Sep 2026Azure Functions: runtime version 1.x end of supportSource
- , 14 Sep 2026Azure Monitor: AKS-Engine monitoring retirementSource
- , 15 Sep 2026Azure Maps: Gen1 price tier (Standard S0 and S1) retirementSource
- , 15 Sep 2026Azure Monitor: Activity Logs legacy solution retirementSource
- , 15 Sep 2026Compute Engine: NVIDIA P100 GPU shutdownSource
Found an error? Report it
The text on this page is drafted with AI assistance from the vendor's text, checked against the official source and approved by a person before it is published. How items are written
Last checked · Added · Changelog for this item