diff --git a/modules/ROOT/pages/osv2-connected-apps.adoc b/modules/ROOT/pages/osv2-connected-apps.adoc
index 7ae85bf..ad89892 100644
--- a/modules/ROOT/pages/osv2-connected-apps.adoc
+++ b/modules/ROOT/pages/osv2-connected-apps.adoc
@@ -1,11 +1,18 @@
-= Configuring Connected Apps
+= Configuring Connected Apps for Object Store
 
-The Connected Apps feature enables you to integrate external applications with Anypoint Platform by providing access to those applications without sharing your user credentials.
+Connected apps provide secure, credential-free access to Object Store for external applications and Mule integrations. After creating a connected app in Access Management, use the generated client ID and secret to authenticate with the Object Store v2 API.
 
 For information about Connected Apps, see 
 xref:access-management::connected-apps-overview.adoc[] and
 xref:access-management::connected-apps-developers.adoc[].
 
+[IMPORTANT]
+====
+If your organization has IP allowlisting enabled for connected apps, you must either allowlist the outbound IPs of the runtime where your Mule app is deployed, or exempt the connected app from IP enforcement. Without one of these steps, token generation fails and your Mule flows stop processing messages.
+
+If your app runs on CloudHub without static IPs or on CloudHub 2.0 Shared Space, you must exempt the connected app. These deployment models use dynamic or shared IPs that can't be reliably allowlisted. For guidance on all deployment models and exemption steps, see xref:access-management::managing-ip-allowlists.adoc#configure-ip-allowlisting-connected-apps[Configure IP Allowlisting for Connected Apps].
+====
+
 
 [[configure-os-conn-app]]
 == Configure a Connected App in Access Management