-
Notifications
You must be signed in to change notification settings - Fork 10k
[Email Security] Update Migration guide #23756
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 2 commits
Commits
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
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 |
|---|---|---|
|
|
@@ -33,6 +33,10 @@ Once you have added new account members, you will have to assign each member an | |
|
|
||
| ## Create webhooks | ||
|
|
||
| :::note | ||
| By October 2025, Area 1 webhooks will be visible in Zero Trust Email Security, but non-configurable. Use [Logpush](/cloudflare-one/insights/logs/enable-logs/#enable-user-action-logs) to create new webhooks or configure webhooks. | ||
| ::: | ||
|
|
||
| In Area 1, you can [create alert webhooks](/email-security/email-configuration/domains-and-routing/alert-webhooks/#create-an-alert-webhook). | ||
|
|
||
| In Zero Trust Email Security, webhooks are instead referred to as logs. You can enable [detection logs](/cloudflare-one/insights/logs/enable-logs/#enable-detection-logs) and/or [user action logs](/cloudflare-one/insights/logs/enable-logs/#enable-user-action-logs). Additionally, you can enable [Outbound Data Loss Prevention](/cloudflare-one/email-security/outbound-dlp/) to protect sensitive information in outbound emails. | ||
|
|
@@ -47,8 +51,18 @@ In Email Security, you can: | |
| - Go to [Cloudflare Status API](https://www.cloudflarestatus.com/api) to view status information for the API documentation and functionality. | ||
| - Configure [Cloudflare Notifications](/notifications/get-started/). | ||
|
|
||
| ## Email alerts | ||
|
|
||
| In Area 1, you receive daily or weekly updates of the number of emails dispositioned. | ||
|
|
||
| In Email Security, you can view [email monitoring](/cloudflare-one/email-security/email-monitoring/) over the last 90, 30, 7, 3, 1 day(s). | ||
|
|
||
| ## Contact support | ||
|
|
||
| :::note | ||
| From October 2025, we will no longer receive support requests via email to any `@area1security.com` addresses. We will transition to receiving support requests from the Cloudflare dashboard. | ||
Maddy-Cloudflare marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
Maddy-Cloudflare marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| ::: | ||
|
|
||
| In Area 1, you can reach out to support via the following email addresses: | ||
|
|
||
| - [email protected] | ||
|
|
@@ -63,6 +77,8 @@ In Email Security, you can: | |
| - In what area can we help you? **Email Security** | ||
| - Email [email protected] (for PhishGuard customers only). | ||
|
|
||
| If you are PhishGuard customer, you will be informed when you can start raising PhishGuard tickets in the Cloudflare dashboard. | ||
|
|
||
| ## Search emails | ||
|
|
||
| In Area 1, you can perform two types of search: [Fielded Search](/email-security/reporting/search/#fielded-search) and [Freeform Search](/email-security/reporting/search/#freeform-search). | ||
|
|
@@ -119,4 +135,14 @@ In Email Security, this feature is known as [impersonation registry](/cloudflare | |
|
|
||
| In Area 1, you can [integrate directories](/email-security/email-configuration/enhanced-detections/business-email-compromise/#integrating-a-directory) in your email provider. | ||
|
|
||
| In Email Security, you can add and sync [directories](/cloudflare-one/email-security/directories/). | ||
| In Email Security, you can add and sync [directories](/cloudflare-one/email-security/directories/). | ||
|
|
||
| ## API | ||
|
|
||
| :::note | ||
| Area 1 API endpoints will deprecate on December 18, 2025. Use the [Email Security API](https://developers.cloudflare.com/api/resources/email_security/) endpoints to prevent interruption to your normal operations. | ||
| ::: | ||
|
|
||
| To access Area 1 API, go to the [API Documentation](https://developers.cloudflare.com/email-security/static/api_documentation_1.38.1.pdf). You can set up a [service account](https://developers.cloudflare.com/email-security/api/service-accounts/) to configure API tokens. | ||
|
|
||
| To access Email Security API, go to [Email Security API](https://developers.cloudflare.com/api/resources/email_security/). You can set up an [API token](/fundamentals/api/get-started/create-token/) to use the Email Security API. | ||
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.
Uh oh!
There was an error while loading. Please reload this page.