Merge pull request #116216 from derekolo/peering-update

Update setup-basics-tab.png

Author: PMEds28

articles/internet-peering/howto-exchange-portal.md

@@ -6,7 +6,7 @@ services: internet-peering
 author: derekolo
 ms.service: internet-peering
 ms.topic: article
-ms.date: 5/21/2020
+ms.date: 5/2/2020
 ms.author: derekol
 ---
 
@@ -28,14 +28,14 @@ If you prefer, you can complete this guide by using [PowerShell](howto-exchange-
 ### <a name=create></a>Create an Exchange peering
 
 
-As an Internet Exchange Provider, you can create a direct peering request by [Creating a Peering]( https://go.microsoft.com/fwlink/?linkid=2129593).
+As an Internet Exchange Provider, you can create an exchange peering request by [Creating a Peering]( https://go.microsoft.com/fwlink/?linkid=2129593).
 
 1. On the **Create a Peering** page, on the **Basics** tab, fill in the boxes as shown here:
 
->    [!div class="mx-imgBorder"]
->   ![Register Peering Service](./media/setup-basics-tab.png)
+    > [!div class="mx-imgBorder"] 
+    > ![Register Peering Service](./media/setup-basics-tab.png)
 
-* Select your Azure Subscription.
+*    Select your Azure Subscription.
 
 * For Resource group, you can either choose an existing resource group from the drop-down list or create a new group by selecting Create new. We'll create a new resource group for this example.
 
@@ -44,12 +44,12 @@ As an Internet Exchange Provider, you can create a direct peering request by [Cr
 * Region is auto-selected if you chose an existing resource group. If you chose to create a new resource group, you also need to choose the Azure region where you want the resource to reside.
 
 >[!NOTE]
-    The region where a resource group resides is independent of the location where you want to create peering with Microsoft. But it's a best practice to organize your peering resources within resource groups that reside in the closest Azure regions. For example, for peerings in Ashburn, you can create a resource group in East US or East US2.
+>The region where a resource group resides is independent of the location where you want to create peering with Microsoft. But it's a best practice to organize your peering resources within resource groups that reside in the closest Azure regions. For example, for peerings in Ashburn, you can create a resource group in East US or East US2.
 
 * Select your ASN in the **PeerASN** box.
 
 >[!IMPORTANT] 
-You can only choose an ASN with ValidationState as Approved before you submit a peering request. If you just submitted your PeerAsn request, wait for 12 hours or so for ASN association to be approved. If the ASN you select is pending validation, you'll see an error message. If you don't see the ASN you need to choose, check that you selected the correct subscription. If so, check if you have already created PeerAsn by using **[Associate Peer ASN to Azure subscription](https://go.microsoft.com/fwlink/?linkid=2129592)**.
+>You can only choose an ASN with ValidationState as Approved before you submit a peering request. If you just submitted your PeerAsn request, wait for 12 hours or so for ASN association to be approved. If the ASN you select is pending validation, you'll see an error message. If you don't see the ASN you need to choose, check that you selected the correct subscription. If so, check if you have already created PeerAsn by using **[Associate Peer ASN to Azure subscription](https://go.microsoft.com/fwlink/?linkid=2129592)**.
 
 * Select **Next: Configuration** to continue.
 

articles/internet-peering/howto-legacy-direct-portal.md

@@ -27,7 +27,28 @@ If you prefer, you can complete this guide by using [PowerShell](howto-legacy-di
 
 ### <a name=create></a>Convert a legacy Direct peering
 
-You can convert legacy peering connections by using the **Peering** resource.
+As an Internet Service Provider, you can convert legacy direct peering connections by using [Creating a Peering]( https://go.microsoft.com/fwlink/?linkid=2129593).
+
+1. On the **Create a Peering** page, on the **Basics** tab, fill in the boxes as shown here:
+
+    > [!div class="mx-imgBorder"] 
+    > ![Register Peering Service](./media/setup-basics-tab.png)
+
+*    Select your Azure Subscription.
+
+* For Resource group, you can either choose an existing resource group from the drop-down list or create a new group by selecting Create new. We'll create a new resource group for this example.
+
+* Name corresponds to the resource name and can be anything you choose.
+
+* Region is auto-selected if you chose an existing resource group. If you chose to create a new resource group, you also need to choose the Azure region where you want the resource to reside.
+
+>[!NOTE]
+>The region where a resource group resides is independent of the location where you want to create peering with Microsoft. But it's a best practice to organize your peering resources within resource groups that reside in the closest Azure regions. For example, for peerings in Ashburn, you can create a resource group in East US or East US2.
+
+* Select your ASN in the **PeerASN** box.
+
+>[!IMPORTANT] 
+>You can only choose an ASN with ValidationState as Approved before you submit a peering request. If you just submitted your PeerAsn request, wait for 12 hours or so for ASN association to be approved. If the ASN you select is pending validation, you'll see an error message. If you don't see the ASN you need to choose, check that you selected the correct subscription. If so, check if you have already created PeerAsn by using **[Associate Peer ASN to Azure subscription](https://go.microsoft.com/fwlink/?linkid=2129592)**.
 
 #### Launch the resource and configure basic settings
 [!INCLUDE [direct-peering-basic](./includes/direct-portal-basic.md)]

articles/internet-peering/howto-legacy-exchange-portal.md

@@ -21,11 +21,11 @@ If you prefer, you can complete this guide by using [PowerShell](howto-legacy-ex
 
 ## Convert a legacy Exchange peering to an Azure resource
 
-As an Internet Exchange Provider, you can create a direct peering request by [Creating a Peering]( https://go.microsoft.com/fwlink/?linkid=2129593).
+As an Internet Exchange Provider, you can create a exchange peering request by [Creating a Peering]( https://go.microsoft.com/fwlink/?linkid=2129593).
 
 1. On the **Create a Peering** page, on the **Basics** tab, fill in the boxes as shown here:
 
->    [!div class="mx-imgBorder"]
+
 >   ![Register Peering Service](./media/setup-basics-tab.png)
 
 * Select your Azure Subscription.
@@ -37,21 +37,38 @@ As an Internet Exchange Provider, you can create a direct peering request by [Cr
 * Region is auto-selected if you chose an existing resource group. If you chose to create a new resource group, you also need to choose the Azure region where you want the resource to reside.
 
 >[!NOTE]
-    The region where a resource group resides is independent of the location where you want to create peering with Microsoft. But it's a best practice to organize your peering resources within resource groups that reside in the closest Azure regions. For example, for peerings in Ashburn, you can create a resource group in East US or East US2.
+>The region where a resource group resides is independent of the location where you want to create peering with Microsoft. But it's a best practice to organize your peering resources within resource groups that reside in the closest Azure regions. For example, for peerings in Ashburn, you can create a resource group in East US or East US2.
 
 * Select your ASN in the **PeerASN** box.
 
 >[!IMPORTANT]  
-    You can only choose an ASN with ValidationState as Approved before you submit a peering request. If you just submitted your PeerAsn request, wait for 12 hours or so for ASN association to be approved. If the ASN you select is pending validation, you'll see an error message. If you don't see the ASN you need to choose, check that you selected the correct subscription. If so, check if you have already created PeerAsn by using **[Associate Peer ASN to Azure subscription](https://go.microsoft.com/fwlink/?linkid=2129592)**.
+>You can only choose an ASN with ValidationState as Approved before you submit a peering request. If you just submitted your PeerAsn request, wait for 12 hours or so for ASN association to be approved. If the ASN you select is pending validation, you'll see an error message. If you don't see the ASN you need to choose, check that you selected the correct subscription. If so, check if you have already created PeerAsn by using **[Associate Peer ASN to Azure subscription](https://go.microsoft.com/fwlink/?linkid=2129592)**.
 
 * Select **Next: Configuration** to continue.
 
 ### <a name=create></a>Convert legacy Exchange peering
 
-You can convert legacy peering connections by using the **Peering** resource.
+You can convert legacy peering connections by using [Creating a Peering]( https://go.microsoft.com/fwlink/?linkid=2129593).
+
+####  Configure basic settings
+>   ![Register Peering Service](./media/setup-basics-tab.png)
+
+* Select your Azure Subscription.
+
+* For Resource group, you can either choose an existing resource group from the drop-down list or create a new group by selecting Create new. We'll create a new resource group for this example.
+
+* Name corresponds to the resource name and can be anything you choose.
+
+* Region is auto-selected if you chose an existing resource group. If you chose to create a new resource group, you also need to choose the Azure region where you want the resource to reside.
+
+>[!NOTE]
+    The region where a resource group resides is independent of the location where you want to create peering with Microsoft. But it's a best practice to organize your peering resources within resource groups that reside in the closest Azure regions. For example, for peerings in Ashburn, you can create a resource group in East US or East US2.
+
+* Select your ASN in the **PeerASN** box.
+
+>[!IMPORTANT]  
+    You can only choose an ASN with ValidationState as Approved before you submit a peering request. If you just submitted your PeerAsn request, wait for 12 hours or so for ASN association to be approved. If the ASN you select is pending validation, you'll see an error message. If you don't see the ASN you need to choose, check that you selected the correct subscription. If so, check if you have already created PeerAsn by using **[Associate Peer ASN to Azure subscription](https://go.microsoft.com/fwlink/?linkid=2129592)**.
 
-#### Launch the resource and configure basic settings
-[!INCLUDE [direct-peering-basic](./includes/direct-portal-basic.md)]
 
 #### Configure connections and submit
 [!INCLUDE [exchange-peering-configuration](./includes/exchange-portal-configuration-legacy.md)]

articles/internet-peering/includes/direct-portal-basic.md

@@ -3,11 +3,11 @@ title: include file
 titleSuffix: Azure
 description: include file
 services: internet-peering
-author: prmitiki
+author: derekolo
 ms.service: internet-peering
 ms.topic: include
-ms.date: 11/27/2019
-ms.author: prmitiki
+ms.date: 5/22/2020
+ms.author: derekol
 ---
 
 1. Select **Create a resource** > **See all**.