Updates based on Mahip's comments

Author: Michael Bender

articles/load-balancer/cross-subscription-how-to-attach-backend.md

@@ -14,7 +14,7 @@ ms.custom:
 # Attach a cross-subscription backend to an Azure Load Balancer
 In this article, you learn how to attach a cross-subscription backend to an Azure Load Balancer by creating a cross-subscription backend pool and attaching cross-subscription network interfaces to the backend pool of the load balancer.
 
-A [cross-subscription internal load balancer (ILB)](cross-subscription-load-balancer-overview.md) can reference a virtual network that resides in a different subscription other than the load balancers. This feature allows you to deploy a load balancer in one subscription and reference a virtual network in another subscription.
+A [cross-subscription load balancer](cross-subscription-load-balancer-overview.md) can reference a virtual network that resides in a different subscription other than the load balancers. This feature allows you to deploy a load balancer in one subscription and reference a virtual network in another subscription.
 
 [!INCLUDE [load-balancer-cross-subscription-preview](../../includes/load-balancer-cross-subscription-preview.md)]
 

articles/load-balancer/cross-subscription-how-to-attach-frontend.md

@@ -134,13 +134,20 @@ Create a load balancer with [`New-AzLoadBalancer`](/powershell/module/az.network
 
 ```azurepowershell
 # Create a load balancer
+
+$tags = @{
+'IsRemoteFrontend'= 'true'
+}
+
 $loadbalancer = @{
     ResourceGroupName = 'myResourceGroupLB'
     Name = 'myLoadBalancer'
     Location = 'westus'
     Sku = 'Standard'
+    Tag = $tags
 }
 
+
 $LB = New-AzLoadBalancer @loadbalancer
  
 $LBinfo = @{

articles/load-balancer/cross-subscription-howto-internal-load-balancer.md

@@ -27,7 +27,7 @@ A [cross-subscription internal load balancer (ILB)](cross-subscription-load-bala
 
 ## Create a load balancer 
 
-In this section, you create a load balancer in **Azure Subscription B**. You create a load balancer with a frontend IP address.
+In this section, you create a load balancer in **Azure Subscription B** that is connected to a virtual network in **Azure Subscription A**. You create a load balancer with a frontend IP address.
 
 # [Azure PowerShell](#tab/azurepowershell)
 With Azure PowerShell, you'll:
@@ -39,11 +39,17 @@ With Azure PowerShell, you'll:
 
 ```azurepowershell
 # Create a load balancer
+
+$tags = @{
+'IsRemoteFrontend'= 'true'
+}
+
 $loadbalancer = @{
     ResourceGroupName = 'myResourceGroupLB'
     Name = 'myLoadBalancer'
     Location = 'westus'
     Sku = 'Standard'
+    Tags = $tags
 }
 
 $LB = New-AzLoadBalancer @loadbalancer

articles/load-balancer/cross-subscription-load-balancer-overview.md

@@ -63,7 +63,7 @@ With syncMode configured as “Manual”, backend pool instances aren't synchron
 
 ## Cross-subscription Global Load Balancer
 
-In addition to, cross-subscription load balancing is supported for Azure global Load Balancer. With cross-subscription global load balancer, backend regional load balancers can each be located in different subscriptions. Cross-subscription backends on a global load balancer don't need other parameters or changes to the backend pool.
+In addition, cross-subscription load balancing is supported for Azure global Load Balancer. With cross-subscription global load balancer, backend regional load balancers can each be located in different subscriptions. Cross-subscription backends on a global load balancer don't need other parameters or changes to the backend pool.
 
 :::image type="content" source="media/cross-subscription-load-balancer-overview/global-load-balancer-cross-subscription-concept.png" alt-text="Diagram of cross subscription global load balancer concept":::
 
@@ -89,7 +89,7 @@ Microsoft.Network/virtualNetworks/write
 Microsoft.Network/networkInterfaces/write
 
 ### Cross-tenant  
-When working cross-tenant, a user must be assigned to the *Network Contributor* role or to a custom role that is assigned the appropriate actions for cross-subscription frontends in both subscriptions. More information on cross-tenant linkage can be found here. 
+When working cross-tenant, a user must be assigned to the *Network Contributor* role or to a custom role that is assigned the appropriate actions for cross-subscription frontends in both subscriptions. More information on cross-tenant linkage, see [Authenticate requests across tenants](../azure-resource-manager/management/authenticate-multi-tenant.md). 
 
 ## Limitations 
 - syncMode can only be set on new backend pools 

includes/load-balancer-cross-subscription-add-nic.md

@@ -14,7 +14,10 @@ ms.custom: include-file
 ## Attach network interface cards to the load balancer
 
 # [Azure PowerShell](#tab/azurepowershell)
-In this section, you attach network interface cards to the load balancer. You create a network interface with [`New-AzNetworkInterface`](/powershell/module/az.network/new-aznetworkinterface) and then create an IP configuration for the network interface card with [`New-AzNetworkInterfaceIpConfig`](/powershell/module/az.network/new-aznetworkinterfaceipconfig).
+In this section, you attach the network interface card (NIC) in **Azure Subscription A** to the load balancer in **Azure Subscription B**. You create a network interface with [`New-AzNetworkInterface`](/powershell/module/az.network/new-aznetworkinterface) and then create an IP configuration for the network interface card with [`New-AzNetworkInterfaceIpConfig`](/powershell/module/az.network/new-aznetworkinterfaceipconfig).
+
+> [!NOTE]
+> The network interface card (NIC) must be in the same VNet as the load balancer’s backend pool.
 
 ```azurepowershell
 
@@ -40,6 +43,16 @@ New-AzNetworkInterface @nic
 
 # [Azure CLI](#tab/azurecli)
 
-This step is only performed with Azure PowerShell. It's unnecessary with Azure CLI.
+In this section, you attach the network interface card (NIC) in **Azure Subscription A** to the load balancer in **Azure Subscription B** with [`az network nic create`](/cli/azure/network/nic#az-network-nic-create)
+
+> [!NOTE]
+> The network interface card (NIC) must be in the same VNet as the load balancer’s backend pool.
 
+```azurecli
+# Set the subscription context to **Azure Subscription A**
+Az account set –subscription 'Sub A'
+
+# Attach the network interface card to the load balancer
+az network nic create --name NIC --resource-group NIC-rg --vnet VNET-name --lb-address-pool "/subscriptions/<Subscription B ID>/resourceGroups/myResourceGroupLB/providers/Microsoft.Network/loadBalancers/myLoadBalancer/backendAddressPools/BackendPool1"
+```
 ---