acrolinx

asudbring · asudbring · commit 4e590768c386 · 2024-07-01T15:45:14.000-05:00
diff --git a/articles/virtual-network/create-peering-different-subscriptions.md b/articles/virtual-network/create-peering-different-subscriptions.md
@@ -12,7 +12,7 @@ ms.custom: template-how-to, FY23 content-maintenance, devx-track-azurepowershell
 
 # Create a virtual network peering - Resource Manager, different subscriptions and Microsoft Entra tenants
 
-In this tutorial, you learn to create a virtual network peering between virtual networks created through Resource Manager. The virtual networks exist in different subscriptions that may belong to different Microsoft Entra tenants. Peering two virtual networks enables resources in different virtual networks to communicate with each other with the same bandwidth and latency as though the resources were in the same virtual network. Learn more about [Virtual network peering](virtual-network-peering-overview.md).
+In this tutorial, you learn to create a virtual network peering between virtual networks created through Resource Manager. The virtual networks exist in different subscriptions that might belong to different Microsoft Entra tenants. Peering two virtual networks enables resources in different virtual networks to communicate with each other with the same bandwidth and latency as though the resources were in the same virtual network. Learn more about [Virtual network peering](virtual-network-peering-overview.md).
 
 Depending on whether, the virtual networks are in the same, or different subscriptions the steps to create a virtual network peering are different. Steps to peer networks created with the classic deployment model are different. For more information about deployment models, see [Azure deployment model](../azure-resource-manager/management/deployment-models.md?toc=%2fazure%2fvirtual-network%2ftoc.json).
 
@@ -26,13 +26,13 @@ Learn how to create a virtual network peering in other scenarios by selecting th
 
 A virtual network peering can't be created between two virtual networks deployed through the classic deployment model. If you need to connect virtual networks that were both created through the classic deployment model, you can use an Azure [VPN Gateway](../vpn-gateway/tutorial-site-to-site-portal.md?toc=%2fazure%2fvirtual-network%2ftoc.json) to connect the virtual networks.
 
-This tutorial peers virtual networks in the same region. You can also peer virtual networks in different [supported regions](virtual-network-manage-peering.md#cross-region). It's recommended that you familiarize yourself with the [peering requirements and constraints](virtual-network-manage-peering.md#requirements-and-constraints) before peering virtual networks.
+This tutorial peers virtual networks in the same region. You can also peer virtual networks in different [supported regions](virtual-network-manage-peering.md#cross-region). Familiarize yourself with the [peering requirements and constraints](virtual-network-manage-peering.md#requirements-and-constraints) before peering virtual networks.
 
 ## 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 or accounts 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).
 
@@ -48,7 +48,7 @@ This tutorial peers virtual networks in the same region. You can also peer virtu
 
 # [**PowerShell**](#tab/create-peering-powershell)
 
-- 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 or accounts 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).
 
@@ -62,15 +62,15 @@ This tutorial peers virtual networks in the same region. You can also peer virtu
 
 - Azure PowerShell installed locally or Azure Cloud Shell.
 
-- Sign in to Azure PowerShell and ensure you've selected the subscription with which you want to use this feature.  For more information, see [Sign in with Azure PowerShell](/powershell/azure/authenticate-azureps).
+- Sign in to Azure PowerShell and select the subscription with which you want to use this feature. For more information, see [Sign in with Azure PowerShell](/powershell/azure/authenticate-azureps).
 
 - Ensure your `Az.Network` module is 4.3.0 or later. To verify the installed module, use the command `Get-InstalledModule -Name "Az.Network"`. If the module requires an update, use the command `Update-Module -Name Az.Network` if necessary.
 
 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-azure-powershell). If you're running PowerShell locally, you also need to run `Connect-AzAccount` to create a connection with Azure.
 
 # [**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 or accounts 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).
 
@@ -374,7 +374,7 @@ In this section, you sign in as **user-2** and create a virtual network for the
 
 # [**Portal**](#tab/create-peering-portal)
 
