Skip to main content
Here you will learn how to integrate xorlab with your Microsoft 365 environment to monitor email traffic. You can use xorlab to passively monitor incoming, outgoing, and internal emails. Passive monitoring is useful when you want to observe email traffic without affecting the mail flow. This approach is often used during the proof of value (PoV) phase.
We will use example.com as the example for an Microsoft 365 domain and we will assume that xorlab runs under xorlab.example.com.For a cloud deployment, we will use mx.xyz.activeguard.cloud in the examples.
PrerequisitesTo monitor your Microsoft 365 environment with xorlab, you will need:
  • Access to the Microsoft 365 Admin Center.
  • The email address of your xorlab instance, e.g., monitor@xorlab.example.com or monitor@mx.xyz.activeguard.cloud.

Configuration

  1. Go to the Exchange Admin Center, in its left pane click Mail flow and, in the expanded list of items, click Rules: Selecting Mail Flow Rules Selecting Mail Flow Rules
  2. On the Rules screen that appears, click the plus (+) icon and select Create a new rule… from the drop-down list. Creating a new rule Creating a new rule
  3. A new pane opens with input fields for setting new rule conditions. Create a rule for incoming emails with the following settings:
    • Enter IncomingBCCxorlab in the field under Name.
    • Click the drop-down list under Apply this rule if to expand it and choose The sender, then click the Select one drop-down list on the right to expand it and select is external/internal, and finally choose Outside the organization from the select sender location list.
    • Click the plus icon (+) at the end of condition lists for Apply this rule if to add another condition. Click the drop-down list under the new And condition to expand it and choose The recipient, then click the Select one drop-down list on the right to expand it and select is external/internal, and finally choose Inside the organization from the select recipient location list.
    • Click the drop-down list under Do the following to expand it, select Add Recipients, then click the Select one drop-down list on the right to expand it and select to the Bcc box, and finally select the xorlab Security Platform monitoring mailbox address from the list of recipients or enter it manually, e.g., monitor@xorlab.example.com or monitor@mx.xyz.activeguard.cloud, where xyz is your customer ID for your xorlab instances.
    The resulting rule conditions should look as depicted in the screenshot below: Rule settings for incoming emails Setting up a rule for incoming emails
  4. Click Next.
  5. On the next Set rule settings page, leave all settings at their defaults. Click Next.
  6. Review the settings for your rule on the last page and if they are OK, click Finish, then Done when the transport rule is created.
  7. Repeat steps #2-6 to add another rule—this time, for outgoing emails: name it OutgoingBCCxorlab, set the sender to be from inside the organization and the recipient from outside the organization. See the screenshot below: Rule settings for outgoing emails Setting up a rule for outgoing emails
Now, a copy of every incoming and outgoing email will be sent to xorlab.

Including internal emails

The above configuration monitors only the cross-border communication (incoming to and outgoing from your organization). If you want to include also internal email communication, follow steps #1-6 above, but in step #3 create just one rule for all messages by setting these properties:
  • Name: BCCxorlab
  • Apply this rule if → Apply to all messages
  • Do the following… → BCC the message to… → select the xorlab monitoring mailbox address from the list of recipients or enter it manually, e.g., monitor@xorlab.example.com or monitor@mx.xyz.activeguard.cloud, where xyz is your customer ID for your xorlab instances.
Configuring the monitor rule Configuring the monitor rule required to send a copy of all emails to xorlab Now, a copy of every email will be sent to xorlab.

Monitoring mode using a connector

In addition to the integration above, it is possible to force BCC emails to xorlab through an additional connector instead of using a transport rule. This can be required in the following cases:
  • You already have an existing connector that interferes with the BCC emails sent to xorlab.
  • You have a hybrid MS setup with an on-prem-only email delivery (Centralized Mail Transport) and you would like to send the BCC emails directly with M365 to xorlab.
To set up a monitoring mode using a connector, follow the instructions on how to create an M365 connector to xorlab, with the only difference being a different use of connector (step #4 in the referenced article):
  1. On the Home screen of the Exchange admin center click Mail flow in the left pane and in the expanded list of items click Connectors: Mail flow connectors Exchange admin center
  2. On the Connectors page, click Add a connector. Add a connector Adding a connector
  3. Select Office 365 under Connection from and Your organization’s email server under Connection to and click Next: New connector from O365 Adding a new connector from M365
  4. Set the name of the connector to Microsoft365Toxorlab on the Connector name screen and click Next: Connector name from M365 Setting the connector name
  5. On the Use of connector page, choose the third option Only when email messages are sent to these domains and enter your xorlab domain as specified in the templateDomain property (see step #7 in Basic settings), e.g., mx.xyz.activeguard.cloud: Use of connector Defining the use of connector
  6. Click the plus (+) icon to add your domain and click Next.
  7. Add a new smart host with the domain that resolves to the xorlab MTAs on the Routing screen by entering them and clicking the plus (+) button. If your customer ID for your xorlab instances is xyz you should add mx.xyz.activeguard.cloud. When you’re done, click Next: Routing Selecting the host for delivered messages
  8. On the Security restrictions page activate the Always use Transport Layer Security… option and select Issued by a trusted certificate authority (CA). Click Next: Security restrictions Security restrictions
  9. Enter an email address in your connected mailbox where a validation email should be sent on the Validation email screen, click Validate and, after validation, click Next: Validation email Providing the validation email address
    Unsuccessful validationThe connector validation might fail at this point. If this happens, save the connector without validation, and then validate the connector again.
  10. Review the connector and click Create when it’s OK.