Merge pull request #186371 from anavinahar/patch-262

Update load-balancer-multivip-overview.md

Author: AnnaMHuff

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

@@ -9,7 +9,7 @@ ms.custom: seodec18
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: infrastructure-services
-ms.date: 08/07/2019
+ms.date: 01/26/2022
 ms.author: allensu
 ---
 
@@ -19,7 +19,7 @@ Azure Load Balancer allows you to load balance services on multiple ports, multi
 
 This article describes the fundamentals of this ability, important concepts, and constraints. If you only intend to expose services on one IP address, you can find simplified instructions for [public](./quickstart-load-balancer-standard-public-portal.md) or [internal](./quickstart-load-balancer-standard-internal-portal.md) load balancer configurations. Adding multiple frontends is incremental to a single frontend configuration. Using the concepts in this article, you can expand a simplified configuration at any time.
 
-When you define an Azure Load Balancer, a frontend and a backend pool configuration are connected with rules. The health probe referenced by the rule is used to determine how new flows are sent to a node in the backend pool. The frontend (aka VIP) is defined by a 3-tuple comprised of an IP address (public or internal), a transport protocol (UDP or TCP), and a port number from the load balancing rule. The backend pool is a collection of Virtual Machine IP configurations (part of the NIC resource) which reference the Load Balancer backend pool.
+When you define an Azure Load Balancer, a frontend and a backend pool configuration are connected with rules. The health probe referenced by the rule is used to determine how new flows are sent to a node in the backend pool. The frontend (also known as VIP) is defined by a 3-tuple comprised of an IP address (public or internal), a transport protocol (UDP or TCP), and a port number from the load balancing rule. The backend pool is a collection of Virtual Machine IP configurations (part of the NIC resource) which reference the Load Balancer backend pool.
 
 The following table contains some example frontend configurations:
 
@@ -155,7 +155,7 @@ The Floating IP rule type is the foundation of several load balancer configurati
 
 ## Limitations
 
-* Multiple frontend configurations are only supported with IaaS VMs.
+* Multiple frontend configurations are only supported with IaaS VMs and virtual machine scale sets.
 * With the Floating IP rule, your application must use the primary IP configuration for outbound SNAT flows. If your application binds to the frontend IP address configured on the loopback interface in the guest OS, Azure's outbound SNAT is not available to rewrite the outbound flow and the flow fails.  Review [outbound scenarios](load-balancer-outbound-connections.md).
 * Floating IP is not currently supported on secondary IP configurations for Internal Load Balancing scenarios.
 * Public IP addresses have an effect on billing. For more information, see [IP Address pricing](https://azure.microsoft.com/pricing/details/ip-addresses/)