![New Microsoft Outlook and Outlook for the web: Admin setting for inheriting a S/MIME signature on reply [MC1072404]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-ekamelev-927500-1024x683.webp "New Microsoft Outlook and Outlook for the web: Admin setting for inheriting a S/MIME signature on reply [MC1072404] 1")
Message ID: MC1072404
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.
[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. 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.
[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
Source: Microsoft
![Power Platform admin center – Admins will soon be able to dismiss recommendations [MC1072367]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-noellegracephotos-906018-150x150.webp "Power Platform admin center – Admins will soon be able to dismiss recommendations [MC1072367] 6")
![Microsoft Viva Insights | Copilot Analytics: Unified experience for Copilot Dashboard and Insights analyst workbench [MC1072399]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-nuno-obey-34504-127160-150x150.webp "Microsoft Viva Insights | Copilot Analytics: Unified experience for Copilot Dashboard and Insights analyst workbench [MC1072399] 7")
The introduction of the new admin setting for S/MIME signatures in Microsoft Outlook and Outlook for the web is a noteworthy update that will have a significant impact on both administrators and users.
For admins, this change offers a valuable opportunity to enhance email security and streamline communication protocols within their organizations. With the ability to define whether S/MIME signatures are inherited in “Reply” and “Reply All” scenarios, admins can exercise greater control over email integrity. The flexibility to set the default state through the NoSignOnReply setting can help tailor the experience to the specific needs of an organization, ensuring that critical security measures are upheld without overwhelming users with unnecessary complexity.
On the user side, the impact is equally substantial. Users will benefit from a more consistent experience that aligns with their expectations when replying to emails. For those accustomed to the classic Outlook behavior, the default inheritance of S/MIME signatures will feel familiar and intuitive. However, the option to opt-out of signature inheritance when necessary adds an extra layer of customization that can be particularly useful in scenarios involving encrypted communications.
In terms of overall impact, this update appears to strike a balance between user experience and security, which is always a win in the world of email management. As organizations navigate this change, it will be interesting to see how they adapt their policies and user training to maximize the benefits of the new setting.
I encourage everyone to share their thoughts on this update! How do you think it will affect your workflow? Are there specific scenarios you foresee where this change could be particularly beneficial or challenging? Let’s get a conversation going! For more insights and updates, be sure to check out additional posts at mwpro.co.uk.