Setup

You can set up Email Security via:

Post-delivery deployment

With post-delivery deployment, Email Security scans emails after they reach users' inbox.

Post-delivery deployment includes Microsoft Graph API and BCC/Journaling.

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.

When you set up Microsoft Graph API, you get access to the following features:

Auto-moves.
Directory synchronization.
Post-delivery response / Phish submission response.
Auto pull EMLs for reclassification whose disposition is "None".
Manually move messages to different inboxes.

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.

Pre-delivery deployment

With pre-delivery deployment, 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:

Log in to Zero Trust ↗ > Email Security.
Go to Settings and locate your domain.
Select the three dots > Associate an integration.
Select the integration you want to associate, then select Associate.

To enable post-delivery response and phish submission response:

Go to Settings > Moves.
Go to Auto-moves, select View > Configure.
Select Post-delivery response (Recommended) and Phish submission response (Recommended).
Select Save.

Was this helpful?

Community
X
Discord
YouTube
GitHub