Merge pull request #113640 from anavinahar/patch-245

Update types.md

Author: ttorble

articles/load-balancer/types.md

@@ -1,6 +1,6 @@
 ---
-title: Azure Load Balancer Types
-description: Overview of Azure Load Balancer types
+title: Azure Load Balancer SKUs
+description: Overview of Azure Load Balancer SKUs
 services: load-balancer
 documentationcenter: na
 author: asudbring
@@ -9,49 +9,15 @@ ms.devlang: na
 ms.topic: overview
 ms.tgt_pltfrm: na
 ms.workload: infrastructure-services
-ms.date: 04/30/2020
+ms.date: 05/01/2020
 ms.author: allensu
 
 ---
-# Azure Load Balancer types
+# Azure Load Balancer SKUs
 
-Azure Load Balancer has two types and two SKU's.
+Azure Load Balancer has two flavors or SKUs.
 
-## <a name = "publicloadbalancer"></a>Public load balancer
-
-A public load balancer maps the public IP and port of incoming traffic to the private IP and port of the VM. Load balancer maps traffic the other way around for the response traffic from the VM. You can distribute specific types of traffic across multiple VMs or services by applying load-balancing rules. For example, you can spread the load of web request traffic across multiple web servers.
-
->[!NOTE]
->You can implement only one public load balancer and one internal load balancer per availability set.
-
-The following figure shows a load-balanced endpoint for web traffic that is shared among three VMs for the public and TCP port 80. These three VMs are in a load-balanced set.
-
-![Public load balancer example](./media/load-balancer-overview/load-balancer.png)
-
-*Figure: Balancing web traffic by using a public load balancer*
-
-Internet clients send webpage requests to the public IP address of a web app on TCP port 80. Azure Load Balancer distributes the requests across the three VMs in the load-balanced set. For more information about load balancer algorithms, see [Load balancer concepts](concepts.md).
-
-Azure Load Balancer distributes network traffic equally among multiple VM instances by default. You can also configure session affinity. For more information, see [Configure the distribution mode for Azure Load Balancer](load-balancer-distribution-mode.md).
-
-## <a name = "internalloadbalancer"></a> Internal load balancer
-
-An internal load balancer distributes traffic to resources that are inside a virtual network. Azure restricts access to the front-end IP addresses of a virtual network that are load balanced. 
-
-Front-end IP addresses and virtual networks are never directly exposed to an internet endpoint. Internal line-of-business applications run in Azure and are accessed from within Azure or from on-premises resources.
-
-An internal load balancer enables the following types of load balancing:
-
-* **Within a virtual network**: Load balancing from VMs in the virtual network to a set of VMs that are in the same virtual network.
-* **For a cross-premises virtual network**: Load balancing from on-premises computers to a set of VMs that are in the same virtual network.
-* **For multi-tier applications**: Load balancing for internet-facing multi-tier applications where the back-end tiers aren't internet-facing. The back-end tiers require traffic load balancing from the internet-facing tier. See the next figure.
-* **For line-of-business applications**: Load balancing for line-of-business applications that are hosted in Azure without additional load balancer hardware or software. This scenario includes on-premises servers that are in the set of computers whose traffic is load balanced.
-
-![Internal Load Balancer example](./media/load-balancer-overview/load-balancer.png)
-
-*Figure: Balancing multi-tier applications by using both public and internal load balancer*
-
-## <a name="skus"></a> Load Balancer SKU comparison
+## <a name="skus"></a> SKU comparison
 
 Load balancer supports both Basic and Standard SKUs. These SKUs differ in scenario scale, features, and pricing. Any scenario that's possible with Basic load balancer can be created with Standard load balancer.
 
@@ -61,7 +27,21 @@ To compare and understand the differences, see the following table. For more inf
 > Microsoft recommends Standard load balancer.
 Standalone VMs, availability sets, and virtual machine scale sets can be connected to only one SKU, never both. Load balancer and the public IP address SKU must match when you use them with public IP addresses. Load balancer and public IP SKUs aren't mutable.
 
-[!INCLUDE [comparison table](../../includes/load-balancer-comparison-table.md)]
+| | Standard Load Balancer | Basic Load Balancer |
+| --- | --- | --- |
+| [Backend pool size](https://docs.microsoft.com/azure/azure-resource-manager/management/azure-subscription-service-limits#load-balancer) | Supports up to 1000 instances. | Supports up to 300 instances. |
+| Backend pool endpoints | Any virtual machines or virtual machine scale sets in a single virtual network. | Virtual machines in a single availability set or virtual machine scale set. |
+| [Health probes](./load-balancer-custom-probe-overview.md#types) | TCP, HTTP, HTTPS | TCP, HTTP |
+| [Health probe down behavior](./load-balancer-custom-probe-overview.md#probedown) | TCP connections stay alive on an instance probe down __and__ on all probes down. | TCP connections stay alive on an instance probe down. All TCP connections terminate when all probes are down. |
+| Availability Zones | Zone-redundant and zonal frontends for inbound and outbound traffic. | Not available |
+| Diagnostics | [Azure Monitor multi-dimensional metrics](./load-balancer-standard-diagnostics.md) | [Azure Monitor logs](./load-balancer-monitor-log.md) |
+| HA Ports | [Available for Internal Load Balancer](./load-balancer-ha-ports-overview.md) | Not available |
+| Secure by default | Closed to inbound flows unless allowed by a network security group. Please note that internal traffic from the VNet to the internal load balancer is allowed. | Open by default. Network security group optional. |
+| Outbound Rules | [Declarative outbound NAT configuration](./load-balancer-outbound-rules-overview.md) | Not available |
+| TCP Reset on Idle | [Available on any rule](./load-balancer-tcp-reset.md) | Not available |
+| [Multiple front ends](./load-balancer-multivip-overview.md) | Inbound and [outbound](./load-balancer-outbound-connections.md) | Inbound only |
+| Management Operations | Most operations < 30 seconds | 60-90+ seconds typical |
+| SLA | [99.99%](https://azure.microsoft.com/support/legal/sla/load-balancer/v1_0/) | Not available | 
 
 For more information, see [Load balancer limits](https://docs.microsoft.com/azure/azure-resource-manager/management/azure-subscription-service-limits#load-balancer). For Standard Load Balancer details, see [overview](load-balancer-standard-overview.md), [pricing](https://aka.ms/lbpricing), and [SLA](https://aka.ms/lbsla).
 
@@ -72,4 +52,4 @@ For more information, see [Load balancer limits](https://docs.microsoft.com/azur
 - Learn about [Health Probes](load-balancer-custom-probe-overview.md).
 - Learn about using [Load Balancer for outbound connections](load-balancer-outbound-connections.md).
 - Learn about [Standard Load Balancer with HA Ports load balancing rules](load-balancer-ha-ports-overview.md).
-- Learn more about [Network Security Groups](../virtual-network/security-overview.md).
+- Learn more about [Network Security Groups](../virtual-network/security-overview.md).