updates for clarity

Author: mbender-ms

articles/virtual-network/ip-services/public-ip-basic-upgrade-guidance.md

@@ -45,7 +45,7 @@ We recommend the following approach to upgrade to Standard SKU public IP address
   | Virtual Machine | Use scripts or manually detach and upgrade public IPs. For standalone virtual machines, you can use the [upgrade script](public-ip-upgrade-vm.md) or for virtual machines in an availability set use [this script](public-ip-upgrade-availability-set.md). |
   | Virtual Machine Scale Sets | [Replace basic SKU instance public IP addresses](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-networking#public-ipv4-per-virtual-machine) with new standard SKU. |
   | Load Balancer (Basic SKU) | New Load Balancer SKU required. Use the upgrade script [Upgrade Basic Load Balancer to Standard SKU](../../load-balancer/upgrade-basic-standard-with-powershell.md) to upgrade to Standard Load Balancer. |
-  | VPN Gateway (using Basic IPs) | A migration path will be provided in the future. When this migration path is available, we update this decision path with migration information and send out a service health alert. For more information, see [Migrating a basic SKU FAQ](../../vpn-gateway/vpn-gateway-vpn-faq.md#migrating-a-basic-sku-public-ip-address-to-standard-sku). |
+  | VPN Gateway (using Basic IPs) | VPN Gateway migration is required. All non-AZ SKUs become AZ SKUs. Follow the [VPN Gateway migration guidance](../../vpn-gateway/basic-public-ip-migrate-howto.md) to upgrade to Standard SKU public IPs. |
   |  ExpressRoute Gateway (using Basic IPs) | ExpressRoute Gateway migration is required. Follow the [ExpressRoute Gateway migration guidance](../../expressroute/gateway-migration.md)   |
   | Application Gateway (v1 SKU) | New AppGW SKU required. Use this [migration script to migrate from v1 to v2](../../application-gateway/migrate-v1-v2.md).  |
   | Azure Databricks (using Basic IPs) | For ephemeral workloads, Standard SKU public IP addresses are automatically deployed as virtual machines (VMs) cycle out through regular usage attrition with new VMs. For long running workloads, we recommended manually [restarting the compute resources](/azure/databricks/compute/clusters-manage#restart) which replaces existing Basic IPs with Standard IPs.  |