> For the complete documentation index, see [llms.txt](https://docs.mailtrap.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mailtrap.io/email-live-sending/troubleshooting/ms-office-365-quarantine.md).

# Office 365 quarantine

How to resolve your emails sent from Mailtrap Email Live Sending being sent to Office 365 quarantine.

Sometimes transactional messages from Mailtrap (such as email confirmations, invitations to join a sandbox, invoices, etc.) can be sent to Threat Management >> Quarantine by MS Office 365.

### Solution

If you have faced this issue, follow these steps to resolve it:

{% stepper %}
{% step %}
**Access Office 365 Quarantine**

Go to <https://protection.office.com/#/quarantine>.
{% endstep %}

{% step %}
**Select Mailtrap Emails**

Select the emails sent from Mailtrap that are in quarantine.
{% endstep %}

{% step %}
**Release Messages**

Click the **Release messages** button.
{% endstep %}

{% step %}
**Add to Allow List**

Check the **"Add sender to your organization's allow list"** checkbox.

This will prevent future emails from Mailtrap from being quarantined.
{% endstep %}
{% endstepper %}

### Alternative: OAuth Integration

When signing up for Mailtrap, you have the option to use Office 365 account authorization (OAuth) for smooth integration. In this case, email confirmation won't be required and you can avoid quarantine issues altogether.

### Related Articles

* [Getting Started with Email Live Sending](https://docs.mailtrap.io/general/sending-domain.md)
* [Email Live Sending FAQs](https://docs.mailtrap.io/general/faq.md)


---

# 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://docs.mailtrap.io/email-live-sending/troubleshooting/ms-office-365-quarantine.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.
