Merge pull request #190369 from cburuzie/patch-14

Update load-balancer-ha-ports-overview.md

Author: PRMerger3

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

@@ -87,7 +87,7 @@ You can configure *one* public Standard Load Balancer resource for the backend r
 
 - HA ports load-balancing rules are available only for internal Standard Load Balancer.
 - The combining of an HA ports load-balancing rule and a non-HA ports load-balancing rule pointing to same backend ipconfiguration(s) is **not** supported on a single Frontend IP configuration unless both have Floating IP enabled.
-- Existing IP fragments will be forwarded by HA Ports load-balancing rules to same destination as first packet.  IP fragmenting a UDP or TCP packet is not supported.
+- IP fragmenting is not supported. If a packet is already fragmented, it will be forwarded based on the 2-tuple [distribution mode](distribution-mode-concepts.md) when enabled on HA ports load-balancing rules.
 - Flow symmetry (primarily for NVA scenarios) is supported with backend instance and a single NIC (and single IP configuration) only when used as shown in the diagram above and using HA Ports load-balancing rules. It is not provided in any other scenario. This means that two or more Load Balancer resources and their respective rules make independent decisions and are never coordinated. See the description and diagram for [network virtual appliances](#nva). When you are using multiple NICs or sandwiching the NVA between a public and internal Load Balancer, flow symmetry is not available.  You may be able to work around this by source NAT'ing the ingress flow to the IP of the appliance to allow replies to arrive on the same NVA.  However, we strongly recommend using a single NIC and using the reference architecture shown in the diagram above.