Skip to content

Commit a5b0f07

Browse files
Apply suggestion from @deadlypants1973
Co-authored-by: Kate Tungusova <[email protected]>
1 parent fcfe215 commit a5b0f07

File tree

1 file changed

+1
-1
lines changed
  • src/content/docs/cloudflare-one/email-security/setup

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ The following table compares features available across API, BCC/Journaling and M
2424
| Supported Email Provider | Microsoft 365 | Gmail, Microsoft 365 | Microsoft 365 | All email providers |
2525
| Inspection Timing | Scans messages already in the mailbox | Scans a copy of the message upon delivery | Scans a copy of the message upon delivery | Scans the message before delivery |
2626
| Mechanism | Uses MS Graph API to integrate with Microsoft 365. | Uses a BCC rule to send a copy to Cloudflare | Uses a Journal Rule in the Microsoft Purview portal | Changes MX records to point email traffic to Cloudflare |
27-
| Message Remediation | Auto-moves through Read-Write API permissions | Auto-moves through Google or Microsoft integration | Auto-moves through Microsoft integration | Messages can be blocked, quarantined, or modified inline |
27+
| Message Remediation | Auto-moves through Read/Write API permissions | Auto-moves through Google or Microsoft integration | Auto-moves through Microsoft integration | Messages can be blocked, quarantined, or modified inline |
2828
| Message Modification | Primarily deletion/move post-delivery | Primarily deletion/move post-delivery | Primarily deletion/move post-delivery. | Move post-delivery. Supports link actions and text add-ons.[^1] |
2929

3030
[^1] With inline, we recommend setting up the integrations to allow post-delivery response and phish submission response to work. Refer to step 7 in [Auto-moves](/cloudflare-one/email-security/auto-moves/) to learn more.

0 commit comments

Comments
 (0)