Skip to content

Commit 3438244

Browse files
authored
Update expressroute-migration-classic-resource-manager.md
1 parent d1198bf commit 3438244

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: ganesr
66

77
ms.service: expressroute
88
ms.topic: conceptual
9-
ms.date: 01/17/2019
9+
ms.date: 06/13/2019
1010
ms.author: ganesr;cherylmc
1111
ms.custom: seodec18
1212

@@ -19,7 +19,7 @@ This article explains how to migrate ExpressRoute-associated virtual networks fr
1919

2020
[!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
2121

22-
* 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).
22+
* 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).
2323
* 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.
2424
* 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.
2525
* Verify that the circuit is fully operational in the classic deployment model.

0 commit comments

Comments
 (0)