Title
Page icon
Create new category
Edit page index title
Edit category
Edit link
Microsoft Exchange Online
MetaDefender Cloud Email Security ™ integrates seamlessly with Microsoft Exchange Online by rerouting email traffic through the platform for advanced security analysis before emails reach user mailboxes or are sent externally. This proactive approach enhances protection compared to API-based solutions that scan emails only after delivery to the mailbox.
How the Exchange Online Integration Works
MetaDefender Cloud Email Security ™ establishes a mail flow redirection path within Microsoft 365 using the following components:
Outbound Connector
Configured in Microsoft 365 to forward selected outbound emails to the product platform for inspection before external delivery.
Inbound Connector
Ensures that Microsoft 365 accepts and trusts emails processed and returned from the platform.
Mail Flow Rules (Transport Rules)
Customizable rules define which emails (inbound or outbound) are rerouted to MetaDefender Cloud Email Security ™ for analysis. This provides granular control over the protection scope.
For more information see Integration Details (In-line Protection mode) and Integration Details (Monitoring mode).
When integrating on systems with other third-party email security solutions deployed, check Integrating with 3rd Party Connector-Based Email Security Solutions to ensure accidental email loops are prevented.
Trusted ARC Sealer
MetaDefender Cloud Email Security ™ platform domain names (opswat.com) are added as Microsoft 365 Trusted ARC sealer domains to ensure trusted communication and prevent emails from being marked as spam or rejected.
Wizard Steps
This guide walks you through the steps to integrate Microsoft Exchange Online with MetaDefender Cloud Email Security ™.
Specify Deployment Type
You will have two options:
Express: Will automatically configure a protection integration with default protection settings.
Advanced: Allows you to customize deployment modes (inline/protected) for a subset of users/groups and set default actions for malicious/suspicious content.
Select the appropriate option based on your needs.
Connect to Microsoft 365
Click the Authorize Application button.
This will open the Microsoft 365 sign in page.
Log in using your Global Admin Credentials.
Grant the required permissions for the platform.
Refer to the Microsoft 365 Application permissions KB article for detailed information on the permissions required by MetaDefender Cloud Email Security ™.
Define User Protection Scope (Advanced Deployment Only)
Choose which users will be protected:
All users in the organization (Apply protection to all accounts)
Only the selected users (Protect only specific users)
Only the selected groups (Protect only specific groups)
Click Continue to confirm your selection.
The user protection scope defines which users the Microsoft 365 mail flow rules will apply to. Emails for users not included in this scope will not be routed through MetaDefender Cloud Email Security ™. (You can modify the protection scope later through the mail flow rules in the Microsoft 365 Exchange administration center.)
How Would You Like Us To Install? (Advanced Deployment Only)
Choose how MetaDefender Cloud Email Security ™ should handle email security:
Protection Mode: Will actively scan emails in real time.
Monitor Mode: Receives and analyzes copies of emails for threats, providing detailed reports.
Select the type of email traffic to be analyzed (You can select one or multiple options):
Inbound (Incoming emails)
Outbound (Emails sent outside the organization)
Click Continue to confirm your selection.
Summary
Verify the selections made is previous steps and confirm by clicking Continue.
Applying Changes
The system will configure the integration.
You will see status messages indicating successful steps:
✅ Connected to Microsoft Exchange Online.
✅ Configured outbound and inbound connectors.
✅ Configured transport rules.
Once the system configuration is completed, the mail flow rules can be examined before they are enabled.
Refer to Integration Details (In-line Protection mode) or Integration Details (Monitoring mode) for more information.
The mail flow rules can also be enabled directly from: https://admin.exchange.microsoft.com. For more details on when using MetaDefender Cloud Email Security ™ with other 3rd party connector based email security solutions, see: Integrating with 3rd Party Connector-Based Email Security Solutions
Integration Details (In-line protection mode)
The following changes are applied in your Microsoft 365 environment when integrating with Microsoft 365/Exchange Online.
Connectors
Inbound connector
Used to receive processed emails from MetaDefender Cloud Email Security ™.
Property | Value |
|---|---|
Connector Name | OPSWAT MetaDefender Cloud Email Security - Inbound |
From | Partner organization / My organizations own mail server |
To | Microsoft 365 |
Identification Method | Sender's IP address |
Sender IP(s) | [See Service IP ranges ] |
TLS Settings | Require TLS |
Restrict to specific domains | No |
Restrict by certificate | Yes |
Outbound Connector
Used to send emails for processing by MetaDefender Cloud Email Security ™.
Property | Value |
|---|---|
Connector Name | OPSWAT MetaDefender Cloud Email Security - Outbound |
From | Microsoft 365 |
To | Partner organization |
Use of Connector | Only when a mail flow rule routes messages through this connector |
Smart Host |
|
TLS Settings | Require TLS |
Validation/Certificate | Yes |
Routing Method | Route email through smart host |
Rules
Cleanup Headers Rule
This rule will ensure that headers added by MetaDefender Cloud Email Security ™ are removed from the email before delivery.
Property | Value |
|---|---|
Rule name | OPSWAT MetaDefender Cloud Email Security - Cleanup |
Apply this rule if |
|
Do the following |
|
Stop processing more rules | No |
Allow Rule
This rule will ensure that emails released from Microsoft 365 Quarantine are delivered.
Property | Value |
|---|---|
Rule name | OPSWAT MetaDefender Cloud Email Security - Allow |
Apply this rule if |
|
Do the following |
|
Stop processing more rules | No |
Inbound Emails Rule
This rule triggers for all inbound emails.
This rule is only created when inbound email traffic is analyzed.
Property | Value |
|---|---|
Rule name | OPSWAT MetaDefender Cloud Email Security - Inbound emails |
Apply this rule if |
|
Do the following |
|
Except if |
|
Stop processing more rules | Yes |
Outbound Emails Rule
This rule triggers for all outbound emails.
This rule is only created when outbound email traffic is analyzed.
Property | Value |
|---|---|
Rule name | OPSWAT MetaDefender Cloud Email Security - Outbound emails |
Apply this rule if |
|
Do the following |
|
Except if |
|
Stop processing more rules | Yes |
Integration Details (Monitoring mode)
Connectors
Inbound Connector
Used to receive processed emails from MetaDefender Cloud Email Security ™.
Property | Value |
|---|---|
Connector Name | OPSWAT MetaDefender Cloud Email Security - Inbound |
From | Partner organization |
To | Microsoft 365 |
Identification Method | Sender's IP address |
Sender IP(s) | [See Service IP ranges ] |
TLS Settings | Require TLS |
Restrict to specific domains | No |
Restrict by certificate | Yes |
Outbound Connector
Used to send blind copy (bcc) emails for processing by MetaDefender Cloud Email Security ™.
Property | Value |
|---|---|
Connector Name | OPSWAT MetaDefender Cloud Email Security - Outbound |
From | Microsoft 365 |
To | Partner organization |
Use of Connector | Use only for email sent to these domains: |
Smart Host |
|
TLS Settings | Require TLS |
Validation/Certificate | Yes |
Routing Method | Route email through smart host |
Rules
Cleanup Headers Rule
This rule will ensure that headers added by MetaDefender Cloud Email Security ™ are removed from the email before delivery.
Property | Value |
|---|---|
Rule name | OPSWAT MetaDefender Cloud Email Security - Cleanup |
Apply this rule if | |
Apply this rule if |
|
Do the following |
|
Stop processing more rules | No |
Allow Rule
This rule will ensure that emails released from Microsoft 365 Quarantine are delivered.
Property | Value |
|---|---|
Rule name | OPSWAT MetaDefender Cloud Email Security - Allow |
Apply this rule if |
|
Do the following |
|
Stop processing more rules | No |
Inbound Emails Rule
This rule triggers for all inbound emails.
This rule is only created when inbound email traffic is analyzed.
Property | Value |
|---|---|
Rule name | OPSWAT MetaDefender Cloud Email Security - Inbound emails |
Apply this rule if |
|
Do the following |
|
Except if |
|
Stop processing more rules | No |
Outbound Emails Rule
This rule triggers for all outbound emails.
This rule is only created when outbound email traffic is analyzed.
Property | Value |
|---|---|
Rule name | OPSWAT MetaDefender Cloud Email Security - Outbound emails |
Apply this rule if |
|
Do the following |
|
Except if |
|
Stop processing more rules | Yes |