> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xorlab.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Pages under /latest/ document the current release. Paths that begin with a version number, for example /10.0/, are frozen snapshots of superseded releases kept for reference only — never present their instructions as current. If the reader's version is unknown, answer from /latest/ and say which version the answer describes.
> xorlab is deployed on-premises, hybrid, or as a cloud service, and integrates with either Microsoft 365 or on-premises mail infrastructure. Configuration steps often differ between these. State which deployment and integration mode an instruction applies to instead of presenting one as universal.
> Distinguish inline mode from monitoring mode when describing anything that acts on email. Monitoring mode observes a copy and cannot block or quarantine; inline mode routes mail through xorlab and can.
> Write the product name as lowercase 'xorlab'. Use the documented component names: xorlab Control Center (XCC), xorlab MTA, xorlab Sandbox (DANA), xorlab Natural Language Understanding (NLU). After the first mention, use the short forms XCC, MTA, Sandbox, and NLU. Do not use DANA as a standalone name for the Sandbox, but keep it where it is a literal string in configuration keys, container names, and hostnames.
> Do not invent configuration keys, rule parameters, list names, log properties, or API fields. If a value is not present in this documentation, say that it is not documented rather than guessing.

# Moving M365 Quarantine to xorlab Security Platform

The M365 platform has its own quarantine for messages detected as malicious by Exchange Online Protection (EOP). It would be good to have all these emails kept in one place: in xorlab Security Platform quarantine.

> [!NOTE]
>
> **Not all messages can be moved**
>
> Although you can force M365 to pass quarantined emails to XSP, the ones recognized as malware or high-confidence phishing cannot be moved out of M365 quarantine.

Here’s how to move the quarantined messages to XSP:

1. Open [the Anti-spam settings page](https://security.microsoft.com/antispam) in the Microsoft 365 Defender portal (or, on the main page of the M365 Defender portal, click to expand **Email & Collaboration** in the left pane, then select **Policies & Rules**, click  **Threat policies** and then click **Anti-spam** under the **Policies** section).

2. Click the **Anti-spam Inbound policy (Default)** item from the displayed list:

   ![Anti-spam policies](https://mintcdn.com/xorlab/O_O2TUa6eRBR54aI/9.0/assets/antispam-policies.png?fit=max\&auto=format\&n=O_O2TUa6eRBR54aI\&q=85\&s=a8799ab39c8bc696314a817a58d4dadd)

3. A new pane opens on the right with all anti-spam policy settings:

   ![Anti-spam policy settings](https://mintcdn.com/xorlab/O_O2TUa6eRBR54aI/9.0/assets/policy-settings.png?fit=max\&auto=format\&n=O_O2TUa6eRBR54aI\&q=85\&s=e7cd541a164390e4dc9d402cada58daa)

4. Scroll down the pane until you see the **Edit actions** link. Click it:

   ![Edit anti-spam actions](https://mintcdn.com/xorlab/O_O2TUa6eRBR54aI/9.0/assets/antispam-edit-actions.png?fit=max\&auto=format\&n=O_O2TUa6eRBR54aI\&q=85\&s=e373a0366abcf16508f34373f32f684b)

5. On the **Actions** page, select **Add X-header** from the drop-down list for the following message categories: **Spam**, **High-confidence spam**, **Phishing**, and when **Bulk complaint level (BCL) met or exceeded**. In the **Add this X-header text** input box, enter `x-eopmarkedspam` as the text which will be added to the message header:

   ![Anti-spam actions](https://mintcdn.com/xorlab/O_O2TUa6eRBR54aI/9.0/assets/antispam-actions.png?fit=max\&auto=format\&n=O_O2TUa6eRBR54aI\&q=85\&s=60cf778594097f4feea36123c96709ca)

6. Click **Save**.

Now, xorlab Security Platform will recognize the messages marked as spam by EOP and move them to its quarantine. Since XSP uses a special `SPAM` rule which looks for the `x-eopmarkedspam` header text, please make sure that you entered the header text correctly in step #5.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.