From 00cd0e73e3f3ba6f334daf55c2a1cf30e67bbfd0 Mon Sep 17 00:00:00 2001
From: Corry Root <corry.root@mongodb.com>
Date: Tue, 15 Sep 2026 11:09:44 -0400
Subject: [PATCH 1/2] (DOCSP-58901): Note Admin API limitations for
 regionalized projects

---
 cet/atlas/data-processing.rst | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/cet/atlas/data-processing.rst b/cet/atlas/data-processing.rst
index 14b920d..b753f7a 100644
--- a/cet/atlas/data-processing.rst
+++ b/cet/atlas/data-processing.rst
@@ -62,7 +62,21 @@ When the option is enabled, {+service+} will limit processing of document field
 values and database logs that are processed through Performance
 Advisor, Query Profiler, Schema Advisor, Data Explorer, and Real Time
 Performance Panel so that those field values and database logs are
-processed in a specific *Project Services Region*. 
+processed in a specific *Project Services Region*.
+
+.. note:: {+atlas-admin-api+} Limitations for Regionalized Projects
+
+   For projects with a non-US *Project Services Region* enabled, you
+   can access the preceding features only through the {+service+}
+   console. |service-fullname| doesn't support programmatic requests to
+   the :ref:`{+atlas-admin-api+} <atlas-admin-api>` for the following
+   features, and such requests fail:
+
+   - :ref:`Performance Advisor <performance-advisor>`
+   - :ref:`Query Profiler <profile-database>`
+   - :ref:`Schema Advisor <schema-suggestions>`
+   - :ref:`Data Explorer <atlas-ui>`
+   - :ref:`Real Time Performance Panel <real-time-metrics-status-tab>`
 
 Q: How does {+service+} select the *Project Services Region*?
 

From 68810a22e64043039b184d1691f965de1509160d Mon Sep 17 00:00:00 2001
From: Corry Root <corry.root@mongodb.com>
Date: Wed, 16 Sep 2026 10:13:12 -0400
Subject: [PATCH 2/2] (DOCSP-58901): Incorporated Melissa's feedback.

---
 cet/atlas/data-processing.rst | 30 +++++++++++-------------------
 1 file changed, 11 insertions(+), 19 deletions(-)

diff --git a/cet/atlas/data-processing.rst b/cet/atlas/data-processing.rst
index b753f7a..995c852 100644
--- a/cet/atlas/data-processing.rst
+++ b/cet/atlas/data-processing.rst
@@ -58,25 +58,17 @@ The following {+service+} features support non-US *Project Services Regions*:
 - :ref:`Data Explorer <atlas-ui>`
 - :ref:`Real Time Performance Panel <real-time-metrics-status-tab>`
 
-When the option is enabled, {+service+} will limit processing of document field
-values and database logs that are processed through Performance
-Advisor, Query Profiler, Schema Advisor, Data Explorer, and Real Time
-Performance Panel so that those field values and database logs are
-processed in a specific *Project Services Region*.
-
-.. note:: {+atlas-admin-api+} Limitations for Regionalized Projects
-
-   For projects with a non-US *Project Services Region* enabled, you
-   can access the preceding features only through the {+service+}
-   console. |service-fullname| doesn't support programmatic requests to
-   the :ref:`{+atlas-admin-api+} <atlas-admin-api>` for the following
-   features, and such requests fail:
-
-   - :ref:`Performance Advisor <performance-advisor>`
-   - :ref:`Query Profiler <profile-database>`
-   - :ref:`Schema Advisor <schema-suggestions>`
-   - :ref:`Data Explorer <atlas-ui>`
-   - :ref:`Real Time Performance Panel <real-time-metrics-status-tab>`
+.. note:: Limitations for Regionalized Projects
+
+   When the option is enabled, {+service+} limits processing of
+   document field values and database logs that are processed through
+   Performance Advisor, Query Profiler, Schema Advisor, Data Explorer,
+   and Real Time Performance Panel so that those field values and
+   database logs are processed in a specific *Project Services Region*.
+
+   You can access these features only through the {+service+} console.
+   You can't access them by programmatic request to the
+   :ref:`{+atlas-admin-api+} <atlas-admin-api>`.
 
 Q: How does {+service+} select the *Project Services Region*?