Merge pull request #296545 from mbender-ms/lb-combine-us399097

load balancer | Major Maintenance | migrate 3 articles to combined tabs article

Author: denrea

articles/load-balancer/.openpublishing.redirection.load-balancer.json

@@ -379,6 +379,21 @@
             "source_path_from_root": "/articles/load-balancer/upgrade-internalbasic-to-publicstandard.md",
             "redirect_url": "/azure/load-balancer/upgrade-basic-standard-with-powershell",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/load-balancer/tutorial-gateway-portal.md",
+            "redirect_url": "/azure/load-balancer/tutorial-create-gateway-load-balancer",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/load-balancer/tutorial-gateway-cli.md",
+            "redirect_url": "/azure/load-balancer/tutorial-create-gateway-load-balancer",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/load-balancer/tutorial-gateway-powershell.md",
+            "redirect_url": "/azure/load-balancer/tutorial-create-gateway-load-balancer",
+            "redirect_document_id": false
         }
     ]
 }

articles/load-balancer/TOC.yml

@@ -87,12 +87,8 @@
     items:
     - name: Partners
       href: gateway-partners.md
-    - name: Create gateway load balancer - Portal
-      href: tutorial-gateway-portal.md
-    - name: Create gateway load balancer - PowerShell
-      href: tutorial-gateway-powershell.md
-    - name: Create gateway load balancer - Azure CLI
-      href: tutorial-gateway-cli.md
+    - name: Create gateway load balancer
+      href: tutorial-create-gateway-load-balancer.md
     - name: Deploy a dual-stack gateway load balancer
       href: gateway-deploy-dual-stack-load-balancer.md
     - name: Configure outbound connectivity with a gateway load balancer

articles/load-balancer/egress-only.md

@@ -31,6 +31,8 @@ This configuration provides outbound NAT for an internal load balancer scenario,
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 
+## Create a virtual network and bastion host
+
 [!INCLUDE [load-balancer-create-no-gateway](../../includes/load-balancer-create-no-gateway.md)]
 
 ## Create internal load balancer

articles/load-balancer/gateway-deploy-dual-stack-load-balancer.md

@@ -34,7 +34,7 @@ Along with the Gateway Load Balancer, this scenario includes the following alrea
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 - An existing dual-stack load balancer. For more information on creating a dual-stack load balancer, see [Deploy IPv6 dual stack application - Standard Load Balancer](virtual-network-ipv4-ipv6-dual-stack-standard-load-balancer-powershell.md).
-- An existing IPv4 gateway balancer. For more information on creating a gateway load balancer, see [Create a gateway load balancer](./tutorial-gateway-powershell.md).
+- An existing IPv4 gateway balancer. For more information on creating a gateway load balancer, see [Create a gateway load balancer](./Tutorial-create-gateway-load-balancer.md).
 
 ## Add IPv6 address ranges to an existing subnet
 

articles/load-balancer/gateway-overview.md

@@ -42,7 +42,7 @@ Gateway Load Balancer has the following benefits:
 
 ## Configuration and supported scenarios
 
-A Standard Public Load balancer or a Standard IP configuration of a virtual machine can be chained to a Gateway Load Balancer. "Chaining" refers to the load balancer frontend or NIC IP configuration containing a reference to a Gateway Load Balancer frontend IP configuration. Once the Gateway Load Balancer is chained to a consumer resource, no additional configuration such as UDRs are needed to ensure traffic to and from the application endpoint is sent to the Gateway Load Balancer.
+A Standard Public Load balancer or a Standard IP configuration of a virtual machine can be chained to a Gateway Load Balancer. "Chaining" refers to the load balancer frontend or NIC IP configuration containing a reference to a Gateway Load Balancer frontend IP configuration. Once the Gateway Load Balancer is chained to a consumer resource, no additional configuration such as UDRs is needed to ensure traffic to and from the application endpoint is sent to the Gateway Load Balancer.
 
 Gateway Load Balancer supports both inbound and outbound traffic inspection. For inserting NVAs in the path of outbound traffic with Standard Load Balancer, Gateway Load Balancer must be chained to the frontend IP configurations selected in the configured outbound rules.
 
