ChangeIntelIT change radar
Public mode

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

Some sources, documents or advisories need attention: 271/272 feeds/APIs · 469/469 docs · 7/9 advisories · checked 23:56 UTC Customize Public modeDiscuss ChangeIntel on Discord
MC1072404 Stay informedUpdated messageFeature updateUser impactAdmin impact

New Microsoft Outlook and Outlook for the web: Admin setting for inheriting a S/MIME signature on reply

Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.
Exchange OnlineMicrosoft 365 for the webMicrosoft 365 apps
Microsoft 365 admin center

Rollout

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 this installation saw
  • Seen 21 Jul 2025 early July 2025, mid-July 2025 → late August 2025
  • Seen 17 Jun 2025 mid-May 2025, late May 2025, early June 2025, mid-June 2025, late June 2025 → early July 2025, mid-July 2025, early August 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, with source markup removed
Updated July 22, 2025: We have updated the timeline. Thank you for your patience. New Microsoft Outlook for Windows desktop will soon support an admin setting to define the application of S/MIME signatures in "reply to" scenarios. This setting enables admins to define if an S/MIME signature will be inherited by default in Reply and Reply all scenarios. When this will happen: For new Outlook for Windows desktop: General Availability (Worldwide): we will begin rolling out late July (previously early July) and expect to complete by early August 2025 (previously mid-July). General Availability (GCC): We will begin rolling out early August 2025 (previously mid-July) and expect to complete by late August 2025 (previously early August). For Outlook for Web: After further review we have decided not to proceed with this change at this time for Outlook for Web. We apologize for any inconvenience. How this will affect your organization: After this rollout, you can use the new setting called NoSignOnReply to define Signing on Reply and Reply all. Using this setting, admins can define inheritance of S/MIME signature for its users. The NoSignOnReply setting is available in Microsoft Entra ID (formerly Active Directory). NoSignOnReply = $False. When value = False, Reply and Reply all will inherit the S/MIME signature. Users will need to go to S/MIME settings and remove S/MIME signature. NoSignOnReply = $TrueThis is the default state. Reply and Reply all will not inherit S/MIME signature. In cases where incoming email has S/MIME encryption and a signature attached, this setting will only inherit encryption and not the signature. This setting can be useful in scenarios where your organization has not configured S/MIME signatures for its users. As an alternative, admins can configure this setting with the cmdlet Set-SmimeConfig (Set-SmimeConfig (ExchangePowerShell) | Microsoft Learn. Admins can configure this setting in the Microsoft Exchange Management Shell or the Microsoft Exchange Online Shell. What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your users or admins about this change and update any relevant documentation. If your organization does not use S/MIME emails, you do not need to take any action. If your organization has enabled communications with S/MIME, you may need to review this setting based on your preferences for the behavior. Learn more about this new setting and other S/MIME settings available for admins to define: Set-SmimeConfig (ExchangePowerShell) | Microsoft Learn #newoutlookforwindows

What changed

Between archive captures, newest first

  1. Updated June 21,July 22, 2025: We have updated the timeline below.timeline. Thank you for your patience. New Microsoft Outlook for Windows desktop will …

  2. Updated June 17,21, 2025: We have updated the timeline below. Thank you for your patience. … Outlook for Windows desktop: General Availability (Worldwide): we will begin rolling out earlylate July 2025 (previously mid-June)(previously early July) and expect to complete by mid-Julyearly August 2025 (previously late June). mid-July). General Availability (GCC): We will begin rolling out mid-Julyearly August 2025 (previously late June) mid-July) and expect to complete by earlylate August 2025 (previously  early July).August). For Outlook for Web: After further review we have decided not to …

    • Tags Feature update, User impact, Admin impact → Updated message, Feature update, User impact, Admin impact

    New Microsoft OutlookUpdated June 17, 2025: We have updated the timeline below. Thank you for Windows desktop andyour patience. New Microsoft Outlook for the webWindows desktop will soon support an admin setting to define the application of S/MIME … Outlook for Windows desktop: General Availability (Worldwide): we will begin rolling out mid-Mayearly July 2025 (previously mid-June) and expect to complete by mid-July 2025 (previously late May 2025. June). General Availability (GCC): We will begin rolling out mid-July 2025 (previously late May 2025 June) and expect to complete by early June 2025.August 2025 (previously  early July). For Outlook for the web: General Availability (Worldwide): We will begin rolling out early June 2025 and expect to complete by mid-June 2025. General Availability (GCC): Web: After further review we have decided not to proceed with this change at this time for Outlook for Web. We will begin rolling out mid-June 2025 and expect to complete by late June 2025. apologize for any inconvenience. How this will affect your organization: After this rollout, you can use … is available in Microsoft Entra ID (formerly Active Directory). NoSignOnReply = $False. This is the default state. When value = False, Reply and Reply all will inherit the S/MIME … need to go to S/MIME settings and remove S/MIME signature. NoSignOnReply = $True.$TrueThis is the default state. Reply and Reply all will not inherit S/MIME signature. In cases where … scenarios where your organization has not configured S/MIME signatures for its users. The default behavior is consistent with classic Outlook. As an alternative, admins can configure this setting with the cmdlet Set-SmimeConfig …

  4. · first version seen

Linked documentation

Microsoft pages the notice links to

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

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 26 Oct 23:56 UTC · 271 of 272 readable · 269 fully read · documentation 469/469 current

No accounts or analytics; your preferences stay in your browser. Information, not advice. ChangeIntel is an independent tool and is not affiliated with or endorsed by Microsoft, Apple, Google, Broadcom (VMware), Jamf, Oracle, Mozilla, or any other vendor it covers. Product names are trademarks of their owners. Built by Evotec.