Merge pull request #234961 from asudbring/linux-fixes

Linux doc-athon fixes for Create peering different subscriptions how-to article

Author: prmerger-automator[bot]

articles/virtual-network/create-peering-different-subscriptions.md

@@ -30,21 +30,33 @@ This tutorial peers virtual networks in the same region. You can also peer virtu
 
 ## Prerequisites
 
+# [**Portal**](#tab/create-peering-portal)
+
 - An Azure account(s) with two active subscriptions. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 
 - An Azure account with permissions in both subscriptions or an account in each subscription with the proper permissions to create a virtual network peering. For a list of permissions, see [Virtual network peering permissions](virtual-network-manage-peering.md#permissions).
 
-    - If the virtual networks are in different subscriptions and Active Directory tenants, and you intend to separate the duty of managing the network belonging to each tenant, then add the user from each tenant as a guest in the opposite tenant and assign them a reader role to the virtual network.
+    - To separate the duty of managing the network belonging to each tenant, add the user from each tenant as a guest in the opposite tenant and assign them a reader role to the virtual network. This procedure applies if the virtual networks are in different subscriptions and Active Directory tenants.
 
-    - If the virtual networks are in different subscriptions and Active Directory tenants, and you do not intend to separate the duty of managing the network belonging to each tenant, then add the user from tenant A as a guest in the opposite tenant and assign them the correct permissions to establish a network peering. This user will be able to initiate and connect the network peering from each subscription.
+    - To establish a network peering when you don't intend to separate the duty of managing the network belonging to each tenant, add the user from tenant A as a guest in the opposite tenant. Then, assign them the correct permissions to initiate and connect the network peering from each subscription. With these permissions, the user is able to establish the network peering from each subscription.
 
     - For more information about guest users, see [Add Azure Active Directory B2B collaboration users in the Azure portal](../active-directory/external-identities/add-users-administrator.md?toc=%2fazure%2fvirtual-network%2ftoc.json#add-guest-users-to-the-directory).
 
     - Each user must accept the guest user invitation from the opposite Azure Active Directory tenant.
 
-[!INCLUDE [azure-cli-prepare-your-environment-no-header.md](~/articles/reusable-content/azure-cli/azure-cli-prepare-your-environment-no-header.md)]
+# [**PowerShell**](#tab/create-peering-powershell)
 
-- This how-to article requires version 2.31.0 or later of the Azure CLI. If using Azure Cloud Shell, the latest version is already installed.
+- An Azure account(s) with two active subscriptions. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
+
+- An Azure account with permissions in both subscriptions or an account in each subscription with the proper permissions to create a virtual network peering. For a list of permissions, see [Virtual network peering permissions](virtual-network-manage-peering.md#permissions).
+
+    - To separate the duty of managing the network belonging to each tenant, add the user from each tenant as a guest in the opposite tenant and assign them a reader role to the virtual network. This procedure applies if the virtual networks are in different subscriptions and Active Directory tenants.
+
+    - To establish a network peering when you don't intend to separate the duty of managing the network belonging to each tenant, add the user from tenant A as a guest in the opposite tenant. Then, assign them the correct permissions to initiate and connect the network peering from each subscription. With these permissions, the user is able to establish the network peering from each subscription.
+
+    - For more information about guest users, see [Add Azure Active Directory B2B collaboration users in the Azure portal](../active-directory/external-identities/add-users-administrator.md?toc=%2fazure%2fvirtual-network%2ftoc.json#add-guest-users-to-the-directory).
+
+    - Each user must accept the guest user invitation from the opposite Azure Active Directory tenant.
 
 - Azure PowerShell installed locally or Azure Cloud Shell.
 
@@ -54,7 +66,27 @@ This tutorial peers virtual networks in the same region. You can also peer virtu
 
 If you choose to install and use PowerShell locally, this article requires the Azure PowerShell module version 5.4.1 or later. Run `Get-Module -ListAvailable Az` to find the installed version. If you need to upgrade, see [Install Azure PowerShell module](/powershell/azure/install-Az-ps). If you're running PowerShell locally, you also need to run `Connect-AzAccount` to create a connection with Azure.
 
-In the following steps, you'll learn how to peer virtual networks in different subscriptions and Azure Active Directory tenants. 
+# [**Azure CLI**](#tab/create-peering-cli)
+
+- An Azure account(s) with two active subscriptions. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
+
+- An Azure account with permissions in both subscriptions or an account in each subscription with the proper permissions to create a virtual network peering. For a list of permissions, see [Virtual network peering permissions](virtual-network-manage-peering.md#permissions).
+
+    - To separate the duty of managing the network belonging to each tenant, add the user from each tenant as a guest in the opposite tenant and assign them a reader role to the virtual network. This procedure applies if the virtual networks are in different subscriptions and Active Directory tenants.
+
+    - To establish a network peering when you don't intend to separate the duty of managing the network belonging to each tenant, add the user from tenant A as a guest in the opposite tenant. Then, assign them the correct permissions to initiate and connect the network peering from each subscription. With these permissions, the user is able to establish the network peering from each subscription.
+
+    - For more information about guest users, see [Add Azure Active Directory B2B collaboration users in the Azure portal](../active-directory/external-identities/add-users-administrator.md?toc=%2fazure%2fvirtual-network%2ftoc.json#add-guest-users-to-the-directory).
+
+    - Each user must accept the guest user invitation from the opposite Azure Active Directory tenant.
+
+[!INCLUDE [azure-cli-prepare-your-environment-no-header.md](~/articles/reusable-content/azure-cli/azure-cli-prepare-your-environment-no-header.md)]
+
+- This how-to article requires version 2.31.0 or later of the Azure CLI. If using Azure Cloud Shell, the latest version is already installed.
+
+---
+
+In the following steps, learn how to peer virtual networks in different subscriptions and Azure Active Directory tenants. 
 
 You can use the same account that has permissions in both subscriptions or you can use separate accounts for each subscription to set up the peering. An account with permissions in both subscriptions can complete all of the steps without signing out and signing in to portal and assigning permissions.
 
@@ -282,7 +314,7 @@ Use [az ad user list](/cli/azure/ad/user#az-ad-user-list) to obtain the object I
 ```azurecli-interactive
 az ad user list --display-name UserB
 ```
-```bash
+```output
 [
   {
     "businessPhones": [],
@@ -368,7 +400,7 @@ echo $vnetidA
 
 ## Create virtual network - myVNetB
 
-In this section, you'll sign in as **UserB** and create a virtual network for the peering connection to **myVNetA**.
+In this section, you sign in as **UserB** and create a virtual network for the peering connection to **myVNetA**.
 
 # [**Portal**](#tab/create-peering-portal)
 
@@ -583,7 +615,7 @@ Use [az ad user list](/cli/azure/ad/user#az-ad-user-list) to obtain the object I
 az ad user list --display-name UserA
 ```
 
-```bash
+```output
 [
   {
     "businessPhones": [],
@@ -667,7 +699,7 @@ echo $vnetidB
 
 ## Create peering connection - myVNetA to myVNetB
 
-You'll need the **Resource ID** for **myVNetB** from the previous steps to set up the peering connection.
+You need the **Resource ID** for **myVNetB** from the previous steps to set up the peering connection.
 
 # [**Portal**](#tab/create-peering-portal)
 
@@ -837,11 +869,11 @@ az network vnet peering list \
 
 ---
 
-The peering connection will show in **Peerings** in a **Initiated** state. To complete the peer, a corresponding connection must be set up in **myVNetB**.
+The peering connection shows in **Peerings** in a **Initiated** state. To complete the peer, a corresponding connection must be set up in **myVNetB**.
 
 ## Create peering connection - myVNetB to myVNetA
 
-You'll need the **Resource IDs** for **myVNetA** from the previous steps to set up the peering connection.
+You need the **Resource IDs** for **myVNetA** from the previous steps to set up the peering connection.
 
 # [**Portal**](#tab/create-peering-portal)
 
@@ -1015,7 +1047,9 @@ For more information about using your own DNS for name resolution, see, [Name re
 For more information about Azure DNS, see [What is Azure DNS?](../dns/dns-overview.md).
 
 ## Next steps
-<!-- Add a context sentence for the following links -->
+
 - Thoroughly familiarize yourself with important [virtual network peering constraints and behaviors](virtual-network-manage-peering.md#requirements-and-constraints) before creating a virtual network peering for production use.
+
 - Learn about all [virtual network peering settings](virtual-network-manage-peering.md#create-a-peering).
+
 - Learn how to [create a hub and spoke network topology](/azure/architecture/reference-architectures/hybrid-networking/hub-spoke#virtual-network-peering) with virtual network peering.