Remove mentions of VPN Gateway form cross-sub and cross-rg move documentation

-VPN gateway moves are blocked at the vNet level with CSES and VMSS gateways

Author: deeharris-23

articles/azure-resource-manager/management/move-limitations/networking-move-limitations.md

@@ -16,9 +16,9 @@ If you want to move networking resources to a new region, see [Tutorial: Move Az
 
 ## Dependent resources
 
-When moving a resource, you must also move its dependent networking resources. However, any resource that is associated with a **Standard SKU** public IP address can't be moved across subscriptions. For example, you can't move a VPN Gateway that is associated with a **Standard SKU** public IP address to a new subscription.
+When moving a resource, you must also move its dependent networking resources. However, any resource that is associated with a **Standard SKU** public IP address can't be moved across subscriptions.
 
-To move a virtual machine with a network interface card to a new subscription, you must move all dependent resources. Move the virtual network for the network interface card, all other network interface cards for the virtual network, and the VPN gateways. If a virtual machine is associated with a **Standard SKU** public IP address, [disassociate the public IP address](../../../virtual-network/ip-services/remove-public-ip-address-vm.md) before moving across subscriptions.
+To move a virtual machine with a network interface card to a new subscription, you must move all dependent resources. Move the virtual network for the network interface card, and all other network interface cards for the virtual network. If a virtual machine is associated with a **Standard SKU** public IP address, [disassociate the public IP address](../../../virtual-network/ip-services/remove-public-ip-address-vm.md) before moving across subscriptions.
 
 If you move the virtual network for an AKS cluster, the AKS cluster stops working. The local network gateways can be in a different resource group.
 
@@ -28,11 +28,6 @@ For more information, see [Scenario for move across subscriptions](../move-resou
 
 To move a peered virtual network, you must first disable the virtual network peering. Once disabled, you can move the virtual network. After the move, reenable the virtual network peering.
 
-## VPN Gateways
-
-You can't move VPN Gateways across resource groups or subscriptions if they are of Basic SKU. Basic SKU is only meant for test environment usage and doesn't support resource move operation.
-A virtual network gateway must always be in the same resource group as its virtual network, they can't be moved separately.
-
 ## Subnet links
 
 You can't move a virtual network to a different subscription if the virtual network contains a subnet with resource navigation links. For example, if an Azure Cache for Redis resource is deployed into a subnet, that subnet has a resource navigation link.