If you have FIPS mode enabled for your V1 gateway, it won't be migrated to your new v2 gateway.

To migrate a TLS/SSL configuration, you must specify all the TLS/SSL certs used in your v1 gateway.

Virtual network service endpoint policies are currently not supported in an Application Gateway subnet.

If you have a network security group or user defined routes associated to the v2 gateway subnet, make sure they adhere to the NSG requirements and UDR requirements for a successful migration.

However, if the existing subnet already has a v2 gateway, that may still work provided there's enough IP address space. The script can't create the v2 gateway in any existing subnets that already have a v1 gateway.

You must provide an IP address space for another subnet within your virtual network where your v1 gateway is located.

However, you can allocate an existing (unallocated) public or private IP address to the new v2 gateway. It isn't possible to move the IP addresses associated with the existing v1 gateway seamlessly to v2.

The new v2 gateway has new public and private IP addresses.

Seamlessly copies the configuration associated with the v1 Standard or WAF gateway to the newly created Standard_V2 or WAF_V2 gateway.

Creates a new Standard_v2 or WAF_v2 gateway in a virtual network subnet that you specify.

Migration overviewĪn Azure PowerShell script is available that does the following: However, some high-level, general recommendations are provided. Client traffic migration varies depending on your specific environment. This article covers configuration migration.

If you want to migrate from v1 to v2, follow the steps in this article. However, existing v1 gateways aren't automatically upgraded to v2.

Azure Application Gateway and Web Application Firewall (WAF) v2 is now available, offering additional features such as autoscaling and availability-zone redundancy.

Wafv2