Merge pull request #301273 from raboilla/patch-21

tweaks to migration considerations-Update basic-public-ip-migrate-abo…

Author: prmerger-automator[bot]

articles/vpn-gateway/basic-public-ip-migrate-about.md

@@ -18,7 +18,7 @@ This article explains the migration process from a Basic SKU public IP address t
 
 To migrate your gateway, you first need to validate whether your resource is capable of migration. Here are some common situations to be aware of:
 
-* If your current gateway subnet is /28 or smaller, the migration tool will error out. You need to [resize the gateway subnet](../virtual-network/virtual-network-manage-subnet.md#change-subnet-settings) to /27 or larger before you can proceed with migration.
+* If your current gateway subnet is /28 or smaller, the migration tool may error out. You can use this to [add multiple prefixes for subnet](https://learn.microsoft.com/azure/virtual-network/how-to-multiple-prefixes-subnet?tabs=powershell) to /27 or larger before you can proceed with migration.
 
 * Before your initiate migration for your VPN gateway, verify that your gateway subnet has at least *three* available IP addresses in your current prefix.