Forum Discussion
Office 365 - Message Encryption - and sign using S/MIME
S/MIME signing/encrypting is a client-based operation, you can only do it via Outlook or OWA. There is no transport rule action that corresponds to this. You can use OME instead, as you've already discovered.
Hi Vasil
Thanks for responding.But is it possible to add the certificate using OME then?
Decide whether you want Microsoft to manage the root key for Azure Information Protection (the default), or generate and manage this key yourself (known as bring your own key, or BYOK). If you want to generate and manage this key yourself, you need to complete some steps before you set up the new capabilities for OME. For more information, see Planning and implementing your Azure Information Protection tenant key. Microsoft recommends that you complete these steps before you set up OME.
I'm not entirely sure what you mean by that. OME does not need any certificate, it generates all the needed cryptographic components on the backend. The process is explained here: https://docs.microsoft.com/en-us/azure/information-protection/understand-explore/how-does-it-work
Well..
We have bought a certificate to sign all outgoing mails with a company signing (Company certificate). I want to add this certificate AND use the OME encryption features.
So when sending an email, its encrypted from OME AND signed using the certificate (Even though it should be added local from Outlook.)
If I add S/MIME certificate from Outlook, the encryption from OME is removed???
