Merge pull request #290043 from deeharris-23/patch-15

add instructions for locating a classic vpn gateway

Author: rmca14

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

@@ -17,14 +17,21 @@ 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 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).
+VPN gateways begin 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 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.
 
+## Locating a classic VPN gateway 
+To locate a classic VPN gateway via PowerShell, you will need to install the Azure PowerShell Service Management module. Start here: [Installing the Azure PowerShell Service Management module](https://learn.microsoft.com/powershell/azure/servicemanagement/install-azure-ps). To view classic resources, you will need co-admin or owner permissions. You can't use Az cmdlets to access classic resources. 
+
+
+To locate a classic VPN gateway via Azure portal, open the portal and search for "Virtual network(classic)". Select your classic virtual network and navigate to the gateway blade to find your classic virtual network gateway. 
+
+
 ## Supported scenarios
 
 Most common VPN connectivity scenarios are covered by classic to Resource Manager migration. The supported scenarios include: