Skip to content

warn that edited Email Routing records remain service-linked.mdx#32101

Open
dpiteira95 wants to merge 1 commit into
cloudflare:productionfrom
dpiteira95:patch-13
Open

warn that edited Email Routing records remain service-linked.mdx#32101
dpiteira95 wants to merge 1 commit into
cloudflare:productionfrom
dpiteira95:patch-13

Conversation

@dpiteira95

Copy link
Copy Markdown
Contributor

Clarify that unlocking and editing an Email Service-created DNS record does not remove its association with Email Service.

Previously, the migration guidance suggested unlocking records and adding new provider records before disabling Email Routing. However, it was not clear that editing an unlocked record (for example, changing the SPF TXT record to point to Microsoft 365 or another provider) would still cause that record to be deleted when Email Routing is disabled, because the record remains internally linked to the service.

Add a caution note explaining this behavior.

Clarify that unlocking and editing an Email Service-created DNS record
does not remove its association with Email Service.

Previously, the migration guidance suggested unlocking records and adding
new provider records before disabling Email Routing. However, it was not
clear that editing an unlocked record (for example, changing the SPF TXT
record to point to Microsoft 365 or another provider) would still cause
that record to be deleted when Email Routing is disabled, because the
record remains internally linked to the service.

Add a caution note explaining this behavior.
@dpiteira95
dpiteira95 requested a review from a team as a code owner July 16, 2026 11:32
@cloudflare-docs-bot

cloudflare-docs-bot Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Review

✅ No issues found in commit 519634e.

Code Review

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

No code review issues found.

Conventions

No convention issues found.

Style Guide Review

No style-guide issues found.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant