Merge pull request #79561 from cherylmc/patch-2

Update expressroute-migration-classic-resource-manager.md

Author: PRMerger7

articles/expressroute/expressroute-migration-classic-resource-manager.md

@@ -2,12 +2,12 @@
 title: 'Migrate virtual networks from classic to Resource Manager - ExpressRoute: Azure: PowerShell | Microsoft Docs'
 description: This page describes how to migrate ExpressRoute-associated virtual networks to Resource Manager after moving your circuit.
 services: expressroute
-author: ganesr
+author: cherylmc
 
 ms.service: expressroute
 ms.topic: conceptual
-ms.date: 01/17/2019
-ms.author: ganesr;cherylmc
+ms.date: 06/13/2019
+ms.author: cherylmc
 ms.custom: seodec18
 
 ---
@@ -19,7 +19,7 @@ This article explains how to migrate ExpressRoute-associated virtual networks fr
 
 [!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
 
-* Verify that you have the latest version of the Azure PowerShell modules. For more information, see [How to install and configure Azure PowerShell](/powershell/azure/overview).
+* Verify that you have the latest versions of the Azure PowerShell modules. For more information, see [How to install and configure Azure PowerShell](/powershell/azure/overview). To install the PowerShell Service Management module (which is needed for the classic deployment model), see [Installing the Azure PowerShell Service Management Module](/powershell/azure/servicemanagement/install-azure-ps).
 * Make sure that you have reviewed the [prerequisites](expressroute-prerequisites.md), [routing requirements](expressroute-routing.md), and [workflows](expressroute-workflows.md) before you begin configuration.
 * Review the information that is provided under [Moving an ExpressRoute circuit from classic to Resource Manager](expressroute-move.md). Make sure that you fully understand the limits and limitations.
 * Verify that the circuit is fully operational in the classic deployment model.