-
Notifications
You must be signed in to change notification settings - Fork 10k
Create 2025-09-11-regional-email-processing-gia.md #25112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
30 changes: 30 additions & 0 deletions
30
...ntent/changelog/email-security-cf1/2025-09-11-regional-email-processing-gia.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,30 @@ | ||
| --- | ||
| title: Regional Email Processing for Germany, India, or Australia | ||
| description: Customers can now choose their preferred mail processing location to be Germany, India, or Australia during onboarding | ||
| date: 2025-09-11T23:15:00Z | ||
| --- | ||
|
|
||
| We’re excited to announce that Email Security customers can now choose their preferred mail processing location directly from the UI when onboarding a domain. This feature is available for the following onboarding methods: **MX**, **BCC**, and **Journaling**. | ||
|
|
||
| ### What’s new | ||
| Customers can now select where their email is processed. The following regions are supported: | ||
| - **Germany** | ||
| - **India** | ||
| - **Australia** | ||
|
|
||
| Global processing remains the default option, providing flexibility to meet both compliance requirements or operational preferences. | ||
|
|
||
| ### How to use it | ||
| When onboarding a domain with MX, BCC, or Journaling: | ||
| 1. Select the desired processing location (Germany, India, or Australia). | ||
| 2. The UI will display updated processing addresses specific to that region. | ||
| 3. For MX onboarding, if your domain is managed by Cloudflare, you can automatically update MX records directly from the UI. | ||
|
|
||
| ### Availability | ||
| This feature is available across these Email Security packages: | ||
| - **Advantage** | ||
| - **Enterprise** | ||
| - **Enterprise + PhishGuard** | ||
|
|
||
| ### What’s next | ||
| We’re expanding the list of processing locations to match our [Data Localization Suite (DLS)](/data-localization/) footprint, giving customers the broadest set of regional options in the market without the complexity of self-hosting. | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor suggestion: Since this isn't really a 3-step process, I recommend removing the steps.