Skip to content

Commit 9608120

Browse files
Merge pull request #313557 from aybatra/patch-56
Revise support date and migration information in FAQ
2 parents 40a8593 + f90aa76 commit 9608120

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

includes/vpn-gateway-deprecate-sku-faq.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
ms.author: cherylmc
33
author: cherylmc
4-
ms.date: 03/16/2026
4+
ms.date: 03/23/2026
55
ms.service: azure-vpn-gateway
66
ms.topic: include
77
---
@@ -12,7 +12,7 @@ No. You can create gateways that use VpnGw1 and VpnGw2 SKUs for the same price a
1212

1313
### How long will my existing gateways be supported on the Standard and High Performance SKUs?
1414

15-
All existing gateways that use the Standard or High Performance SKU will be supported until February 28, 2026.
15+
The customer initiated migration as well the gateways will be supported until the retirement date.
1616

1717
### Will my IP address change when my legacy VPN gateway SKU is migrated?
1818

@@ -30,7 +30,7 @@ Your SKUs are automatically migrated and upgraded to SKUs that are supported by
3030

3131
Yes. You get better performance with the VpnGw1AZ and VpnGw2AZ SKUs. For more information about SKU throughput, see [About gateway SKUs](https://go.microsoft.com/fwlink/?linkid=2256302).
3232

33-
### What happens if I don't migrate by February 28, 2026?
33+
### What happens if I don't migrate by retirement date?
3434

3535
To ensure a smooth transition, we strongly recommend that customers use the Basic IP migration tool to migrate their Basic IPs and associated gateways. After Jun 2026, we'll attempt to automatically migrate all gateways that still use the Standard or High Performance SKU:
3636

0 commit comments

Comments
 (0)