Merge pull request #271973 from anavinahar/patch-278

Update outbound-rules.md

Author: prmerger-automator[bot]

articles/load-balancer/outbound-rules.md

@@ -5,7 +5,7 @@ services: load-balancer
 author: mbender-ms
 ms.service: load-balancer
 ms.topic: conceptual
-ms.date: 05/08/2023
+ms.date: 04/11/2024
 ms.author: mbender
 ms.custom: template-how-to, engagement-fy23
 ---
@@ -238,7 +238,8 @@ When only inbound NAT rules are used, no outbound NAT is provided.
 - The maximum number of usable ephemeral ports per frontend IP address is 64,000.
 - The range of the configurable outbound idle timeout is 4 to 120 minutes (240 to 7200 seconds).
 - Load balancer doesn't support ICMP for outbound NAT, the only supported protocols are TCP and UDP.
-- Outbound rules can only be applied to primary IP configuration of a NIC.  You can't create an outbound rule for the secondary IP of a VM or NVA. Multiple NICs are supported.
+- Outbound rules can only be applied to primary IPv4 configuration of a NIC.  You can't create an outbound rule for the secondary IPv4 configurations of a VM or NVA . Multiple NICs are supported.
+- Outbound rules for the secondary IP configuration are only supported for IPv6.
 - All virtual machines within an **availability set** must be added to the backend pool for outbound connectivity. 
 - All virtual machines within a **virtual machine scale set** must be added to the backend pool for outbound connectivity.