Updates from pre-review - New Images - Renamed files

Author: Michael Bender

articles/load-balancer/TOC.yml

@@ -106,6 +106,8 @@
     href: distribution-mode-concepts.md
   - name: Health probes
     href: load-balancer-custom-probe-overview.md
+  - name: Cross-subscription load balancer
+    href: cross-subscription-overview.md
   - name: Cross-region load balancer
     href: cross-region-overview.md
   - name: Reliability
@@ -224,6 +226,17 @@
       href: move-across-regions-internal-load-balancer-portal.md
     - name: Internal load balancer - PowerShell
       href: move-across-regions-internal-load-balancer-powershell.md
+  - name: Cross-subscription load balancing
+    items:
+    - name: Attach a cross-subscription backend to an Azure Load Balancer
+      href: cross-subscription-how-to-attach-backend.md
+    - name: Attach a cross-subscription frontend to an Azure Load Balancer
+      href: cross-subscription-how-to-attach-frontend.md
+    - name: Create a global load balancer with cross-subscription backends
+      href: cross-subscription-how-to-global-backend.md
+    - name: Create a cross-subscription internal load balancer
+      href: cross-subscription-how-to-internal-load-balancer.md
+    
   - name: IPv6
     items:
     - name: Configure DHCPv6 for Linux VMs

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

@@ -6,15 +6,15 @@ services: load-balancer
 author: mbender-ms
 ms.service: load-balancer
 ms.topic: how-to
-ms.date: 05/31/2024
+ms.date: 06/18/2024
 ms.author: mbender
 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 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.
+A [cross-subscription load balancer](cross-subscription-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)]
 
@@ -124,4 +124,4 @@ az network lb address-pool update --lb-name myLoadBalancer --resource-group myRe
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Create a cross-subscription internal load balancer](./cross-subscription-howto-internal-load-balancer.md)
+> [Create a cross-subscription internal load balancer](./cross-subscription-how-to-internal-load-balancer.md)

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

@@ -6,7 +6,7 @@ services: load-balancer
 author: mbender-ms
 ms.service: load-balancer
 ms.topic: how-to
-ms.date: 05/24/2024
+ms.date: 06/18/2024
 ms.author: mbender
 ms.custom: 
 ---
@@ -15,7 +15,7 @@ ms.custom:
 
 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.
+A [cross-subscription load balancer](cross-subscription-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)]
 
@@ -215,4 +215,4 @@ az network lb address-pool update --lb-name myLoadBalancer --resource-group myRe
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Create a cross-subscription internal load balancer](./cross-subscription-howto-internal-load-balancer.md)
+> [Create a cross-subscription internal load balancer](./cross-subscription-how-to-internal-load-balancer.md)

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

@@ -6,7 +6,7 @@ services: load-balancer
 author: mbender-ms
 ms.service: load-balancer
 ms.topic: how-to
-ms.date: 05/24/2024
+ms.date: 06/18/2024
 ms.author: mbender
 ms.custom: 
 ---
@@ -15,7 +15,7 @@ ms.custom:
 
 In this article, you learn how to create a global load balancer with cross-subscription backends.
 
-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-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)]
 
@@ -261,7 +261,7 @@ az network cross-region-lb address-pool address add \
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Create a cross-subscription internal load balancer](./cross-subscription-howto-internal-load-balancer.md)
+> [Create a cross-subscription internal load balancer](./cross-subscription-how-to-internal-load-balancer.md)
 
 
 

articles/load-balancer/cross-subscription-howto-internal-load-balancer.md renamed to articles/load-balancer/cross-subscription-how-to-internal-load-balancer.md

@@ -5,7 +5,7 @@ services: load-balancer
 author: mbender-ms
 ms.service: load-balancer
 ms.topic: how-to
-ms.date: 05/24/2024
+ms.date: 06/18/2024
 ms.author: mbender
 ms.custom:
 #CustomerIntent: As a < type of user >, I want < what? > so that < why? > .
