Skip to main content

Prepare xorlab

  1. Open shared/guarded_tenants.yml and add all email address patterns that are allowed to report emails.
    guarded_tenants.yml
  2. Choose if you want to enable or disable automatic feedback. If enabled, every reporter will get an immediate feedback email.

    Automatic feedback

    guarded_tenants.yml

    Disabled feedback

    guarded_tenants.yml
  3. Optional: Change the sender address used for feedback emails: Change Sender Address.
  4. Click Publish. The new configuration becomes active within about one minute.

Forward M365 reported emails to xorlab

  1. You need a dedicated mailbox in M365 that receives reported emails. If you don’t have one, create one like reporting@example.com.
  2. In the M365 Defender portal go to SettingsEmail & collaborationUser reported settings. Or directly via User submissions.
  3. Activate Monitor reported messages in Outlook.
  4. Scroll down to Reported message destinations and add the mailbox from step #1 to the mailbox field. Choose either My reporting mailbox only or Microsoft and my reporting mailbox in the dropdown. Email address for reported messages
  5. Click Save.
  6. Go to Exchange Mail Flow and create a new rule with the name xorlabReportingIntegration:
    • Apply this rule ifThe recipientis this person and select your mailbox from step #1.
    • Do the followingRedirect the message to → enter the xorlab reporting address suspicious@mx.xyz.activeguard.cloud, where xyz is your customer ID.
    Reporting rule conditions
  7. Click Next until Finish, then Done.
  8. Enable the new rule.

Test the integration

  1. Report an email via the M365 built-in button. It is available in the web interface as well as in Outlook.
  2. In xorlab, go to Abuse MailboxAll Cases and there you should see the reported email. It can take up to 30 seconds to appear.
  3. If you enabled automatic feedback in the beginning, you should receive a feedback email within 30 seconds.

How to change the reporting address

The default address under which xorlab will listen for reported emails is suspicious@<templateDomain>, with templateDomain referring to the parameter that’s set in active_guard.yml. If you like to customize the sender address, add the following block (if it does not already exist) to the active_guard.yml file:
active_guard.yml
Afterward, click Publish. The scanSources handler settings become active within about one minute.

How to automate reported email handling

For further information about automation, have a look at Abuse Mailbox.

How “Not Junk” reports are handled

When you integrate M365 reporting, xorlab adds one of the following tags to each reported email:
  • #reportedasnotjunk for messages reported as Not Junk
  • #reportedasjunk for messages reported as Junk
  • #reportedasphishing for messages reported as Phishing
Default behavior:
  • Not Junk: the case is automatically resolved as benign by REPORTED_NOT_JUNK_decision, no acknowledgment email is sent, and the #reportedasnotjunk tag is added.
  • Junk/Phishing: the corresponding tag is added, acknowledgment is sent (if enabled), and the case is handled by normal reported-email analysis.
REPORTED_NOT_JUNK_decision is evaluated before campaigns, so these cases are auto-resolved before campaign rules are applied. To disable this auto-resolve behavior and return to normal reported-email handling, set the rule state to PASSIVE in /activeguard/core/rule_sets/90_local/params/local.properties:
local.properties
Then click Publish. The rule-set configuration becomes active within about one minute.

Multi-Tenancy

Repeat this integration for each M365 tenant. In addition, xorlab needs to know which tenant a reported email belongs to, which is decided by a header on the carrier email:

Assign Reported Emails to Tenants

Add the x-ag-tenant header so that reported emails end up in the right tenant.
Note that local.properties above applies to all tenants. To change this behavior for a single tenant only, see Manage Tenant Rules.

Next steps

The M365 integration is complete: