Why Microsoft 365 quarantine holds legitimate email

Microsoft 365 quarantine holds legitimate business emails when filtering detects suspicious content, authentication failures, impersonation or a match with an organisation’s mail flow rules. A familiar sender does not override those checks. Before releasing a message, establish why it was held and whether the evidence supports delivery.

Repeated false positives need a configuration review, rather than a broad exception that weakens protection. Start with the message details, then identify whether the problem belongs to the sender, the receiving organisation or an incorrectly applied policy.

Key Takeaways

  • Microsoft 365 can quarantine legitimate email because of authentication failures, spam or phishing detection, suspicious content, or an organisation’s mail flow rules.
  • Review the quarantine reason, sender details and authentication evidence before releasing a message. Passing authentication doesn’t prove that an email is safe.
  • Release decisions and configuration changes are separate: releasing one message doesn’t fix the cause or stop future messages from being quarantined.
  • Retention and release options depend on the detection category, policy and permissions. Check the message’s expiry date and use appropriately scoped administrator access.
  • Correct the underlying sender or policy issue where possible, and avoid broad exceptions that weaken protection.

Why legitimate messages trigger quarantine

Quarantine is a secure holding area for suspicious or potentially harmful emails and attachments detected by Exchange Online Protection or Microsoft Defender for Office 365. It keeps the message away from the inbox whilst allowing authorised review.

A white envelope and a small red warning marker sit inside a mesh metal desk tray on a shelf.

Authentication and sending systems

A genuine supplier can send through a poorly configured marketing platform, invoicing service or support system. If that service is not correctly authorised, the message may fail authentication or resemble domain spoofing. A familiar sender address doesn’t rule out a suspicious email.

Forwarding can also affect authentication results. The correct response depends on the failed check and how the message travelled, rather than whether the sender appears familiar.

Content and policy decisions

Other reasons include spam or bulk-mail classification, phishing indicators, impersonation, suspicious links, malicious links, malware and viruses in attachments. An internal mail flow rule can also quarantine a message even when the sender is genuine.

Some policies hold legitimate bulk mail separately from other threat categories. This is a useful description of bulk quarantine, not the name of a specific Microsoft setting.

These categories need different responses. A bulk-mail false positive does not justify changing malware protection, and releasing 1 message does not correct the policy responsible. Our guidance on Microsoft 365 anti-phishing configuration explains the controls that need reviewing together.

Find and review an email in Microsoft 365 quarantine

Use the Microsoft 365 Defender portal to find quarantined email, rather than relying on Outlook search. Users normally see messages addressed to them, subject to their permissions and quarantine policy. Administrators with suitable access can investigate messages across the organisation.

Locate the held message

Follow these steps:

  1. Open the Microsoft 365 Defender portal using your organisation’s normal sign-in route.
  2. Select Email & collaboration, then Review, then Quarantine.
  3. In the quarantine portal, open the Email view and filter by recipient, sender, subject or received date.
  4. Select a message to inspect its details, quarantine reason and available actions.

Microsoft’s user quarantine guidance describes the available views and actions. If the expected message is absent, widen the date filter before assuming it was never received.

Check the authentication evidence

Review the sender address, return path, detection technologies and headers. Check the Sender Policy Framework (SPF), DomainKeys Identified Mail (DKIM) and Domain-based Message Authentication, Reporting and Conformance (DMARC) results.

SPF checks authorised sending infrastructure, DKIM validates a signature, and DMARC checks alignment with the visible From domain. A different return path can be legitimate for a mailing service, and doesn’t alone establish fraud.

An overhead view of two hands holding a blurred document on a desk next to a closed laptop and notebook.

Passing authentication does not prove safety. A compromised supplier mailbox can send authenticated messages containing fraudulent instructions.

What each quarantine action does

Available actions depend on the threat category, quarantine policy and account permissions.

ActionWhat it does
Preview messageDisplays the message for review without delivering it to the inbox.
View message headersShows routing, authentication and other technical evidence.
Release messageDelivers the held message to the selected recipient or recipients.
Request releaseAsks an administrator to review delivery when direct release is unavailable.
Block senderAdds a sender restriction where the action is available.
Delete messagesRemoves selected items from quarantine without delivering them. The item leaves review, and deletion may be a hard delete. Confirm the action’s effect in the portal before assuming the item can be recovered.

Request release is not delivery approval. The message remains held until an authorised reviewer releases it.

Users can’t necessarily release messages classified as malware or high-confidence phishing. A missing Release option may therefore reflect an intentional security restriction rather than a portal fault.

Administrators should use appropriately scoped access, such as the Quarantine Administrator role, instead of Global Administrator for routine handling. Microsoft’s administrator quarantine guidance explains the permissions and management actions.

Keep privileged accounts separate from daily email and browsing. A quarantine review shouldn’t require routine use of the tenant’s most powerful account.

Apply the checks to a supplier invoice

For a quarantined supplier invoice, review the sender’s full address and quarantine reason before considering the payment request. Compare the message with the expected transaction, including the purchase order, invoice timing and established contact.

An authentication failure may indicate a supplier’s invoicing platform needs correcting. Passing authentication still leaves the possibility of a compromised mailbox. Neither result settles whether changed bank details are genuine.

Confirm payment changes using a telephone number already held in trusted records, rather than contact details supplied in the email. Keep payment approval separate from the decision to release the message.

Once the content and sender have been assessed, release it or request administrator approval. Our explanation of how phishing bypasses standard filters covers why familiar accounts and plausible business conversations still need scrutiny.

