From 67fabd4d63d0b17cd9c52a2e69d542a5d0b0bbc7 Mon Sep 17 00:00:00 2001 From: Cheryl McGuire <1660095+cherylmc@users.noreply.github.com> Date: Fri, 9 Oct 2020 08:08:05 -0700 Subject: [PATCH] Update vpn-gateway-howto-site-to-site-classic-portal.md --- .../vpn-gateway-howto-site-to-site-classic-portal.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/articles/vpn-gateway/vpn-gateway-howto-site-to-site-classic-portal.md b/articles/vpn-gateway/vpn-gateway-howto-site-to-site-classic-portal.md index f61ac3875c573..585ce69d31d7a 100644 --- a/articles/vpn-gateway/vpn-gateway-howto-site-to-site-classic-portal.md +++ b/articles/vpn-gateway/vpn-gateway-howto-site-to-site-classic-portal.md @@ -105,12 +105,12 @@ Site-to-Site connections to an on-premises network require a VPN device. In this ## Create the connection -In this step, using the values from the previous steps, you set the shared key and create the connection. The key you set is must be the same key that was used in your VPN device configuration. - > [!NOTE] > For the classic deployment model, this step is not available in the Azure portal or via Azure Cloud Shell. You must use the Service Management (SM) version of the Azure PowerShell cmdlets locally from your desktop. > +In this step, using the values from the previous steps, you set the shared key and create the connection. The key you set is must be the same key that was used in your VPN device configuration. + 1. Set the shared key and create the connection. * Change the -VNetName value and the -LocalNetworkSiteName value. When specifying a name that contains spaces, use single quotation marks around the value.