Merge pull request #109702 from irenehua/patch-16

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

Author: PRMerger17

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

@@ -90,7 +90,7 @@ You can configure *one* public Standard Load Balancer resource for the back-end
 ## Limitations
 
 - 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 is not supported.
+- The combining of an HA ports load-balancing rule and a non-HA ports load-balancing rule pointing to same backend ipconfigurations is not supported.
 - 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.
 - 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.