Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Secure/Multipurpose Internet Mail Extensions encryption support in new Outlook for Windows

From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Roadmap
397891

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

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions we saw
  • Seen 23 Jan 2025 late February 2025

Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.

What the notice says

Microsoft’s text, safely structured

Updated January 21, 2025: After further review, we will not be rolling this out to DoD during the timeline outlined below. We will communicate via Message center when we are ready to proceed. Organizations in GCC High and DoD can safely disregard this message. Thank you for your patience.

We are rolling out fundamental Secure/Multipurpose Internet Mail Extensions (S/MIME) support for primary accounts in new Outlook. With this new feature, new Outlook will start supporting sending and reading signed and encrypted emails.

In new Microsoft Outlook, this option is available in Options > More Options.

This message is associated with Microsoft 365 Roadmap ID 397891.

When this will happen

General Availability (Worldwide): We began rolling out mid-December 2024 and expect to complete by late January 2025.

General Availability (GCC): We will begin rolling out early February 2025 and expect to complete by mid-February 2025.

General Availability (GCC High, DoD): We will communicate via Message center when we are ready to proceed.

How this will affect your organization

If your organization is not using New Outlook this will not impact you.

If your organization does not have S/MIME setup for your users, this will not impact you.

If your organization is currently using S/MIME, you will soon see controls to apply S/MIME encryption when signing into new Outlook. Similarly, you will be able to verify, sign, decrypt, and reply to S/MIME emails.

What you need to do to prepare

This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate.

Users with S/MIME certificates on their machine or Smart Card will be able to use this new feature in new Outlook.

Learn more: Overview of the new Outlook for Windows

What changed

Between archive captures, newest first
    • Tags New feature, User impact, Admin impact → Updated message, New feature, User impact, Admin impact

    Updated January 21, 2025: After further review, we will not be rolling this out to DoD during the timeline outlined below. We will communicate via Message center when we are ready to proceed. Organizations in GCC High and DoD can safely disregard this message. Thank you for your patience. We are rolling out fundamental Secure/Multipurpose Internet Mail Extensions (S/MIME) support for primary accounts … to complete by mid-February 2025. General Availability (GCC High, DoD): We will begin rolling out mid-February 2025 and expectcommunicate via Message center when we are ready to complete by late February 2025.proceed. How this will affect your organization: If your organization is not using …

  1. · first version seen

Learn more

Links from the notice and their documentation checks

No related announcements were found in the saved public history. Check the source for newer announcements.

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.
  • 1 linked page has not been read yet.
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 16 Nov 00:16 UTC · 274 of 275 readable · 251 fully read · 18 waiting for GitHub's hourly limit · documentation 469/469 current