Hello,
I'm having a problem with signatures on Outlook. I deploy the signatures via GPO, which works fine because when I open Outlook classic, the signatures appear. But when I migrate Outlook to Outlook new, the signatures disappear. I've tried setting the DisableRoamingSignaturesTemporaryToggle registry key to 1 in HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Setup
it doesn't solve the problem.
I've also noticed that when I create an outlook new signature and return to classic, the signature doesn't appear.
Here's the answer from someone in the Microsoft community
“First of all, regarding the registry change you mentioned, I think you must have come across articles about the Outlook Signature Roaming feature. However, the signature roaming feature is designed to support synchronization of signatures on different devices for the classic version of Outlook only.
Please note that there is no direct iterative relationship between Outlook (classic) and the new Outlook. Outlook (classic) is a C-based application, while the new Outlook is web-based. Its design focuses on providing Windows users with a free, lightweight e-mail client.
Signatures in the classic Outlook are stored locally, while signatures in the new Outlook are stored on the server. There is no direct communication or synchronization between the two. Therefore, I can only suggest that you create separate signatures for classic Outlook and new Outlook.
Thank you for taking the time to answer this question. Feel free to post if you need any further help. I wish you all the best.”
So what I also understand is that by GPO it's impossible to deploy signatures on the new version, right?
And is it possible to deploy a genetic signature on the outlook web in a company?
Thansk for your help
Frédérico