You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: includes/vpn-gateway-deprecate-sku-faq.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,22 +16,22 @@ All existing gateways that use the Standard or High Performance SKU will be supp
16
16
17
17
### Will my IP address change when my Legacy VPN gateway SKU (Standard or HighPerformance) is migrated as part of Basic IP address migration initiated through Azure portal?
18
18
19
-
No, the IP address will not change when you migrate Basic IP using Azure portal experience. You can choose to migrate the Basic SKU IP address to Standard SKU IP address through a customer controlled portal experience. For more information about Basic SKU IP migration, see [About migrating a Basic SKU public IP address to Standard SKU for VPN Gateway](../articles/vpn-gateway/basic-public-ip-migrate-about.md) article.
19
+
No, the IP address won't change when you migrate Basic IP using Azure portal experience. You can choose to migrate the Basic SKU IP address to Standard SKU IP address through a customer controlled portal experience. For more information about Basic SKU IP migration, see [About migrating a Basic SKU public IP address to Standard SKU for VPN Gateway](../articles/vpn-gateway/basic-public-ip-migrate-about.md) article.
20
20
21
21
### Do I need to migrate my gateways from the Standard or High Performance SKU right now?
22
22
23
-
No, you are required to migrate the Basic IP address on your gateway using the portal experience if you want to retain the IP address. As part of this migration, your gateways will be automatically migrated to AZ SKUs.
23
+
No, you're required to migrate the Basic IP address on your gateway using the portal experience if you want to retain the IP address. As part of this migration, your gateways are automatically migrated to AZ SKUs.
24
24
25
25
26
26
### Will there be any pricing difference for my gateways after migration?
27
27
28
-
Your SKUs will automatically be migrated and upgraded to AZ SKUs as part of Basic IP migration. See [VPN Gateway pricing](https://azure.microsoft.com/pricing/details/vpn-gateway/) for more details.
28
+
Your SKUs are automatically migrated and upgraded to AZ SKUs as part of Basic IP migration. See [VPN Gateway pricing](https://azure.microsoft.com/pricing/details/vpn-gateway/) for more details.
29
29
30
30
### Will there be any performance impact on my gateways with this migration?
31
31
32
32
Yes. You get better performance with VpnGw1AZ and VpnGw2AZ. For more information about SKU throughput, see [About gateway SKUs](https://go.microsoft.com/fwlink/?linkid=2256302).
33
33
34
-
### What happens if I don't migrate by February 28, 2025?
34
+
### What happens if I don't migrate by February 28, 2026?
35
35
36
36
All gateways that still use the Standard or High Performance SKU will be migrated automatically and upgraded to the following AZ SKUs:
37
37
@@ -42,6 +42,6 @@ We'll send communication before initiating migration on any gateways.
42
42
43
43
### Is the VPN Gateway Basic SKU also retiring?
44
44
45
-
No, the VPN Gateway Basic SKU is not retiring. You can create a VPN gateway by using the Basic SKU via Azure PowerShell or the Azure CLI.
45
+
No, the VPN Gateway Basic SKU isn't retiring. You can create a VPN gateway by using the Basic SKU via Azure PowerShell or the Azure CLI.
46
46
47
47
Currently, the VPN Gateway Basic SKU supports only the Basic SKU public IP address resource (which is on a path to retirement). We're working on adding support for the Standard SKU public IP address resource to the VPN Gateway Basic SKU.
0 commit comments