> ## 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.

# Integration Overview

> Where to start integrating xorlab, including the choice between the Microsoft 365 and on-premises paths.

**Start here.** These three steps are the complete, standard xorlab integration — mail flow, user login, reporting, and the optional Microsoft 365 features. Follow them in order.

1. Follow [Before You Begin](/latest/before-begin-integration).
2. Choose your integration:

   <CardGroup cols={2}>
     <Card title="M365" icon="microsoft" href="/latest/m365-integration-overview">
       Integrate xorlab with your M365. Use this also for hybrid setups where you receive and send emails via M365.
     </Card>

     <Card title="On-premises" icon="server" href="/latest/on-prem-integration-overview">
       Integrate xorlab with your on-premises infrastructure. Use this also for hybrid setups where you receive and send emails on-premises.
     </Card>
   </CardGroup>
3. After you completed the integration above, follow [Next Steps](/latest/integration-next-steps).

## What changes in your environment

The integration is made of settings in your own admin portal — connectors, mail flow rules and an app registration. Nothing is installed on your servers, clients or endpoints, no mailbox is moved, and with M365 your MX records keep pointing at Microsoft.

<Card title="Review What Changes in Your Environment" icon="list-check" horizontal href="/latest/integration-impact">
  Which settings each path adds, what it leaves untouched, what your users notice, and how to undo it.
</Card>

<Card title="What Integrating xorlab Involves" icon="server" horizontal href="/latest/admin-essentials">
  The wider picture around these steps: choosing between SaaS and on-premises, what your users notice, and what you maintain once the integration is live.
</Card>

## Multi-Tenancy

If you protect multiple organizations with a single xorlab instance, do not follow the steps above one by one. Instead, onboard each organization as a tenant:

<Card title="Add a Tenant" icon="rocket-launch" horizontal href="/latest/multi-tenancy-new-tenant">
  Step-by-step guide that walks you through domains, routing, mail flow activation and the optional per-tenant features.
</Card>

See [Multi-Tenancy Overview](/latest/multi-tenancy-overview) for the full picture.