|
5 | 5 | order: 1 |
6 | 6 | --- |
7 | 7 |
|
| 8 | +import { Markdown } from "~/components"; |
| 9 | + |
8 | 10 | Before you start the onboarding process, you will have to choose a deployment path. Email Security provides two deployment modes: [post-delivery](/cloudflare-one/email-security/setup/) (for API and BCC/Journaling), and [pre-delivery](/cloudflare-one/email-security/setup/#pre-delivery-deployment) (for MX/Inline). |
9 | 11 |
|
10 | 12 | ## Post-delivery deployment |
@@ -91,13 +93,15 @@ A correct use of reclassifications ensures that Email Security delivers a strong |
91 | 93 |
|
92 | 94 | | Step | Post-delivery | Pre-delivery | |
93 | 95 | |---------------------------------------------------------------------------------------------------------|---------------|--------------| |
94 | | -| Authorize integration (Graph API or Google Workspace) | Required | Required | |
95 | | -| Create service account and journaling rule | Required | Required | |
| 96 | +| Authorize integration ([Graph API](/cloudflare-one/email-security/setup/post-delivery-deployment/api/office365-api/#enable-microsoft-integration) or [Google Workspace](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration/))[^1] | Required | Required [^2] | |
96 | 97 | | Associate an integration with an MX/Inline domain | | Required | |
97 | 98 | | Add/verify domains | Required | Required | |
98 | | -| Update MX records/connector, then allow Cloudflare egress IPs on downstream mail server | | Required | |
99 | | -| Enable Post‑delivery response and Phish submission response | Required | Required | |
100 | | -| Populate Impersonation registry and allow / block lists | Required | Required | |
101 | | -| Configure partner TLS and admin quarantine | | Required | |
102 | | -| Configure Text Addons and Link Actions | | Required | |
103 | | -| Send a test email and verify it appears in Monitoring → Email activity with expected disposition | Required | Required | |
| 99 | +| [Update MX records/connector](/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment-setup/), then allow Cloudflare [egress IPs](/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment-setup/) on downstream mail server | | Required | |
| 100 | +| Enable [Post‑delivery response and Phish submission response](/cloudflare-one/email-security/auto-moves/) | Required | Required | |
| 101 | +| Populate [impersonation registry](/cloudflare-one/email-security/detection-settings/impersonation-registry/) and [allow](/cloudflare-one/email-security/detection-settings/allow-policies/)/[block](/cloudflare-one/email-security/detection-settings/blocked-senders/) lists | Required | Required | |
| 102 | +| Configure [partner domain TLS](/cloudflare-one/email-security/setup/pre-delivery-deployment/partner-domain-tls/) and admin quarantine | | Required | |
| 103 | +| Configure [text add-ons](/cloudflare-one/email-security/detection-settings/configure-text-add-ons/) and [link actions](/cloudflare-one/email-security/detection-settings/configure-link-actions/) | | Required | |
| 104 | +| Send a test email and verify it appears in **Monitoring** > [**Email activity**](/cloudflare-one/email-security/email-monitoring/#email-activity) with expected disposition | Required | Required | |
| 105 | + |
| 106 | +[^1]: Alternatively, you can create a service account and add BCC rules. |
| 107 | +[^2]: Still used for directory/auto‑move insight if desired as well as authorizing free API CASB |
0 commit comments