Public mode

No tenant, Graph, or device access. Every item links to its source. What this means

Some sources or documents need attention: 253/255 feeds/APIs · 417/444 docs · checked 13:25 UTC Customize Public modeDiscuss ChangeIntel on Discord

MDO Encrypted email attachment protection

Versions captured by this deployment. Earlier versions and notices may be missing; first observed is not first published.

Rollout

Ends
28 Dec 2026

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Microsoft's start date
27 Jul 2026
Last changed by Microsoft
27 Jul 2026
First seen here
19 Oct 2026
Versions seen
1

What the notice says

Microsoft's text, with its sections, lists and tables; source markup removed

What and Why

Organizations commonly use encrypted or password-protected attachments to securely share sensitive information through email. However, when Microsoft Defender for Office 365 cannot obtain the attachment password during scanning or detonation, the content cannot be fully analyzed for threats.

To help organizations reduce risk from unscanned content, Microsoft is introducing a new opt-in setting in Safe Attachments policies. This setting allows administrators to automatically quarantine email messages that contain password-protected attachments when Microsoft Defender for Office 365 cannot complete scanning or detonation. This enhancement provides administrators with greater control over potentially risky content while preserving business workflows through controlled release options.

Rollout Schedule

  • Worldwide: Early August 2026 through Late August 2026
  • GCC: Late August 2026 through Late September 2026
  • GCC High: Late August 2026 through Late October 2026
  • DoD: Late August 2026 through Late October 2026

Impact on Your Organization

Who is affected

  • Administrators managing Safe Attachments policies.
  • Security operations teams responsible for quarantine management.
  • Users who receive password-protected email attachments.

Platforms/Services

  • Microsoft Defender for Office 365
  • Safe Attachments
  • Quarantine
  • Advanced Hunting
  • Exchange Online

What will happen

  • This feature is off by default and requires administrator opt-in.
  • Administrators can configure Safe Attachments policies to quarantine messages when password-protected content cannot be scanned or detonated.
  • Organizations can pilot the feature using a separate scoped Safe Attachments policy.
  • Users can self-release eligible messages by providing the attachment password. A just-in-time detonation is performed before release.
  • Security administrators can release quarantined messages without requiring the attachment password.
  • Supported file categories include ZIP, GZIP, 7z, RAR, PDF, and Microsoft Office file formats.
  • Selected file categories can be excluded from protection.

Important

  • Users should only enter the attachment password.
  • Users should never enter account credentials, banking passwords, or unrelated passwords.
  • Users should only release expected messages from validated senders.
  • Unexpected protected email messages should be escalated to SecOps.

SecOps teams

EmailAttachmentInfo | where AdditionalFields contains "IsPasswordProtectedItem"

Action Required/Recommendations

No action is required unless you want to use this capability.

  • Review Safe Attachments policies.
  • Consider a pilot deployment.
  • Review quarantine release procedures.
  • Update internal documentation.
  • Communicate the change to support and helpdesk teams.
  • Educate users on appropriate use of attachment passwords during message release.
  • Review Microsoft Defender for Office 365 documentation.

Compliance considerations

The change modifies how password-protected email attachments may be processed and accessed when organizations enable the feature. Administrators gain new controls through Safe Attachments policies and can identify affected content using Advanced Hunting. No other compliance considerations were identified.

What changed

Between the versions this installation saw, newest first

This installation has seen one version of this notice, first on 19 Oct 2026. Later changes will show here.

Linked documentation

Microsoft pages the notice links to

This site links to Microsoft's pages instead of copying them. Installations inside an organization can keep a copy for comparison.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • Versions before 19 Oct 2026: this installation first saw the notice after Microsoft posted it.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Oct 13:25 UTC · 253 of 255 readable · 252 fully read · documentation 417/444 current