> For the complete documentation index, see [llms.txt](https://doc.keepnetlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.keepnetlabs.com/next-generation-product/getting-started/recommended-add-domains-to-url-protection/allow-list-for-exchange-2013-2016.md).

# Allow List for Exchange 2013/2016

To complete this procedure, you must have security administrator privileges with the Microsoft Security & Compliance Center or be a member of the Microsoft Exchange Online Organization Management administrator group.

1. Note the [IP addresses](https://doc.keepnetlabs.com/Next-Generation-Product/getting-started/whitelisting#ip-addresses-and-domains-to-allow) to be allowed.
2. Log in to your exchange admin center.
3. From the left sidebar menu, go to **Mail flow > Connectors**.
4. Click **Add a connector**.
5. Select **Partner organization** in the **Connection** from the section.
6. Give the connector a name and click **Next**.
7. In the **Authenticating sent email** window, select the option that states **By verifying that the IP address of the sending server matches one of the following IP addresses that belong to your partner organization**.
8. Enter the IP addresses and click **Next**.
9. Uncheck the TLS option stating **Reject email messages if they are not sent over**.
10. Click **Next**, then click **Save** to complete the process.

You must complete the following steps once the **connector** is defined.

1. Go to the **Mail flow > Rules** page in the left sidebar menu.
2. Click the **+ icon** on the screen and select **Bypass spam filtering**.
3. In the **New rule** window, give the rule a name and select **The sender is ... > IP address is in any of these ranges or exactly matches.**
4. Enter the IP addresses and click **OK**.
5. In the **Do the following** section, select Set the message header to this value ... > Set a message header and enter **“X-MS-Exchange-Organization-Bypass Clutter”** in the text field, and click **OK**.
6. Set the value information to **true** with the enter text option on the right.
7. Click **Save** to complete the process.

✅ **You have now Allow List Domains so your target users can successfully open Keepnet email links. Please also Allow List in your security solutions if you haven't already.**

**Next step is to** [**Setup your Phishing Reporter**](https://github.com/ucarozan/keepnet-docs/blob/main/next-generation-product/getting-started/6.-setup-phishing-reporter) **➡️**


---

# 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 dynamically by asking a question.

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

```
GET https://doc.keepnetlabs.com/next-generation-product/getting-started/recommended-add-domains-to-url-protection/allow-list-for-exchange-2013-2016.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 `build a script that syncs our docs to a CMS` 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.
