A legitimate business message can be quarantined by Microsoft 365’s phishing, spam, malware, Safe Attachments, or mail-flow protections. Releasing it without checking why it was stopped can turn a false positive into a security incident. This guide shows Microsoft 365 administrators how to review a quarantined email, release it only when the evidence supports that decision, and submit a false positive to Microsoft without creating an unnecessarily broad allow rule.
Before you begin
| Requirement | What to know |
|---|---|
| Portal | Use the Microsoft Defender portal Quarantine page. This guide covers cloud mailboxes. |
| Permissions | To take action for all users, use the least-privileged appropriate role: Quarantine Administrator, Security Administrator, or Organization Management. Read-only reviewers can use Security Reader, Security Operator, or Global Reader. |
| Licensing | Quarantine for email is available with the built-in protection for cloud mailboxes. Defender for Office 365 adds capabilities such as Safe Attachments quarantine for files and Teams-related scenarios. |
| Testing | These steps are verified against Microsoft documentation; they have not been tested in your tenant. Labels and available actions can vary by policy, role, and message verdict. |
Step 1: Open the email quarantine
- Sign in to Microsoft Defender with an account that has the required role.
- Go to Email & collaboration > Review > Quarantine, then select the Email tab. You can also open the direct Quarantine link above.
- Use Filter to narrow the results by sender, recipient, subject, time received, expiry, quarantine reason, policy type, or release status. The search box searches only the current view; use filters when you need a wider search.
Do not start by releasing the message. Select the row itself, rather than the check box, to open the details flyout first.
Step 2: Establish why Microsoft quarantined it
In the details flyout, record the Quarantine reason, Policy type, Policy name, sender, recipient, received time, and expiry time. Review the message headers, authentication results, URLs, and attachments where your role permits it. Typical reasons include bulk, spam, phishing, high-confidence phishing, malware, a transport rule, or a password-protected attachment.
| Signal | Safer interpretation |
|---|---|
| Unexpected sender or changed reply-to address | Treat it as suspicious until the sender is independently verified. |
| Authentication failure or a confusing domain mismatch | Do not rely on the visible display name. Verify the actual sender domain and the business context. |
| Malware or high-confidence phishing verdict | Do not release it simply because someone expects a message. Verify with the sender through a trusted channel and investigate the detection. |
| Transport rule match | Find the named rule and confirm whether it deliberately blocks this message type. Fix the rule only if the policy intent is wrong. |
Warning: Previewing, downloading, or releasing content has risk. Do not open attachments or follow links merely to “check” a message. Verify the business request separately—for example, call a known number or use an existing contact—not the details provided by the email.
Step 3: Release a confirmed false positive
- After the review supports release, select the message in the Quarantine page or in its details flyout.
- Select Release email. If the action is unavailable, your role or the quarantine policy may allow only a release request.
- When offered, select the intended recipient or recipients. Release only to the affected recipient; do not turn a one-message exception into a tenant-wide decision.
- Select the option to submit the message to Microsoft as a false positive when it is available and appropriate. This improves the signal Microsoft receives; it does not automatically release other similar messages.
- Confirm the release. The Released to and Released by fields should record the action. The message normally goes to the recipient’s Inbox or to another folder if mailbox rules apply.
Step 4: Verify delivery and document the decision
- Ask the recipient to confirm delivery without asking them to open a suspicious attachment.
- Check the release status and audit trail in Quarantine. Microsoft records actions taken by administrators and users.
- If the same sender or legitimate service is repeatedly blocked, investigate the underlying cause—authentication, domain alignment, content, a mail-flow rule, or a product configuration—before considering an allow entry.
When a release request is the right outcome
End users may be able to request a release based on the quarantine policy, but they cannot directly release certain high-risk verdicts. In particular, users cannot release messages quarantined as malware by anti-malware policies, as malware or phishing by Safe Attachments, or as high-confidence phishing by anti-spam. A request is an input to an administrator’s review—not evidence that the message is safe.
Avoid these common mistakes
- Creating a permanent allow rule after one false positive: first establish whether the original detection was correct and whether the sender’s authentication is healthy. Broad allow entries can weaken protection.
- Releasing malware or high-confidence phishing because the sender looks familiar: compromised mailboxes and lookalike domains make that unreliable.
- Assuming expired items can be restored: quarantined content is automatically and permanently deleted after its retention period expires.
- Using Global Administrator for routine review: Microsoft recommends least privilege. Assign a quarantine or security role suited to the task instead.
Troubleshooting
| Problem | What to check |
|---|---|
| Release option is missing | Confirm your role, the recipient scope, and the quarantine policy. A user may be limited to requesting a release. |
| The item is not visible | Clear or broaden filters, select Show all senders where appropriate, and check whether the item expired or was deleted. |
| Released message has not appeared | Review the release status, recipient mailbox rules, and message trace. Delivery may be redirected by a mailbox rule. |
| The same valid messages keep returning to quarantine | Submit a false positive, then investigate the responsible policy and the sender’s authentication rather than repeatedly releasing individual copies. |
Security and rollback considerations
Releasing a message is not a clean “undo” operation: it delivers the original content to the selected recipient. If you released something in error, contain the risk rather than assuming it can be recalled. Instruct the recipient not to interact with it, investigate any clicks or opened attachments, and use your incident-response process. Do not silently create allow rules to compensate for an incorrect release.
Related Guava Insights guides
- How to Enable Defender for Office 365 Preset Security Policies
- How to Configure Microsoft 365 SMTP Relay with an Inbound Connector

