updated includes

Author: Michael Bender

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

@@ -11,10 +11,11 @@ ms.author: mbender
 ms.custom: 
 ---
 
-A cross-subscription load balancer allows the public IP address to reside in a different subscription other than the load balancers.
-
+# Attach a cross-subscription backend to an Azure Load Balancer
 In this article, you will 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.
+
 [!INCLUDE [load-balancer-cross-subscription-preview](../../includes/load-balancer-cross-subscription-preview.md)]
 
 [!INCLUDE [load-balancer-cross-subscription-prerequisites](../../includes/load-balancer-cross-subscription-prerequisites.md)]
@@ -94,44 +95,8 @@ $LB = Get-AzLoadBalancer @LBinfo
 # [Azure CLI](#tab/azurecli)
 
 ---
-## Create a health probe and load balancer rule
-
-Create a health probe that determines the health of the backend VM instances and a load balancer rule that defines the frontend IP configuration for the incoming traffic, the backend IP pool to receive the traffic, and the required source and destination port.
-
-# [Azure PowerShell](#tab/azurepowershell)
-
-With Azure PowerShell, create a health probe with [`Add-AzLoadBalancerProbeConfig`](/powershell/module/az.network/add-azloadbalancerprobeconfig) that determines the health of the backend VM instances. Then create a load balancer rule with [`Add-AzLoadBalancerRuleConfig`](/powershell/module/az.network/add-azloadbalancerruleconfig) that defines the frontend IP configuration for the incoming traffic, the backend IP pool to receive the traffic, and the required source and destination port.
 
-```azurepowershell
-## Create the health probe and place in variable
-$probe = @{
-    Name = 'myHealthProbe2'
-    Protocol = 'tcp'
-    Port = '80'
-    IntervalInSeconds = '360'
-    ProbeCount = '5'
-}
-$LB | Add-AzLoadBalancerProbeConfig @probe
-
-## Create the load balancer rule and place in variable
-$lbrule = @{
-    Name = 'myHTTPRule2'
-    Protocol = 'tcp'
-    FrontendPort = '80'
-    BackendPort = '80'
-    IdleTimeoutInMinutes = '15'
-    FrontendIpConfiguration = $LB.FrontendIpConfigurations[0]
-    BackendAddressPool = $backend
-}
-$LB | Add-AzLoadBalancerRuleConfig  @lbrule
-
-## Set the load balancer resource
-$LB | Set-AzLoadBalancer
-```
-
-# [Azure CLI](#tab/azurecli)
-
----
+[!INCLUDE [load-balancer-cross-subscription-health-probe-rules](../../includes/load-balancer-cross-subscription-health-probe-rules.md)]
 
 [!INCLUDE [load-balancer-cross-subscription-add-nic](../../includes/load-balancer-cross-subscription-add-nic.md)]
 

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

@@ -13,10 +13,10 @@ ms.custom:
 
 # Attach a cross-subscription frontend to an Azure Load Balancer
 
-A cross-subscription load balancer allows the public IP address to reside in a different subscription other than the load balancers.
-
 In this article, you learn how to create a load balancer in one Azure subscription and attach a frontend IP address from another subscription. You create a resource group for the load balancer and then create a load balancer with a frontend IP address. You also create a backend address pool, health probe, and load balancer rule.
 
+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. s.
+
 [!INCLUDE [load-balancer-cross-subscription-preview](../../includes/load-balancer-cross-subscription-preview.md)]
 
 ## Prerequisites
@@ -201,70 +201,9 @@ az network lb address-pool update --lb-name myLoadBalancer --resource-group myRe
 
 ---
 