@@ -15,7 +15,7 @@ ms.custom:
 
 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. 
+A [cross-subscription internal load balancer (ILB)](cross-subscription-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-load-balancer-overview.md renamed to articles/load-balancer/cross-subscription-overview.md

@@ -6,7 +6,7 @@ services: load-balancer
 author: mbender-ms
 ms.service: load-balancer
 ms.topic: overview
-ms.date: 05/24/2024
+ms.date: 06/18/2024
 ms.author: mbender
 ms.custom: 
 ---
@@ -22,7 +22,7 @@ This article provides an overview of cross-subscription load balancing with Azur
 
 Cross-subscription load balancing allows you to deploy Azure Load Balancer resources across multiple subscriptions. This feature enables you to deploy a load balancer in one subscription and have the frontend IP and backend pool instances in a different subscription. This capability is useful for organizations that have separate subscriptions for networking and application resources.
 
-:::image type="content" source="media/cross-subscription-load-balancer-overview/cross-subscription-load-balancer-concept.png" alt-text="Diagram of cross-subscription load balancer concepts with two subscriptions and resources.":::
+:::image type="content" source="media/cross-subscription-load-balancer-overview/cross-subscription-load-balancer-concept-thumbnail.png" alt-text="Diagram of cross-subscription load balancer concepts with two subscriptions and resources." lightbox="media/cross-subscription-load-balancer-overview/global-load-balancer-cross-subscription-concept.png":::
 
 The table below illustrates some of the possible scenarios cross-subscription load balancing supports. 
 
@@ -33,7 +33,7 @@ The table below illustrates some of the possible scenarios cross-subscription lo
 | Load Balancer and Frontend IP address | Backend pool resources |
 
 ## Cross-subscription frontend IP configurations
-Cross-subscription frontends allow the frontend IP configuration to reside in a different subscription other than the load balancer’s subscription. To enable cross-subscription frontend IP configurations, the following tag needs to be set to true: “IsRemoteFrontend: True”, and the syncMode property needs to be enabled on the backend pool. 
+Cross-subscription frontends allow the frontend IP configuration to reside in a different subscription other than the load balancer’s subscription. To enable cross-subscription frontend IP configurations, the following tag needs to be set to true: “IsRemoteFrontend: True”, and the SyncMode property needs to be enabled on the backend pool. 
 
 ### Public frontend IP configurations 
 Public IP addresses utilized by an Azure Load Balancer can reside in different subscription than the load balancer. If multiple public IP addresses are attached to a load balancer, each IP address can come from a different subscription. For example, if we have a Load Balancer (deployed in subscription C) with two frontend IPs, the first IP address can reside in subscription B and the second IP address can reside in subscription A.   
@@ -48,26 +48,26 @@ Like public load balancers, internal load balancers can also have cross-subscrip
 
 ## Cross-subscription backend pools
 Cross-subscription backends allow backend instances to reside in a different subscription other than the load balancer’s subscription. For example, the load balancer could be in subscription 1 and my backend VMs could be located in subscription 2. 
-The backend instances and the virtual network they refer to can be located in a different subscription. Cross-subscription backend pools must utilize a new property known as *syncMode*. 
+The backend instances and the virtual network they refer to can be located in a different subscription. Cross-subscription backend pools must utilize a new property known as *SyncMode*. 
 
-### What is syncMode
-The *syncMode* property is a parameter that you can specify when you create a backend pool by using IP addresses and virtual network IDs. This property must be set when using cross-subscription frontends or backends. It has two possible values: “Automatic” or “Manual”.
-In addition, this property replaces the concept of NIC-based or IP-based backend pools. As a result, backend pools with the syncMode property configured are a distinct type of backend pool, separate from NIC or IP-based backend pools. Backend pools can either be exclusively NIC-based, IP-based, or syncMode enabled.  
+### What is SyncMode
+The *SyncMode* property is a parameter that you can specify when you create a backend pool by using IP addresses and virtual network IDs. This property must be set when using cross-subscription frontends or backends. It has two possible values: “Automatic” or “Manual”.
+In addition, this property replaces the concept of NIC-based or IP-based backend pools. As a result, backend pools with the SyncMode property configured are a distinct type of backend pool, separate from NIC or IP-based backend pools. Backend pools can either be exclusively NIC-based, IP-based, or SyncMode enabled.  
 
-#### When should I use syncMode: “Automatic”?
-With syncMode configured as “Automatic”, backend pool instances are synchronized with the load balancer configuration. As a result, changes to the backend pool instances are automatically reflected in the load balancer’s backend pool configuration. This is relevant when using virtual machine scale sets in the backend pool. When the scale set scales in/out, the backend pool members will automatically be added or removed from the pool accordingly.
-Like NIC (network interface cards) based backend pools, if syncMode is set to “Automatic”, then each backend instance’s NIC must also reference the load balancer backend pool. As a result, backend instances are added to “Automatic” syncMode backend pools by updating the NIC resource’s reference to the load balancer.
+#### When should I use SyncMode: “Automatic”?
+With SyncMode configured as “Automatic”, backend pool instances are synchronized with the load balancer configuration. As a result, changes to the backend pool instances are automatically reflected in the load balancer’s backend pool configuration. This is relevant when using virtual machine scale sets in the backend pool. When the scale set scales in/out, the backend pool members will automatically be added or removed from the pool accordingly.
+Like NIC (network interface cards) based backend pools, if SyncMode is set to “Automatic”, then each backend instance’s NIC must also reference the load balancer backend pool. As a result, backend instances are added to “Automatic” SyncMode backend pools by updating the NIC resource’s reference to the load balancer.
 
-#### When should I use syncMode: “Manual”?
-With syncMode configured as “Manual”, backend pool instances aren't synchronized with the load balancer configuration. This mode allows you to create a backend pool with pre-provisioned private IP addresses that can be used for scenarios such as disaster recovery, active-passive, or dynamic provisioning. When using “Manual” syncMode backend pools, you're responsible for updating the backend pool when any changes to your backend instances occur, such as with a scale set autoscaling.
+#### When should I use SyncMode: “Manual”?
+With SyncMode configured as “Manual”, backend pool instances aren't synchronized with the load balancer configuration. This mode allows you to create a backend pool with pre-provisioned private IP addresses that can be used for scenarios such as disaster recovery, active-passive, or dynamic provisioning. When using “Manual” SyncMode backend pools, you're responsible for updating the backend pool when any changes to your backend instances occur, such as with a scale set autoscaling.
 
 ## Cross-subscription Global Load Balancer
 
 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":::
-
-Note, cross-subscription frontends aren't supported on Azure global Load Balancer today. 
+:::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.":::
+> [!NOTE]
+>  cross-subscription frontends aren't supported on Azure global Load Balancer today. 
  
 ## Authorization
 
@@ -92,11 +92,11 @@ Microsoft.Network/networkInterfaces/write
 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 
-  - The syncMode property must be explicitly set – by default, the syncMode property is unspecified  
+- SyncMode can only be set on new backend pools 
+  - The SyncMode property must be explicitly set – by default, the SyncMode property is unspecified  
 - API version 2023-04-01 and above needs to be used to when deploying/updating the load balancers
-- Once configured, the syncMode property can't be changed on a backend pool 
-- A virtual network must be specified when the syncMode property is configured. Once a virtual network is configured, it can’t be updated on the backend pool 
+- Once configured, the SyncMode property can't be changed on a backend pool 
+- A virtual network must be specified when the SyncMode property is configured. Once a virtual network is configured, it can’t be updated on the backend pool 
 - Inbound NAT pools aren’t supported for cross-subscription load balancers. Utilize inbound NAT rules    
 - All resources must be deployed in the same region as the load balancer
 - SyncMode property isn't supported on cross-region load balancer backend pools