diff --git a/admin_guide/managing_networking.adoc b/admin_guide/managing_networking.adoc
index e5094958053c..6a44d18bf07d 100644
--- a/admin_guide/managing_networking.adoc
+++ b/admin_guide/managing_networking.adoc
@@ -1124,11 +1124,16 @@ network isolation and do not support Kubernetes `NetworkPolicy`. However,
 
 [NOTE]
 ====
-Only the `v1` NetworkPolicy features are available in {product-title}. This
+The `v1` NetworkPolicy features are available only in {product-title}. This
 means that egress policy types, IPBlock, and combining `podSelector` and
 `namespaceSelector` are not available in {product-title}.
 ====
 
+[NOTE]
+====
+Do not apply `NetworkPolicy` features on default {product-title} projects, because they can disrupt communication with the cluster.
+====
+
 In a cluster
 ifdef::openshift-enterprise,openshift-origin[]
 xref:../install_config/configuring_sdn.adoc#install-config-configuring-sdn[configured
diff --git a/install_config/configuring_sdn.adoc b/install_config/configuring_sdn.adoc
index ec72b9d506b3..d057e12079c1 100644
--- a/install_config/configuring_sdn.adoc
+++ b/install_config/configuring_sdn.adoc
@@ -242,6 +242,18 @@ $ oc get netnamespace
 [[migrating-between-sdn-plugins-networkpolicy]]
 === Migrating from ovs-multitenant to ovs-networkpolicy
 
+[NOTE]
+====
+The `v1` NetworkPolicy features are available only in {product-title}. This
+means that egress policy types, IPBlock, and combining `podSelector` and
+`namespaceSelector` are not available in {product-title}.
+====
+
+[NOTE]
+====
+Do not apply `NetworkPolicy` features on default {product-title} projects, because they can disrupt communication with the cluster.
+====
+
 In addition to the generic plug-in migration steps above in the xref:migrating-between-sdn-plugins[Migrating between SDN plug-ins section], there is one additional
 step when migrating from the *ovs-multitenant* plug-in to the
 *ovs-networkpolicy* plug-in; you must ensure that every namespace has a unique