-Repeat the steps in the [previous section](#create-virtual-network) to create a second virtual network with the following values:
+Create a second virtual network with the following values by repeating the steps in the [previous section](#create-virtual-network).
 
 | Setting | Value |
 | --- | --- |
@@ -667,7 +667,7 @@ You need the **Resource ID** for **vnet-2** from the previous steps to set up th
     | Virtual network deployment model | **Resource Manager** |
     | I know my resource ID | **Select the box** |
     | Resource ID | **Enter the Resource ID for vnet-2** |
-    | Directory | Select the Entra ID directory that corresponds with **vnet-2** and **user-2** |
+    | Directory | Select the Microsoft Entra ID directory that corresponds with **vnet-2** and **user-2** |
     | **Remote virtual network peering settings** |   |
     | Allow 'the peered virtual network' to access 'vnet-1' | Leave the default of **Enabled** |
     | Allow 'the peered virtual network' to receive forwarded traffic from 'vnet-1' | **Select the box** |
@@ -711,7 +711,7 @@ Connect-AzAccount
 
 ### Change to subscription-1 (optional)
 
-You may have to switch back to **subscription-1** to continue with the actions in **subscription-1**.
+You might have to switch back to **subscription-1** to continue with the actions in **subscription-1**.
 
 Change context to **subscription-1**.
 
@@ -784,7 +784,7 @@ az login
 
 ### Change to subscription-1 (optional)
 
-You may have to switch back to **subscription-1** to continue with the actions in **subscription-1**.
+You might have to switch back to **subscription-1** to continue with the actions in **subscription-1**.
 
 Change context to **subscription-1**.
 
@@ -843,7 +843,7 @@ You need the **Resource IDs** for **vnet-1** from the previous steps to set up t
     | Virtual network deployment model | **Resource Manager** |
     | I know my resource ID | **Select the box** |
     | Resource ID | **Enter the Resource ID for vnet-2** |
-    | Directory | Select the Entra ID directory that corresponds with **vnet-1** and **user-1** |
+    | Directory | Select the Microsoft Entra ID directory that corresponds with **vnet-1** and **user-1** |
     | **Remote virtual network peering settings** |   |
     | Allow 'the peered virtual network' to access 'vnet-1' | Leave the default of **Enabled** |
     | Allow 'the peered virtual network' to receive forwarded traffic from 'vnet-1' | **Select the box** |
@@ -892,7 +892,7 @@ Connect-AzAccount
 
 ### Change to subscription-2 (optional)
 
-You may have to switch back to **subscription-2** to continue with the actions in **subscription-2**.
+You might have to switch back to **subscription-2** to continue with the actions in **subscription-2**.
 
 Change context to **subscription-2**.
 
@@ -965,7 +965,7 @@ az login
 
 ### Change to subscription-2 (optional)
 
-You may have to switch back to **subscription-2** to continue with the actions in **subscription-2**.
+You might have to switch back to **subscription-2** to continue with the actions in **subscription-2**.
 
 Change context to **subscription-2**.
 
@@ -996,7 +996,7 @@ az network vnet peering list \
 ```
 ---
 
-The peering is successfully established after you see **Connected** in the **Peering status** column for both virtual networks in the peering. Any Azure resources you create in either virtual network are now able to communicate with each other through their IP addresses. If you're using subnet-1 Azure name resolution for the virtual networks, the resources in the virtual networks aren't able to resolve names across the virtual networks. If you want to resolve names across virtual networks in a peering, you must create your own DNS server or use Azure DNS.
+The peering is successfully established after you see **Connected** in the **Peering status** column for both virtual networks in the peering. Any Azure resources you create in either virtual network are now able to communicate with each other through their IP addresses. If you're using subnet-1 Azure name resolution for the virtual networks, the resources in the virtual networks aren't able to resolve names across the virtual networks. If you want to resolve names across virtual networks in a peering, you must create your own DNS (Domain Name System) server or use Azure DNS.
 
 > [!IMPORTANT]
 > If you update the address space in one of the members of the peer, you must resync the connection to reflect the address space changes. For more information, see [Update the address space for a peered virtual network using the Azure portal](/azure/virtual-network/update-virtual-network-peering-address-space#modify-the-address-range-prefix-of-an-existing-address-range)
