Skip to content

Commit b3814bf

Browse files
authored
Update compatibility.mdx
1 parent 49ec828 commit b3814bf

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -104,7 +104,7 @@ The table below provides a summary of the Data Localization Suite product's beha
104104

105105
| Product | Geo Key Manager | Regional Services | Customer Metadata Boundary |
106106
| ----------------- | --------------- | ----------------- | -------------------------- |
107-
| Access | 🚧 [^14] | 🚧 [^15] | 🚧 [^16] |
107+
| Access | 🚧 [^14] | 🚧 [^15] | [^16] |
108108
| Browser Isolation | ⚫️ | 🚧 [^17] ||
109109
| CASB | ⚫️ | ⚫️ ||
110110
| Cloudflare Tunnel | ⚫️ | 🚧 [^18] | ⚫️ |
@@ -142,7 +142,7 @@ The table below provides a summary of the Data Localization Suite product's beha
142142

143143
[^15]: Can be localized to US FedRAMP Moderate Domestic region only.
144144

145-
[^16]: Customer Metadata Boundary can be used to limit data transfer outside region, but Access User Logs will not be available outside US region.
145+
[^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.
146146

147147
[^17]: Currently may only be used with US FedRAMP region.
148148

0 commit comments

Comments
 (0)