Skip to content

Migrate to Application Gateway v2#

Operational Excellence · Application Gateway · Rule · 2023_06

Use a Application Gateway v2 SKU.

Description#

The Application Gateway v1 SKUs (Standard and WAF) will be retired on April 28, 2026. To avoid service disruption, migrate to Application Gateway v2 SKUs.

The v2 SKUs offers performance enhancements, security controls and adds support for critical new features like autoscaling, zone redundancy, support for static VIPs, header rewrite, key vault integration, mutual authentication (mTLS), Azure Kubernetes Service ingress controller and private link.

Recommendation#

Migrate deprecated v1 Application Gateways to a v2 SKU before retirement to avoid service disruption.

Examples#

Configure with Azure template#

To deploy Application Gateways that pass this rule:

  • Set properties.sku.tier or properties.sku.name to Standard_v2 (Application Gateway) or WAF_v2 (Web Application Firewall).

For example:

Azure Template snippet
{
  "name": "[parameters('name')]",
  "type": "Microsoft.Network/applicationGateways",
  "apiVersion": "2022-07-01",
  "location": "[resourceGroup().location]",
  "properties": {
    "sku": {
      "capacity": 2,
      "name": "WAF_v2",
      "tier": "WAF_v2"
    }
  }
}

Configure with Bicep#

To deploy Application Gateways that pass this rule:

  • Set properties.sku.tier or properties.sku.name to Standard_v2 (Application Gateway) or WAF_v2 (Web Application Firewall).

For example:

Azure Bicep snippet
resource appGw 'Microsoft.Network/applicationGateways@2022-07-01' = {
  name: 
  location: location
  properties: {
    sku: {
      capacity: 2
      name: 'WAF_v2'
      tier: 'WAF_v2'
    }
  }
}

Notes#

This rule is applicable for both Application Gateways and Application Gateways with Web Application Firewall (WAF).

Not all existing features under the v1 SKUs are supported in the v2 SKUs. The v2 SKUs are not currently available in all regions.

Comments