Forum Discussion
Outlook roaming signature vs Signatures on this device
A lot of our customers use a script to generate an email signature based on information in Active Directory. With the new "cloud signature", the scripted signature cannot be configured by default. It's moved under "Signatures on this device".
Is there a way to configure the signatures in "Signatures on this device" so that they are attached by default to the mail account ? For now, the only way I found is to manually copy the content of the signature into a new signature, which is attached to the email account.
15 Replies
Using Office 365, adding the registry to the register worked perfectly for me. Now the "on this device" is eliminated and my e-mails are now selectable and my signatures are able to be used by either e-mail. Thank you! Chrischevy
I've been able to set default signatures using registry keys as long as the signature is associated with the user's account. This produces the desired default sig you set, but the setting in the Outlook signature settings screen doesn't appear any different. If you check the signature files generated in AppData\Roaming\Microsoft\signatures the ones associated with the account are appended with the user's email in brackets. Just adding this to the signature file name seems to do the trick so that it then appears in the Outlook account signature list rather than the local device one.
To associate signature with account:
Change the signature file name in your script to "[SignatureName] ([User Principal Name]).htm" e.g. "Maddiebean's signature (email address removed for privacy reasons).htm" and it should appear in the user's email dropdown rather than 'Signatures on this device'. Worth noting the UPN is case sensitive in the filename too.
Recently converted to Office365 from Office Pro and all my old signatures were there and I was using them until I wanted to edit one, then only the signature named "signature" was in the list. WTF? read about the new "feature of roaming signatures now contained in the mail box" but no info on how to migrate them. Found this message thread and adding my email in brackets to the signature files worked to have them show up in the edit list. Not sure if its a time saver vs the cut and paste style of recreating them. Previously I had a symbolic link on my computers pointing to a signatures folder on onedrive as a means to have signatures available on all computers I used, but at least for Office 365 that is broke now.
"[SignatureName] ([User Principal Name]).htm"
The filename actually doesn't contain User Principal Name, I have different login than email, and in my case it contains email. BUT I saw user who's email also changed (only domain changed). In this case it contained not current email address, but the email address at the time when the Outlook was configured.
Microsoft, please change this to User Principal Name, so we could fetch this from AD to generate the signature.
For those of those that are using Microsoft Apps for business and not any form of Microsoft email, this is very problematic. We use Google Workspace sync to get our email into Outlook and rely on being able to edit and change our signatures on the device locally.
- I have the same issue.
Seems to be only with Office 365 users. O2019 and O2016 don't seem to be affected.- Response from Microsoft.
Outlook Web App the Roaming Signatures is already implemented, which disables the old EWS way. Outlook currently does not Support this Feature and it is on the Roadmap. Please refer the below roadmap link to track the progress. At the moment the feature is in a rolling out phase. Once the feature is launched for all the channels then you can use this feature.
https://www.microsoft.com/en-in/microsoft-365/roadmap?filters=&searchterms=60371
Also please refer the below link where the same issue is discussed.
https://learn.microsoft.com/en-us/answers/questions/890305/roaming-signatures-in-owa-already-done-and-ews-is.html- Has it now been implemented in the Outlook desktop app as well? Had a user report this morning that their signature had changed to an old obsolete version - which may well have been the one in the webmail / OWA as many of the users tend not to use this.
Roaming signatures is a good idea in theory, but if so it needs to adopt the most recent signature or give an option - not just automatically use whatever is configured in OWA without any option.
We have seen this behaviour aswell in the Click-to-Run version of Outlook.
This is due to the Roaming Signature feature that was introduced.
You can disable this by adding a registry key:
Hive: HKEY_CURRENT_USER
Key Path: Software\Microsoft\Office\16.0\Outlook\Setup\
Value Name: DisableRoamingSignaturesTemporaryToggle
Value Type: REG_DWORD
Value Data:1Example - manual and GPO deployment:
https://support.portal.exclaimer.com/hc/en-gb/articles/5300182785053
Great Post!
The registry entry is what restored the Signature editor for me.
Now i can see and edit all the signatures in my Outlook Desktop App, and no selection of email vs Signatures on this Device.
Changing the "Store my Outlook Settings in the cloud" checkbox made no difference for me.
The registry fix worked for me too.
Thanks Microsoft for an untested new feature.
We've seen this behaviour aswell with the Office365 Click-to-Run Outlook version due to the Roaming Signature feature that was introduced.
You can disable this within the registry of the current user.
Hive: HKEY_CURRENT_USER
Key Path: Software\Microsoft\Office\16.0\Outlook\Setup\
Value Name: DisableRoamingSignaturesTemporaryToggle
Value Type: REG_DWORD
Value Data:1Example - manual and GPO deployment:
https://support.portal.exclaimer.com/hc/en-gb/articles/5300182785053
- its working. Thanks a lot
