Remove ILB limitation for secondary IP in backend pool

Author: rdeltcheva

articles/sap/workloads/dbms-guide-ha-ibm.md

@@ -6,7 +6,7 @@ ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.custom: devx-track-azurecli, devx-track-azurepowershell, linux-related-content
 ms.topic: article
-ms.date: 01/18/2024
+ms.date: 06/18/2024
 ms.author: juergent
 ---
 
@@ -313,9 +313,6 @@ During VM configuration, you have an option to create or select exiting load bal
 
 ---
 
-> [!IMPORTANT]
-> Floating IP isn't supported on a NIC secondary IP configuration in load-balancing scenarios. For more information, see [Azure Load Balancer limitations](../../load-balancer/load-balancer-multivip-overview.md#limitations). If you need another IP address for the VM, deploy a second NIC.
-
 > [!NOTE]
 > When VMs without public IP addresses are placed in the back-end pool of an internal (no public IP address) instance of Standard Azure Load Balancer, there's no outbound internet connectivity unless more configuration is performed to allow routing to public endpoints. For more information on how to achieve outbound connectivity, see [Public endpoint connectivity for VMs using Azure Standard Load Balancer in SAP high-availability scenarios](./high-availability-guide-standard-load-balancer-outbound-connections.md).
 

articles/sap/workloads/high-availability-guide-rhel-ibm-db2-luw.md

@@ -9,7 +9,7 @@ ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.topic: article
 ms.tgt_pltfrm: vm-linux
-ms.date: 01/18/2024
+ms.date: 06/18/2024
 ms.author: juergent
 ---
 # High availability of IBM Db2 LUW on Azure VMs on Red Hat Enterprise Linux Server
@@ -339,9 +339,6 @@ During VM configuration, you have an option to create or select exiting load bal
 
 ---
 
-> [!IMPORTANT]
-> Floating IP isn't supported on a NIC secondary IP configuration in load-balancing scenarios. For more information, see [Azure Load Balancer limitations](../../load-balancer/load-balancer-multivip-overview.md#limitations). If you need another IP address for the VM, deploy a second NIC.
-
 > [!NOTE]
 > When VMs without public IP addresses are placed in the back-end pool of an internal (no public IP address) instance of Standard Azure Load Balancer, there's no outbound internet connectivity unless more configuration is performed to allow routing to public endpoints. For more information on how to achieve outbound connectivity, see [Public endpoint connectivity for VMs using Azure Standard Load Balancer in SAP high-availability scenarios](./high-availability-guide-standard-load-balancer-outbound-connections.md).