> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/microsoft-exchange/getting_started/installing-microsoft-exchange.md).

# Installing Microsoft Exchange

This document explains the process of installing Exchange. Nightfall DLP for Exchange allows you to scan all outgoing emails for sensitive data. Nightfall can scan both, email body and attachments.

## Overview 

When Nightfall detects emails with sensitive data, it can either Block, Quarantine, or Encrypt the email, based on the automated actions configured in the sensitive data policy for Exchange. You must perform the following configurations to set up monitoring of Outlook mails.

**Create Connectors**: In the Exchange portal, you must configure Connectors in your Exchange to route Emails to Nightfall to be scanned and then back to your Exchange server, once scanned.

**Create Rules**: In the Exchange portal, you must configure rules which enable Nightfall to route your emails. 

**Create MX Record**: You must create an MX record in the Nightfall application. This record describes your organization’s Microsoft 365 domain name and MX record.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.nightfall.ai/microsoft-exchange/getting_started/installing-microsoft-exchange.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.