How Exclaimer client-side works with Outlook roaming signatures?

Scenario

You are using one of Exclaimer Cloud client-side to create signatures visible to Microsoft Outlook users. And, with the recent announcement from Microsoft that they are going to introduce a new feature (in CY 2020) in which the signatures in Outlook, for Windows, will be available across devices; this implies that instead of the signatures being stored locally, on the user's Windows device, they will now be stored in the user's mailbox. 

Now, you want to know how the Exclaimer client-side products will work with Microsoft's new feature  - Outlook roaming signatures?

Resolution

Exclaimer has been working with the Microsoft product team and is well-prepared for this change. We have released an update to our client-side agent that will automatically set the registry key to prevent Microsoft from updating the mailbox. 

You can either install the updated version of the client-side agent by the ClickOnce application or by the Group Policy Objects (GPO).   

By default, the registry key is set to 1 (to disable the roaming signatures); however, if the feature flag has already been set for you as a tenant, it will be set to 0 (to enable the roaming signatures).
If you install the Exclaimer Cloud Signature Update Agent for Windows, the registry key will be set to 1 (to disable the roaming signatures).

You can also manually disable this feature; for more information, see: How to disable the Microsoft Outlook Roaming Signatures feature.