Update to reflect Metadata boundary updates (#24406)

* Update logpush-datasets.mdx

* Update compatibility.mdx

Author: kennyj42

src/content/docs/data-localization/compatibility.mdx

@@ -104,7 +104,7 @@ The table below provides a summary of the Data Localization Suite product's beha
 
 | Product           | Geo Key Manager | Regional Services | Customer Metadata Boundary |
 | ----------------- | --------------- | ----------------- | -------------------------- |
-| Access            | 🚧 [^14]        | 🚧 [^15]          | 🚧 [^16]                   |
+| Access            | 🚧 [^14]        | 🚧 [^15]          | ✅ [^16]                   |
 | Browser Isolation | ⚫️             | 🚧 [^17]          | ✅                         |
 | CASB              | ⚫️             | ⚫️               | ✘                          |
 | Cloudflare Tunnel | ⚫️             | 🚧 [^18]          | ⚫️                        |
@@ -142,7 +142,7 @@ The table below provides a summary of the Data Localization Suite product's beha
 
 [^15]: Can be localized to US FedRAMP Moderate Domestic region only.
 
-[^16]: Customer Metadata Boundary can be used to limit data transfer outside region, but Access User Logs will not be available outside US region.
+[^16]: Customer Metadata Boundary can be used to limit data transfer outside region, but Access User Logs will not be available outside US region. EU customers must use Logpush to retain logs.
 
 [^17]: Currently may only be used with US FedRAMP region.
 

src/content/docs/data-localization/metadata-boundary/logpush-datasets.mdx

@@ -34,6 +34,6 @@ Be aware that if you enable CMB for a dataset that does not support your region,
 | Network Analytics Logs         | Account | ✅           | ✅                           | ✅                           |
 | Device Posture Results         | Account | ✘            | ✅                           | ✘                            |
 | Audit Logs                     | Account | ✘            | ✅                           | ✘                            |
-| Access Requests                | Account | ✅           | ✅                           | ✘                            |
+| Access Requests                | Account | ✅           | ✅                           | ✅                            |
 
 [^1]: Customer Metadata Boundary does not apply in this case, as these logs are sent directly from the processing location to your configured destination.