-## Create a health probe and load balancer rule
-
-Create a health probe that determines the health of the backend VM instances and a load balancer rule that defines the frontend IP configuration for the incoming traffic, the backend IP pool to receive the traffic, and the required source and destination port.
-
-# [Azure PowerShell](#tab/azurepowershell)
-
-With Azure PowerShell, create a health probe with [`Add-AzLoadBalancerProbeConfig`](/powershell/module/az.network/add-azloadbalancerprobeconfig) that determines the health of the backend VM instances. Then create a load balancer rule with [`Add-AzLoadBalancerRuleConfig`](/powershell/module/az.network/add-azloadbalancerruleconfig) that defines the frontend IP configuration for the incoming traffic, the backend IP pool to receive the traffic, and the required source and destination port.
-
-```azurepowershell
-## Create the health probe and place in variable. ##
-$probe = @{
-    Name = 'myHealthProbe2'
-    Protocol = 'tcp'
-    Port = '80'
-    IntervalInSeconds = '360'
-    ProbeCount = '5'
-}
-
-## Create the load balancer rule and place in variable. ##
-$lbrule = @{
-    Name = 'myHTTPRule2'
-    Protocol = 'tcp'
-    FrontendPort = '80'
-    BackendPort = '80'
-    IdleTimeoutInMinutes = '15'
-    FrontendIpConfiguration = $LB.FrontendIpConfigurations[0]
-    BackendAddressPool = $backend
-}
-## Set the load balancer resource. ##
-$LB | Add-AzLoadBalancerProbeConfig @probe
-$LB | Add-AzLoadBalancerRuleConfig  @lbrule
-$LB | Set-AzLoadBalancer
-```
-# [Azure CLI](#tab/azurecli/)
-
-With Azure CLI, create a health probe with [`az network lb probe create`](/cli/azure/network/lb/probe#az_network_lb_probe_create) that determines the health of the backend VM instances. Then create a load balancer rule with [`az network lb rule create`](/cli/azure/network/lb/rule#az_network_lb_rule_create) that defines the frontend IP configuration for the incoming traffic, the backend IP pool to receive the traffic, and the required source and destination port.
-
-```azurecli
-# Create a health probe
-az network lb probe create --resource-group myResourceGroupLB --lb-name myLoadBalancer --name myHealthProbe --protocol tcp --port 80
-
-# Create a load balancer rule
-az network lb rule create --resource-group myResourceGroupLB --lb-name myLoadBalancer --name myHTTPRule --protocol tcp --frontend-port 80 --backend-port 80 --frontend-ip-name myFrontEnd --backend-pool-name myBackEndPool --probe-name myHealthProbe --disable-outbound-snat true --idle-timeout 15 --enable-tcp-reset true
-
-```
-
----
-
-## Clean up resources
-
-When no longer needed, you can use the Remove-AzResourceGroup command to remove the resource group, load balancer, and the remaining resources.
-
-# [Azure PowerShell](#tab/azurepowershell)
-
-```azurepowershell
-Remove-AzResourceGroup -Name myResourceGroupLB
-```
+[!INCLUDE [load-balancer-cross-subscription-health-probe-rules](../../includes/load-balancer-cross-subscription-health-probe-rules.md)]
 
-# [Azure CLI](#tab/azurecli)
-
-```azurecli
-az group delete --name myResourceGroupLB
-```
----
+[!INCLUDE [load-balancer-cross-subscription-clean-up](../../includes/load-balancer-cross-subscription-clean-up.md)]
 
 ## Next steps
 

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

@@ -13,10 +13,10 @@ ms.custom:
 
 # Create a cross-subscription internal 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. 
-
 In this how-to guide, you learn how to create a cross-subscription internal load balancer by connecting a virtual network in a subscription to a load balancer in a different subscription.
 
+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. 
+
 [!INCLUDE [load-balancer-cross-subscription-preview](../../includes/load-balancer-cross-subscription-preview.md)]
 
 [!INCLUDE [load-balancer-cross-subscription-prerequisites](../../includes/load-balancer-cross-subscription-prerequisites.md)]
@@ -101,53 +101,7 @@ az network lb address-pool update --lb-name myLoadBalancer --resource-group myRe
 ```
 ---
 
-## Create a health probe and load balancer rule
-
-Create a health probe that determines the health of the backend VM instances and a load balancer rule that defines the frontend IP configuration for the incoming traffic, the backend IP pool to receive the traffic, and the required source and destination port.
-
-# [Azure PowerShell](#tab/azurepowershell)
-
-With Azure PowerShell, create a health probe with [`Add-AzLoadBalancerProbeConfig`](/powershell/module/az.network/add-azloadbalancerprobeconfig) that determines the health of the backend VM instances. Then create a load balancer rule with [`Add-AzLoadBalancerRuleConfig`](/powershell/module/az.network/add-azloadbalancerruleconfig) that defines the frontend IP configuration for the incoming traffic, the backend IP pool to receive the traffic, and the required source and destination port.
-
-```azurepowershell
-## Create the health probe and place in variable. ##
-$probe = @{
-    Name = 'myHealthProbe2'
-    Protocol = 'tcp'
-    Port = '80'
-    IntervalInSeconds = '360'
-    ProbeCount = '5'
-}
-
-## Create the load balancer rule and place in variable. ##
-$lbrule = @{
-    Name = 'myHTTPRule2'
-    Protocol = 'tcp'
-    FrontendPort = '80'
-    BackendPort = '80'
-    IdleTimeoutInMinutes = '15'
-    FrontendIpConfiguration = $LB.FrontendIpConfigurations[0]
-    BackendAddressPool = $backend
-}
-## Set the load balancer resource. ##
-$LB | Add-AzLoadBalancerProbeConfig @probe
-$LB | Add-AzLoadBalancerRuleConfig  @lbrule
-$LB | Set-AzLoadBalancer
-```
-# [Azure CLI](#tab/azurecli/)
-
-With Azure CLI, create a health probe with [`az network lb probe create`](/cli/azure/network/lb/probe#az_network_lb_probe_create) that determines the health of the backend VM instances. Then create a load balancer rule with [`az network lb rule create`](/cli/azure/network/lb/rule#az_network_lb_rule_create) that defines the frontend IP configuration for the incoming traffic, the backend IP pool to receive the traffic, and the required source and destination port.
-
-```azurecli
-# Create a health probe
-az network lb probe create --resource-group myResourceGroupLB --lb-name myLoadBalancer --name myHealthProbe --protocol tcp --port 80
-
-# Create a load balancer rule
-az network lb rule create --resource-group myResourceGroupLB --lb-name myLoadBalancer --name myHTTPRule --protocol tcp --frontend-port 80 --backend-port 80 --frontend-ip-name myFrontEnd --backend-pool-name myBackEndPool --probe-name myHealthProbe --disable-outbound-snat true --idle-timeout 15 --enable-tcp-reset true
-
-```
-
----
+[!INCLUDE [load-balancer-cross-subscription-health-probe-rules](../../includes/load-balancer-cross-subscription-health-probe-rules.md)]
 
 [!INCLUDE [load-balancer-cross-subscription-add-nic](../../includes/load-balancer-cross-subscription-add-nic.md)]
 

includes/load-balancer-cross-subscription-health-probe-rules.md

@@ -0,0 +1,59 @@
+---
+ title: include file
+ description: include file
+ services: load-balancer
+ author: mbender
+ ms.service: load-balancer
+ ms.topic: include
+ ms.date: 05/31/2024
+ ms.author: mbender-ms
+ms.custom: include-file
+---
+
+## Create a health probe and load balancer rule
+
+Create a health probe that determines the health of the backend VM instances and a load balancer rule that defines the frontend IP configuration for the incoming traffic, the backend IP pool to receive the traffic, and the required source and destination port.
+
+# [Azure PowerShell](#tab/azurepowershell)
+
+With Azure PowerShell, create a health probe with [`Add-AzLoadBalancerProbeConfig`](/powershell/module/az.network/add-azloadbalancerprobeconfig) that determines the health of the backend VM instances. Then create a load balancer rule with [`Add-AzLoadBalancerRuleConfig`](/powershell/module/az.network/add-azloadbalancerruleconfig) that defines the frontend IP configuration for the incoming traffic, the backend IP pool to receive the traffic, and the required source and destination port.
+
+```azurepowershell
+## Create the health probe and place in variable. ##
+$probe = @{
+    Name = 'myHealthProbe2'
+    Protocol = 'tcp'
+    Port = '80'
+    IntervalInSeconds = '360'
+    ProbeCount = '5'
+}
+
+## Create the load balancer rule and place in variable. ##
+$lbrule = @{
+    Name = 'myHTTPRule2'
+    Protocol = 'tcp'
+    FrontendPort = '80'
+    BackendPort = '80'
+    IdleTimeoutInMinutes = '15'
+    FrontendIpConfiguration = $LB.FrontendIpConfigurations[0]
+    BackendAddressPool = $backend
+}
+## Set the load balancer resource. ##
+$LB | Add-AzLoadBalancerProbeConfig @probe
+$LB | Add-AzLoadBalancerRuleConfig  @lbrule
+$LB | Set-AzLoadBalancer
+```
+# [Azure CLI](#tab/azurecli/)
+
+With Azure CLI, create a health probe with [`az network lb probe create`](/cli/azure/network/lb/probe#az_network_lb_probe_create) that determines the health of the backend VM instances. Then create a load balancer rule with [`az network lb rule create`](/cli/azure/network/lb/rule#az_network_lb_rule_create) that defines the frontend IP configuration for the incoming traffic, the backend IP pool to receive the traffic, and the required source and destination port.
+
+```azurecli
+# Create a health probe
+az network lb probe create --resource-group myResourceGroupLB --lb-name myLoadBalancer --name myHealthProbe --protocol tcp --port 80
+
+# Create a load balancer rule
+az network lb rule create --resource-group myResourceGroupLB --lb-name myLoadBalancer --name myHTTPRule --protocol tcp --frontend-port 80 --backend-port 80 --frontend-ip-name myFrontEnd --backend-pool-name myBackEndPool --probe-name myHealthProbe --disable-outbound-snat true --idle-timeout 15 --enable-tcp-reset true
+
+```
+
+---

includes/load-balancer-cross-subscription-prerequisites.md

@@ -16,7 +16,7 @@ ms.custom: include-file
 
 - Two Azure subscriptions. One subscription for the virtual network and another subscription for the load balancer.
 - An Azure account with active subscriptions. [Create an account for free](https://azure.microsoft.com/free/)
-- An existing [Virtual Network](../virtual-network/quick-create-powershell.md). deployed in one of the subscriptions. For this example, the virtual network is in **Azure Subscription A**.
+- An existing [Virtual Network](../articles/virtual-network/quick-create-powershell.md). deployed in one of the subscriptions. For this example, the virtual network is in **Azure Subscription A**.
 
 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. If you're running PowerShell locally, you also need to run `Connect-AzAccount` to create a connection with Azure.
 
@@ -27,11 +27,11 @@ If you choose to install and use PowerShell locally, this article requires the A
   
 # [Azure CLI](#tab/azurecli/)
 
-[!INCLUDE [azure-cli-prepare-your-environment.md](~/reusable-content/azure-cli/azure-cli-prepare-your-environment-no-header.md)]
-
 - Two Azure subscriptions. One subscription for the virtual network (**Azure Subscription A**) and another subscription for the load balancer(**Azure Subscription B**).
 - An Azure account with active subscriptions. [Create an account for free](https://azure.microsoft.com/free/)
-- An existing [Virtual Network](../virtual-network/quick-create-cli.md). deployed in one of the subscriptions. For this example, the virtual network is in **Azure Subscription A**.
+- An existing [Virtual Network](../articles/virtual-network/quick-create-cli.md). deployed in one of the subscriptions. For this example, the virtual network is in **Azure Subscription A**.
+
+[!INCLUDE [azure-cli-prepare-your-environment.md](~/reusable-content/azure-cli/azure-cli-prepare-your-environment-no-header.md)]
 
 If you choose to install and use the CLI locally, this quickstart requires Azure CLI version 2.60 or later. To find the version, run az --version. If you need to install or upgrade, see Install the Azure CLI.