check before: 2025-07-31
Product:
Entra, Exchange, Microsoft 365 Apps, Microsoft 365 for the web, Outlook, Windows
Platform:
Online, US Instances, Web, World tenant
Status:
Change type:
Admin impact, Feature update, Updated message, User impact
Links:
Details:
Summary:
New Microsoft Outlook for Windows desktop will support an admin setting to define S/MIME signature inheritance in replies, rolling out from late July to late August 2025. The setting, NoSignOnReply, can be configured to inherit or not inherit S/MIME signatures. This change does not apply to Outlook for Web. No admin action is required before rollout.
Details:
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.
Change Category:
XXXXXXX ... free basic plan only
Scope:
XXXXXXX ... free basic plan only
Release Phase:
Created:
2025-05-13
updated:
2025-07-23
Task Type
XXXXXXX ... free basic plan only
Docu to Check
XXXXXXX ... free basic plan only
MS How does it affect me
XXXXXXX ... free basic plan only
MS Preperations
XXXXXXX ... free basic plan only
MS Urgency
XXXXXXX ... free basic plan only
MS workload name
XXXXXXX ... free basic plan only
summary for non-techies**
XXXXXXX ... free basic plan only
Direct effects for Operations**
S/MIME Signature Inheritance
If the NoSignOnReply setting is not properly configured, users may inadvertently send replies without S/MIME signatures, leading to potential security risks and lack of email authenticity.
- roles: Email Administrators, End Users
- references: https://learn.microsoft.com/en-us/powershell/module/exchange/set-smimeconfig?view=exchange-ps
User Experience with Email Replies
Users may experience confusion or frustration if replies do not include expected S/MIME signatures, impacting communication clarity and trust.
- roles: End Users, Support Staff
- references: https://learn.microsoft.com/en-us/powershell/module/exchange/set-smimeconfig?view=exchange-ps
Configutation Options**
XXXXXXX ... paid membership only
explanation for non-techies**
XXXXXXX ... free basic plan only
** AI generated content. This information must be reviewed before use.
a free basic plan is required to see more details. Sign up here
A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.
change history
| Date | Property | old | new |
| 2025-07-23 | MC Last Updated | 07/21/2025 22:09:19 | 2025-07-22T15:47:36Z |
| 2025-07-23 | MC Messages | Updated June 21, 2025: We have updated the timeline below. 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. | 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. |
| 2025-07-23 | MC End Time | 08/29/2025 09:00:00 | 2025-10-06T09:00:00Z |
| 2025-07-22 | MC Messages | Updated June 17, 2025: We have updated the timeline below. 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 early July 2025 (previously mid-June) and expect to complete by mid-July 2025 (previously late June). General Availability (GCC): We will begin rolling out mid-July 2025 (previously late June) and expect to complete by early August 2025 (previously early July). 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. | Updated June 21, 2025: We have updated the timeline below. 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. |
| 2025-07-22 | MC Last Updated | 06/17/2025 21:11:21 | 2025-07-21T22:09:19Z |
| 2025-07-22 | MC Summary | New Microsoft Outlook for Windows desktop will support an admin setting to define S/MIME signature inheritance in replies, rolling out from early July to mid-July 2025. The setting, NoSignOnReply, can be configured to inherit or not inherit S/MIME signatures. This change does not apply to Outlook for Web. No admin action is required before rollout. | New Microsoft Outlook for Windows desktop will support an admin setting to define S/MIME signature inheritance in replies, rolling out from late July to late August 2025. The setting, NoSignOnReply, can be configured to inherit or not inherit S/MIME signatures. This change does not apply to Outlook for Web. No admin action is required before rollout. |
| 2025-06-18 | MC MessageTagNames | Feature update, User impact, Admin impact | Updated message, Feature update, User impact, Admin impact |
| 2025-06-18 | MC Summary | New Microsoft Outlook for Windows desktop and Outlook for the web will support an admin setting to define S/MIME signature inheritance in replies. Rollout begins in May 2025. Admins can use the `NoSignOnReply` setting to manage this feature via Microsoft Entra ID or Exchange Management Shell. No immediate action required. | New Microsoft Outlook for Windows desktop will support an admin setting to define S/MIME signature inheritance in replies, rolling out from early July to mid-July 2025. The setting, NoSignOnReply, can be configured to inherit or not inherit S/MIME signatures. This change does not apply to Outlook for Web. No admin action is required before rollout. |
| 2025-06-18 | MC Last Updated | 05/13/2025 01:37:58 | 2025-06-17T21:11:21Z |
| 2025-06-18 | MC Messages | New Microsoft Outlook for Windows desktop and Microsoft Outlook for the web 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 mid-May 2025 and expect to complete by late May 2025. General Availability (GCC): We will begin rolling out late May 2025 and expect to complete by early June 2025. 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): We will begin rolling out mid-June 2025 and expect to complete by late June 2025. | Updated June 17, 2025: We have updated the timeline below. 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 early July 2025 (previously mid-June) and expect to complete by mid-July 2025 (previously late June). General Availability (GCC): We will begin rolling out mid-July 2025 (previously late June) and expect to complete by early August 2025 (previously early July). 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. |
| 2025-06-18 | MC Title | New Microsoft Outlook and Outlook for the web: Admin setting for inheriting a S/MIME signature on reply | (Updated) New Microsoft Outlook and Outlook for the web: Admin setting for inheriting a S/MIME signature on reply |
| 2025-06-18 | MC How Affect | 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. This is the default state. 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 = $True. 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. The default behavior is consistent with classic Outlook. 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. | 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. |
Last updated 3 months ago ago
