Recommend enabling out-of-region access

[cferike]

Added recommendation to enable out-of-region access for better log and analytics visibility.

Summary

Screenshots (optional)

Documentation checklist

• Is there a changelog entry (guidelines)? If you don't add one for something awesome and new (however small) — how will our customers find out? Changelogs are automatically posted to RSS feeds, the Discord, and X.
• The change adheres to the documentation style guide.
• If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
• Files which have changed name or location have been allocated redirects.

[cloudflare-docs-bot]

Review

⚠️ 1 warning, 💡 2 suggestions found in commit 15c84f1.

👉 Fix in your agent 👈

Fix the following review findings in PR #32659 (https://github.com/cloudflare/cloudflare-docs/pull/32659).

Before making changes, review each finding and present a brief summary table:
- For each finding, state whether you agree, disagree, or need clarification
- If you disagree (e.g. the fix requires disproportionate effort for minimal benefit,
  or the finding is factually incorrect), explain why
- If you need clarification before deciding, ask those questions
- Then share your plan for which issues to tackle and in what order

After triaging, follow this order:
1. Post a comment on this PR for any findings you are skipping, with the finding ID and your reasoning.
2. Then commit the fixes for the legitimate findings.

The comment must come before the commit — the bot reads PR comments when a new
push triggers a review, so skip comments posted after the push will be missed.

---

## Code Review

### Warnings (1)

#### CR-df3b377f533e · Unconditional recommendation conflicts with feature purpose
- **File:** `src/content/docs/data-localization/metadata-boundary/index.mdx` line 18
- **Issue:** Line 18 states, "It is recommended to enable out-of-region access so that logs and analytics populate in the dashboard," as a blanket recommendation. However, the Customer Metadata Boundary is specifically designed to restrict Customer Logs to a selected region, and some customers choose it precisely to limit where logs can be accessed. Recommending out-of-region access unconditionally could mislead those customers into enabling access from any physical location, undermining their data-residency requirements.
- **Fix:** Qualify the recommendation: explain that enabling out-of-region access keeps Customer Logs stored in the configured region but allows authorized users to view them from anywhere, and that organizations with strict data-residency or access-control requirements should evaluate whether this setting is appropriate before enabling it.

---

## Style Guide Review

### Suggestions (2)

#### SG-840f99986399 · Use turn on / turn off for toggles instead of enable / disable
- **File:** `src/content/docs/data-localization/metadata-boundary/index.mdx` line 18
- **Issue:** Uses `is enabled`, `When enabled`, and `to enable` to describe the `Allow out-of-region access` setting.
- **Fix:** Replace `enabled`/`enable` with `turned on`/`turn on` when referring to the toggle setting.

#### SG-0c5c7acc95f1 · Use active voice where it would be clearer
- **File:** `src/content/docs/data-localization/metadata-boundary/index.mdx` line 18
- **Issue:** Uses passive constructions `An exception is made`, `will be stored`, `will be accessible`, and `It is recommended to enable...`.
- **Fix:** Rewrite the sentence more directly, e.g., "Enable out-of-region access so that logs and analytics populate in the dashboard."

Code Review

This code review is in beta and may not always be helpful — use your judgment.

Warnings (1)

File

Issue

data-localization/metadata-boundary/index.mdx line 18

Unconditional recommendation conflicts with feature purpose — Line 18 states, "It is recommended to enable out-of-region access so that logs and analytics populate in the dashboard," as a blanket recommendation. However, the Customer Metadata Boundary is specifically designed to restrict Customer Logs to a selected region, and some customers choose it precisely to limit where logs can be accessed. Recommending out-of-region access unconditionally could mislead those customers into enabling access from any physical location, undermining their data-residency requirements. Fix: Qualify the recommendation: explain that enabling out-of-region access keeps Customer Logs stored in the configured region but allows authorized users to view them from anywhere, and that organizations with strict data-residency or access-control requirements should evaluate whether this setting is appropriate before enabling it.

Conventions

_{No convention issues found.}

Style Guide Review

Suggestions (2)

File	Issue
data-localization/metadata-boundary/index.mdx line 18	Use turn on / turn off for toggles instead of enable / disable — Uses is enabled, When enabled, and to enable to describe the Allow out-of-region access setting. Fix: Replace enabled/enable with turned on/turn on when referring to the toggle setting.
data-localization/metadata-boundary/index.mdx line 18	Use active voice where it would be clearer — Uses passive constructions An exception is made, will be stored, will be accessible, and It is recommended to enable.... Fix: Rewrite the sentence more directly, e.g., "Enable out-of-region access so that logs and analytics populate in the dashboard."

Commands

Only codeowners can run commands. Post a comment with the command to trigger it.

Command	Description
/review	Runs a review now. Incremental if a prior review exists, full if not.
/full-review	Re-reviews the entire PR diff from scratch, ignoring incremental history. Useful after a rebase, when you want a fresh review, or if the bot gets out of sync and reports issues that no longer exist.
/ignore-review-limit	Permanently lifts the 2-review automatic limit for this PR. Future pushes will trigger reviews as normal.
/disable-auto-review	Stops automatic reviews from triggering on future pushes to this PR. Codeowners can still run /review or /full-review manually.
/rebase	Rebases the PR branch against production. On conflict, attempts to resolve automatically using AI. Stops with an explanation if confidence is not high enough.

[github-actions]

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern	Owners
/src/content/docs/data-localization/	@mathew-cf, @aberglund-cf, @cferike, @cagrawal, @Arkanayan, @connect-avinash31, @umeshgtank, @angelampcosta, @cloudflare/appsec-reviewers, @cloudflare/cf1-reviewers, @elithrar, @cloudflare/product-owners

[github-actions]

Preview URL: https://15c84f10.preview.developers.cloudflare.com
Preview Branch URL: https://cferike-patch-1.preview.developers.cloudflare.com

Files with changes (up to 15)

Original Link	Updated Link
https://developers.cloudflare.com/data-localization/metadata-boundary/	https://cferike-patch-1.preview.developers.cloudflare.com/data-localization/metadata-boundary/