[Email Security] Differences between deployments

Author: Maddy-Cloudflare

src/content/docs/cloudflare-one/email-security/setup/index.mdx

@@ -5,45 +5,39 @@ sidebar:
   order: 1
 ---
 
-import { DirectoryListing } from "~/components"
+You can deploy Email Security via:
 
-You can set up Email Security via:
+- [Microsoft Graph API](/cloudflare-one/email-security/setup/post-delivery-deployment/api/)
+- [BCC](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/gmail-bcc-setup/)/[Journaling](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/office365-journaling/)
+- [MX/Inline](/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment-setup/)
 
-<DirectoryListing />
+If you have an integration, you will be able to:
 
-## Post-delivery deployment
+- Set up [auto-move events](/cloudflare-one/email-security/auto-moves/).
+- [Synchronize a directory](/cloudflare-one/email-security/directories/).
+- Auto pull EMLs for [reclassification](/cloudflare-one/email-security/email-monitoring/search-email/#reclassify-messages) whose disposition is "None".
+- Manually move messages to different inboxes.
 
-With post-delivery deployment, Email Security scans emails **after** they reach users' inbox.
+## Microsoft Graph API
 
-Post-delivery deployment includes [Microsoft Graph API](/cloudflare-one/email-security/setup/post-delivery-deployment/api/) and [BCC](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/gmail-bcc-setup/)/[Journaling](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/office365-journaling/).
+With Microsoft Graph API, Email Security scans emails after they reach users' inbox. 
 
-With Microsoft Graph API, you authorize Email Security to scan domains via your email provider credentials. With BCC/Journaling, you send messages to Email Security via BCC or Journaling configurations within your email provider.
+By deploying Email Security via Microsoft Graph API, you authorize Email Security to scan domains via your email provider credentials. 
 
-When you set up Microsoft Graph API, you get access to the following features:
+## BCC/Journaling
 
-- Auto-moves.
-- Directory synchronization.
-- Post-delivery response / Phish submission response.
-- Auto pull EMLs for [reclassification](/cloudflare-one/email-security/email-monitoring/search-email/#reclassify-messages) whose disposition is "None".
-- Manually move messages to different inboxes.
+Email Security scans emails after they reach users' inbox. 
 
-If you set up Email Security via BCC/Journaling and you want to access the features listed above, you will need to [associate an integration](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-auto-moves/).
+With BCC/Journaling, you send messages to Email Security via BCC or Journaling configurations within your email provider.
 
-## Pre-delivery deployment
+## MX/Inline
 
-With pre-delivery deployment, Email Security scans emails **before** they reach users' inbox.
+With MX/Inline, Email Security scans emails **before** they reach users' inbox.
 
 MX/Inline allows you to send messages to Email Security to scan before they reach your users' inbox. You may need to update your MX records.
 
 With MX/Inline, you will not be able to auto-move emails.
 
-However, you will need to associate an integration to access the following features:
-
-- Directory synchronization.
-- Post-delivery response / Phish submission response.
-- Auto pull EMLs for reclassification for disposition "None".
-- Manually move messages.
-
 ### Associate an integration
 
 To associate an integration: