diff --git a/modules/nw-egress-ips-about.adoc b/modules/nw-egress-ips-about.adoc
index 19e720b4e4eb..94253a4a9cff 100644
--- a/modules/nw-egress-ips-about.adoc
+++ b/modules/nw-egress-ips-about.adoc
@@ -169,7 +169,6 @@ On Azure, the following capacity limits exist for IP address assignment:
 - Per virtual network, the maximum number of assigned IP addresses cannot exceed 65,536.
 
 For more information, see link:https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits?toc=/azure/virtual-network/toc.json#networking-limits[Networking limits].
-endif::openshift-rosa[]
 
 [id="nw-egress-ips-multi-nic-considerations_{context}"]
 == Considerations for using an egress IP on additional network interfaces
@@ -196,7 +195,6 @@ You can determine which other network interfaces might support egress IPs by ins
 OVN-Kubernetes provides a mechanism to control and direct outbound network traffic from specific namespaces and pods. This ensures that it exits the cluster through a particular network interface and with a specific egress IP address.
 ====
 
-ifndef::openshift-rosa[]
 [discrete]
 [id="nw-egress-ips-multi-nic-requirements_{context}"]
 === Requirements for assigning an egress IP to a network interface that is not the primary network interface