How long Microsoft keeps quarantined email

Microsoft 365 quarantine does not have a universal 15-day or 30-day retention period. Retention depends on the detection category and applicable protection policy. The expiry date displayed against a message is the practical deadline for reviewing it.

For spam, bulk mail and phishing handled through default or custom anti-spam policies, the default retention is generally 15 days. Standard and Strict preset security policies use 30 days. Anti-malware and mail-flow-rule quarantine retention is 30 days.

Microsoft’s quarantine retention guidance sets out these differences. This explains why instructions for two organisations can quote different periods without describing the same configuration.

Expired messages are automatically deleted and cannot be recovered after expiry. The service is not an archive or a substitute for retaining business records.

Review time-sensitive correspondence promptly. A weekly notification schedule can leave less time to investigate a held invoice, contract or customer response before expiry.

Notifications and messages that are not visible

Quarantine notifications are optional, policy-controlled messages, not proof that every held email is visible to its recipient. An organisation can allow notifications for some categories while reserving others for administrator review.

How notifications work

Microsoft supports notification schedules of every 4 hours, daily or weekly. A daily spam digest is one possible arrangement, not a universal setting.

Depending on permissions, notifications can offer review, release or block-sender actions. Microsoft’s quarantine notification documentation explains the supported options.

Genuine Microsoft quarantine emails exist, but attackers can imitate them. Open the Defender portal through a known route if a notification is unexpected. A Microsoft logo or familiar display name isn’t sufficient evidence.

When the email is missing

Check Outlook’s junk folder as well as quarantine. Mail in the junk folder is still in the mailbox; quarantined mail is held separately.

If neither location contains the message, administrators should use Exchange Online message trace to establish whether Microsoft received, rejected, delivered or redirected it. If trace shows rejection, the sender may receive a non-delivery report (NDR), though one isn’t always generated. Review inbox rules and forwarding where trace shows delivery but the user can’t find the message.

Post-delivery protection can also remove messages after they arrive. Zero-hour auto purge can move messages to quarantine or Junk, depending on the detection and policy.

Our Microsoft 365 support services cover configuration and troubleshooting when message handling needs investigation beyond a single release.

Reduce false positives without weakening protection

The receiving organisation cannot always fix the underlying cause. Authentication problems may need changes by the sender or its email platform, whilst an internal rule or incorrectly scoped protection policy needs action within the receiving tenant.

Correct the cause before adding exceptions

Identify the policy or detection responsible, including which spam filters acted, before making an exception. Then review a representative message with its headers. Submit an incorrectly classified message to Microsoft for analysis where the available workflow permits.

For authentication failures, the sender may need to correct SPF authorisation, enable DKIM signing or resolve DMARC alignment. Avoid allowing an entire domain just because 1 invoice was blocked.

An Office 365 security assessment can review these settings alongside forwarding rules, permissions and account protection when problems suggest a wider configuration issue.

Configure handling and ownership deliberately

Review anti-spam, anti-phishing, anti-malware, Safe Links and Safe Attachments policies, depending on your licensing. Check which users each policy covers and whether impersonation protection includes relevant senior staff, finance contacts and business domains.

Distinguish threat policies from quarantine policies. Threat policies determine detection responses; quarantine policies control user permissions and notifications.

Assign responsibility for release requests, escalation and recurring false positives. Our anti-phishing services can support configuration and user-reporting processes together, rather than treating every held message as an isolated help-desk task.

Frequently asked questions

Can you turn off quarantine in Outlook?

Outlook does not control organisation-wide quarantine. Administrators configure protection actions in Microsoft 365. Disabling protection to recover legitimate mail creates wider exposure; investigate the detection and apply the narrowest justified correction instead.

Does releasing a message allow future emails?

Releasing a message delivers that item. It does not automatically repair sender authentication or change the policy that caused the hold. Future messages may therefore be quarantined again unless the underlying problem is addressed.

Restore delivery without creating a wider exception

A legitimate email in quarantine needs 2 decisions: whether that message is safe to release, and whether the underlying configuration needs changing. Keep those decisions separate so that an urgent business request does not become a permanent filtering bypass.

Speak to our team about business email security services to investigate recurring quarantine problems, review Microsoft 365 protection and establish a clear release process.

Previous Post
Next Post

Leave a Reply

Your email address will not be published. Required fields are marked *

Most Recent Posts

  • All Post
  • Anti Phishing
  • Antivirus
  • Branding
  • Cybersecurity
  • Dark Web Monitoring
  • Development
  • General
  • Guides
  • IT Support
  • Leadership
  • Management
  • Microsoft 365
  • Network Penetration Testing
  • Online security
  • Outsourcing
  • Technology
  • Uncategorised

Company Info

She wholly fat who window extent either formal. Removing welcomed.

Let's talk

IT support that feels like part of your team.

Tell us what is slowing your organisation down. An experienced specialist will help you understand the most practical next step.

Average response time: 4 business hours

Global capability. Local accountability.

6 global locations. One local point of contact. London-based support.

Dependable IT support and cyber security for ambitious organisations in London and around the world.

London

The Leadenhall Building
122 Leadenhall Street
London EC3V 4AB

Brussels

Schuman Roundabout 2–4
1040 Brussels

New york

14 Wall Street, 20th floor
New York, NY 10005

Paris

33 Rue La Fayette
75009 Paris

San Francisco

75 Broadway, Suite 202
San Francisco, CA

Singapore

Marina Bay Financial Centre
10 Marina Boulevard

© 2026 Northern Star. All rights reserved.