add details about internal migration that occurs after vnet migration

Author: deeharris-23

articles/vpn-gateway/vpn-gateway-classic-resource-manager-migration.md

@@ -17,9 +17,11 @@ VPN gateways can now be migrated from the classic deployment model to [Resource
 > [!IMPORTANT]
 > [!INCLUDE [classic gateway restrictions](../../includes/vpn-gateway-classic-gateway-restrict-create.md)]
 
-VPN gateways are migrated as part of VNet migration from classic to Resource Manager. This migration is done one VNet at a time. There aren't additional requirements in terms of tools or prerequisites to migrate. Migration steps are identical to the existing VNet migration and are documented at [IaaS resources migration page](/azure/virtual-machines/migration-classic-resource-manager-ps).
+VPN gateways begins with a VNet migration from classic to Resource Manager. This migration is done by customers one VNet at a time. There aren't additional requirements in terms of tools or prerequisites to begin the VNet migration. Migration steps are identical to the existing VNet migration and are documented at [IaaS resources migration page](/azure/virtual-machines/migration-classic-resource-manager-ps).
 
-There isn't a data path downtime during migration and thus existing workloads continue to function without the loss of on-premises connectivity during migration. The public IP address associated with the VPN gateway doesn't change during the migration process. This implies that you won't need to reconfigure your on-premises router once the migration is completed.  
+There isn't a data path downtime during VNet migration and thus existing workloads continue to function without the loss of on-premises connectivity during migration. The public IP address associated with the VPN gateway doesn't change during the migration process. This implies that you won't need to reconfigure your on-premises router once the migration is completed. 
+
+Once the VNet migration is completed, Azure will attempt to complete the remainder of the gateway migration to Resource Manager. If the gateway migration does not succeed, customers may be informed to delete their VPN Gateway (classic deployment) and create a new VPN gateway (Resource Manager). If no action is taken by the customer, the existing VPN Gateway (classic deployment) may be decommissioned. Customers can visit the FAQ for additional information and to minimize downtime during migration from classic to Resource Manager.  
 
 The Resource Manager model is different from the classic model and is composed of virtual network gateways, local network gateways and connection resources. These represent the VPN gateway itself, the local-site representing on premises address space and connectivity between the two respectively. Once migration is completed, your gateways won't be available in the classic model and all management operations on virtual network gateways, local network gateways, and connection objects must be performed using the Resource Manager model.
 
@@ -64,4 +66,4 @@ Since we transform VNet-to-VNet connectivity without requiring local sites, the
 
 ## Next steps
 
-After learning about VPN gateway migration support, go to [platform-supported migration of IaaS resources from classic to Resource Manager](/azure/virtual-machines/migration-classic-resource-manager-ps) to get started.
+After learning about VPN gateway migration support, go to [platform-supported migration of IaaS resources from classic to Resource Manager](/azure/virtual-machines/migration-classic-resource-manager-ps) to get started.