> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/documentation/crates/existing-crate-documentation/microsoft-365-quarantine-email-release-crate.md).
# Microsoft 365 Quarantine Email Release Crate
{% hint style="info" %}
If you’re new to Crates, read through our introductory Crate documentation [here](https://docs.rewst.help/prebuilt-automations/crates). Find the Crate in our Crate Marketplace.
{% endhint %}
## What does the Microsoft 365 Quarantine Email Release Crate do?
Our Microsoft 365 Quarantine Email Release Crate has a technician fill out a form where they select an organization, a ticket to update, and a individual or all users to list quarantine emails. They then select a quarantine message and can allow the sender or not and release the email to all or the individual.
## Crate prerequisites
The [Microsoft Cloud Integration Bundle](/documentation/integrations/integration-guides/microsoft-cloud-integration-bundle.md) must be set up before unpacking this Crate.
## Unpack the Microsoft 365 Quarantine Email Release Crate
1. Navigate to **Marketplace > Crates** in the left side menu of the Rewst platform.
2. Search for `Microsoft 365 Quarantine`.\
\
3. Click on the Crate tile to begin unpacking.
4. Click **Unpack Crate**.
5. Click **Continue**.
6. Enter your estimated time saved into the **Time Saved (seconds)** field.
7. Click **Unpack**.
### Test the Crate
1. Navigate to **Automations > Workflows**.
2. Search for `M365 Quarantine Release`.
3. Click on the workflow to open it in the Workflow Builder. Note that this workflow is triggered by a form submission.
4. Click on the trigger in the workflow to open its settings in the right side menu.
5. Click **Copy URL**.
6. Copy the URL for the organization that you wish to use for your test.
7. Paste the URL into a new browser tab.
8. Fill out the form as follows:
1. Choose the organization that you want to release an email from.
2. Choose a ticket that you want updates to be posted to.
3. Select if you want to search an individual mailbox or all users mailbox. If individual, select the user.
4. Select the email to release.
5. Choose to allow or deny future messages from the sender.
6. Choose to release the email to all recipients, or only the selected user.
9. Click **Submit**.
10. Click  **> Execution History** to view the results of the workflow. If there are errors in the result record, the Crate is not working properly.
{% hint style="info" %}
Got an idea for a new Crate? Rewst is constantly adding new Crates to our Crate Marketplace. Submit your idea or upvote existing ideas here in our [Canny feedback collector](https://rewst.canny.io/crates).
{% endhint %}
---
# 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.rewst.help/documentation/crates/existing-crate-documentation/microsoft-365-quarantine-email-release-crate.md?ask=&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.