Skip to main content
Print

How to Release a Quarantined Email and Allow a Blocked Sender in Microsoft 365

A vendor says they emailed you and you never got it. Or you receive a message from quarantine@messaging.microsoft.com with the subject You have messages in quarantine, listing mail you were expecting. The help desk request is always the same: “Can you whitelist this sender?”

This guide covers where Microsoft 365 holds a message, how a user releases it, how an admin creates an allow entry that works, and why Outlook Safe Senders usually does not. It most often affects finance and front desk staff receiving invoices from senders with weak email authentication.

Why This Happens

Exchange Online Protection scores every inbound message and acts on the verdict. Exchange Online Protection (EOP) is the filtering layer in front of every Microsoft 365 mailbox; Microsoft Defender for Office 365 adds impersonation and link protection. Each message receives a verdict such as spam, bulk, phishing, or malware, and the threat policies decide whether that means deliver, move to Junk Email, or quarantine.

Most legitimate mail is held because the sender failed authentication. If the vendor’s SPF record omits their sending service, they lack a DKIM signature, or their DMARC policy says reject, EOP treats the message as a possible spoof and quarantines it as phishing. Impersonation protection catches display names resembling your executives; bulk complaint level scoring catches newsletter platforms with many complaints. The sender’s IT holds the real fix.

The quarantine policy decides what the user may do. The default full-access policy lets users release their own messages, the limited-access policy lets them request release, and the admin-only policy, used for high confidence phishing and malware, hides the release option, so a user cannot talk themselves into releasing a credential harvesting email.

How to Fix It

Method 1: Find and release the message (user)

  1. Check the Junk Email folder first; spam and bulk verdicts go there, not to quarantine. Right-click and choose Report > Not junk (New Outlook and web) or Junk > Not Junk (Classic Outlook).
  2. Open the quarantine notification and click Review message, or go to security.microsoft.com/quarantine. You see only messages to you that your quarantine policy allows.
  3. Read the Quarantine reason and preview. Only release mail you were expecting from a sender you recognize; if it asks you to sign in or open an attachment, leave it and report it to IT.
  4. Click Release. If you see Request release instead, submit it for an admin to approve. If there is no button, the detection is admin-only; ask IT.

Method 2: Safe Senders in Outlook (limited value)

  1. Classic Outlook: Home > Junk > Junk E-mail Options > Safe Senders > Add. New Outlook and web: Settings > Mail > Junk email > Safe senders and domains > Add.
  2. Understand the limit: this delivers spam-classified mail from that sender to your Inbox rather than Junk. It does not override quarantine for phishing, spoof, impersonation, or malware verdicts, where most vendor mail is held.

Method 3: Release and allow correctly (admin)

  1. In security.microsoft.com, open Email & collaboration > Review > Quarantine. Filter by release status to find pending requests.
  2. Review the message and click Release. For a false positive, check Submit the message to Microsoft to improve detection, then Allow emails with similar attributes, which creates a Tenant Allow/Block List entry for the sender and any flagged URLs, with an expiration you choose.
  3. If the message is gone, submit it anyway: Actions & submissions > Submissions > Submit to Microsoft for analysis, choose Email, supply the Network Message ID or .eml file, select the reason that it should not have been blocked, and check Allow emails with similar attributes.
  4. Confirm the entry under Policies & rules > Threat policies > Tenant Allow/Block Lists > Domains & addresses. Domain and address allow entries can only be created through submissions and expire about 45 days after last use unless you set a date. Spoofed sender allow entries, on the Spoofed senders tab, can be created directly.

Method 4: Policy allow list (last resort, admin)

  1. Go to Policies & rules > Threat policies > Anti-spam, open the inbound policy that applies, and add the address under Allowed senders. Microsoft discourages this list because allowed mail skips spam and most phishing checks, so a spoofer who forges an allowed domain inherits the pass.
  2. Check for a blocking mail flow rule in the Exchange admin center under Mail flow > Rules, and any third-party filter in front of Microsoft 365, whose quarantine is separate.

How to Verify the Fix Worked

  • The released message is in the Inbox within minutes, and a fresh test from the sender lands there too, not in Junk or quarantine.
  • Admins: a message trace in the Exchange admin center under Mail flow > Message trace shows Delivered, not Quarantined or FilteredAsSpam.
  • The test message’s Authentication-Results header shows SPF, DKIM, and DMARC passing.

If It Still Isn’t Working

The message never reached Microsoft 365. If message trace shows nothing, the mail was rejected upstream by a third-party gateway, the sender’s outbound filter, or MX records pointing elsewhere. The 5.7.x code in the bounce names the system that refused it.

The allow entry exists but mail is still quarantined. Check the quarantine reason. A sender allow does not cover a malware verdict, nothing overrides high confidence phishing except an admin release, and entries expire. If only some users are affected, a different policy, often a Strict preset on executives, applies to them. Email & collaboration > Explorer (Defender for Office 365 Plan 2) shows the exact detection and policy per message.

If the sender’s authentication is the cause, stop allowlisting and send them the header results. Release an unexpected message only after IT has inspected it; HIPAA and cyber insurance carriers expect filtering decisions to be reviewed, not bypassed.

How Capital Techies Handles This for Managed Clients

For managed clients, Capital Techies tunes Exchange Online Protection and Microsoft Defender for Office 365 per client: quarantine policies that let users release ordinary spam but route phishing verdicts to our help desk, and allow entries created only through Submissions with an expiration date, never a standing domain allow. Every release is checked against the sender’s SPF, DKIM, and DMARC results, and KnowBe4 training reinforces one rule: never release a message you were not expecting.

The outcome is vendor mail that arrives on time without opening the door to business email compromise, plus an audit trail for your insurer. Learn more about our cybersecurity services or contact Capital Techies.

Frequently Asked Questions

Why can I not release a quarantined email myself?

The quarantine policy attached to that detection decides what you can do. High confidence phishing and malware use an admin-only policy by default, so the Release button is replaced by Request release or hidden. An administrator reviews it in the Defender quarantine and releases it if safe.

I added the sender to Safe Senders in Outlook. Why is their mail still quarantined?

Outlook Safe Senders only decides whether spam-classified mail lands in your Inbox or Junk folder. It does not override quarantine verdicts for phishing, spoofing, impersonation, or malware. Those need an admin allow entry created through Submissions, or a fix to the sender’s email authentication.

How long do quarantined messages stay before they are deleted?

Spam, bulk, and phishing quarantines keep messages for 15 days by default, and administrators can raise that to 30. Malware and high confidence phishing are kept for 30 days. After that the message is purged and cannot be recovered.

Related Articles

Table of Contents