Use of digital certificates in Outlook Client for Windows ("trust center")

[patrickcoom]

Hi,

I use Outlook (Office 365) to manage multiple accounts. I want to digitally sign all my outgoing emails from one account with a certificate.

How to set this up differs between my Outlook client for Mac and the one for Windows, and it is the Windows client that (according to me) has a design flaw.

On Mac the setting "S/MIME digitally sign all outgoing emails" is bound to an email account.

On Windows the setting "Trust Center, digitally sign all outgoing emails" is a global setting, so applies to all email accounts at once, there is no option to be selective and pick only one email account.

Hence, when I select this option, the Windows Outlook client now tries to digitally sign ALL my outgoing emails, including those for which the digital certificate is invalid.

Basically, using the Outlook for Windows client to manage multiple email accounts invalidates the setting to digitally sign all outgoing emails.

Does anyone have a workaround, or does anyone know how to propose this product improvement to the Microsoft Outlook for Windows client product team?

Thank you

Patrick

[#2]

@patrickcoom Hello, I just created an additional profile in my Outlook client and configured my primary profile to use my digital certificate (ID card) for signing messages via Trust Center settings in Outlook. When changing Outlook Profile to the new one (File - Account Settings - Change Profile) the settings are not "inherited". They are only configured in the profile in which I created them. In other words I cannot reproduce the issue you're describing as my outgoing messages are only digitally signed from my primary profile.

[#3]

@ChristianBergstromso you switch between profiles basically, which is not really great for using a single client for managing multiple mailboxes at the same time. What a terrible user experience. On Mac this works as one should expect, only on Windows this logic is at a wrong level. While digging deeper I found similar posts even bug reports dating back to 2015, but apparently nobody cares about using digital certificates.

Thx for your response!