Skip to content

Commit 5d4dbdb

Browse files
authored
PR review: Update FAQ for VPN Gateway SKU migration details
Made Acrolinx changes to bring the file's overall Acrolinx score to at least 80. Changed 2025 to 2026 on line 34.
1 parent f81c20e commit 5d4dbdb

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -16,22 +16,22 @@ All existing gateways that use the Standard or High Performance SKU will be supp
1616

1717
### 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?
1818

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.
2020

2121
### Do I need to migrate my gateways from the Standard or High Performance SKU right now?
2222

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.
2424

2525

2626
### Will there be any pricing difference for my gateways after migration?
2727

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.
2929

3030
### Will there be any performance impact on my gateways with this migration?
3131

3232
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).
3333

34-
### What happens if I don't migrate by February 28, 2025?
34+
### What happens if I don't migrate by February 28, 2026?
3535

3636
All gateways that still use the Standard or High Performance SKU will be migrated automatically and upgraded to the following AZ SKUs:
3737

@@ -42,6 +42,6 @@ We'll send communication before initiating migration on any gateways.
4242

4343
### Is the VPN Gateway Basic SKU also retiring?
4444

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.
4646

4747
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

Comments
 (0)