@@ -85,6 +85,6 @@ For pricing, see [Load Balancer pricing](https://azure.microsoft.com/pricing/det
 
 ## Next steps
 
-- See [Create a Gateway Load Balancer using the Azure portal](tutorial-gateway-portal.md) to create a gateway load balancer.
+- See [Create a Gateway Load Balancer using the Azure portal](tutorial-create-gateway-load-balancer.md) to create a gateway load balancer.
 - Learn how to use [Gateway Load Balancer for outbound connectivity scenarios](tutorial-gateway-outbound-connectivity.md).
 - Learn more about [Azure Load Balancer](load-balancer-overview.md).

articles/load-balancer/gateway-partners.md

@@ -122,5 +122,5 @@ Azure has a growing ecosystem of partners offering their network appliances for
 
 ## Next steps
 
-* [Create a Azure Gateway Load Balancer](tutorial-gateway-portal.md)
+* [Create a Azure Gateway Load Balancer](tutorial-create-gateway-load-balancer.md)
 * [What is Azure Gateway Load Balancer?](gateway-overview.md)

articles/load-balancer/load-balancer-best-practices.md

@@ -36,6 +36,7 @@ The following best practices are recommended to ensure the reliability of your A
 #### Deploy with zone-redundancy
 
 Zone-redundancy provides the best resiliency by protecting the data path from zone failure. The load balancer's availability zone selection is synonymous with its frontend IP's zone selection. For public load balancers, if the public IP in the load balancer's frontend is zone redundant then the load balancer is also zone-redundant.
+
 - Deploy load balancer in a region that supports availability zones and enable Zone-redundant when creating a new Public IP address used for the Frontend IP configuration.
 - Public IP addresses can't be changed to zone redundant but we're updating all non-zonal Standard Public IPs to be zone redundant by default. For more information, visit the following Microsoft Azure Blog [Azure Public IPs are now zone-redundant by default | Microsoft Azure Blog](https://azure.microsoft.com/blog/azure-public-ips-are-now-zone-redundant-by-default/?msockid=028aa4446a5a601f37ecb0076b7761c7). To see the most updated list of regions that support zone redundant Standard Public IPs by default, see [Public IP addresses in Azure](../virtual-network/ip-services/public-ip-addresses.md)
 - If you can't deploy as zone-redundant, the next option is to have a zonal load balancer deployment.
@@ -44,7 +45,7 @@ Zone-redundancy provides the best resiliency by protecting the data path from zo
 
 #### Redundancy in your backend pool
 
-Ensure that the backend pool contains at least two instances. If your backend pool only has one instance and it's unhealthy, all traffic sent to the backend pool fails due to lack of redundancy. The Standard Load Balancer SLA is also only supported when there are at least 2 healthy backend pool instances per backend pool. Visit the [SLA documentation](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services?lang=1) for more information.    
+Ensure that the backend pool contains at least two instances. If your backend pool only has one instance and it's unhealthy, all traffic sent to the backend pool fails due to lack of redundancy. The Standard Load Balancer SLA is also only supported when there are at least two healthy backend pool instances per backend pool. Visit the [SLA documentation](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services?lang=1) for more information.    
 
 #### Deploy a global load balancer
 
@@ -58,15 +59,15 @@ The following best practices are recommended to ensure the reliability of your G
 
 #### Chain your Gateway Load Balancer to a Standard Public Load Balancer
 
-Chaining your Gateway Load Balancer to a Standard Public Load Balancer is recommended. This configuration provides high availability and redundancy on both the NVA and application layer. For more information, see [Tutorial: Create a gateway load balancer](./tutorial-gateway-portal.md)
+Chaining your Gateway Load Balancer to a Standard Public Load Balancer is recommended. This configuration provides high availability and redundancy on both the NVA and application layer. For more information, see [Tutorial: Create a gateway load balancer](./tutorial-create-gateway-load-balancer.md)
 
 #### Use a Gateway load balancer when using NVAs instead of a dual load balancer set-up.
 
 We recommend using a Gateway load balancer in north-south traffic scenarios with partner Network Virtual Appliances (NVAs). It's easier to deploy because Gateway load balancers don’t require extra configuration such as user-defined routes (UDRs) because it maintains flow stickiness and flow symmetry. It's also easier to manage because NVAs can be easily added and removed. For more information, see the [Gateway Load Balancer documentation](gateway-overview.md).
 
 ## Configuration guidance
 
-The following configuration guidance are best practices for configuring your Azure Load Balancer deployments. 
+The following configuration guidance is best practices for configuring your Azure Load Balancer deployments. 
 
 ### Create Network Security Groups (NSGs)
 

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

@@ -63,7 +63,7 @@ Key scenarios that you can accomplish by using Azure Standard Load Balancer incl
 
 - Load balance TCP and UDP flow on all ports simultaneously by using [high-availability ports](./load-balancer-ha-ports-overview.md).
 
-- Chain Standard Load Balancer and [Gateway Load Balancer](./tutorial-gateway-portal.md).
+- Chain Standard Load Balancer and [Gateway Load Balancer](./tutorial-create-gateway-load-balancer.md).
 
 ### <a name="securebydefault"></a>Security by default