Does anyone remember the call for support for a proposal by Jeff Guillet regarding centrally managed Outlook signatures? I had reported on Jeff's proposal in March 2018 and asked for Support for the proposal asked. A total of 8,754 votes were cast in favor of the proposal and in September 2019, the response was that the proposal would be implemented.
Now the time has finally come and Jeff's proposal has been given a name "Outlook roaming signatures". Microsoft 365 users and Outlook.com users will be the first to see the new feature. Outlook signatures can be saved as part of the mailbox using "Outlook roaming signatures" and are therefore in principle available on any device or client. Currently, Outlook signatures are stored locally, only OWA signatures are stored centrally on the Exchange servers.
Here is an article on how Jeff's suggestion was implemented:
The feature is currently in the test phase for Microsoft 365 and Outlook.com users. It is currently impossible to say whether and when Outlook roaming signatures will be available for Exchange on-prem. Hopefully the function will be added for Exchange on-prem via CU and will be significantly expanded. I have not yet tested the new feature, but I hope that a design and content can at least be specified in a similar way to the OWA signatures.
At the moment, however, it doesn't look as if special software for managing signatures will be retired any time soon:
If Outlook roaming signatures are consistently developed further and not just limited to "Outlook for Windows" and, ideally, can be managed centrally, the new feature is sure to be a success. It remains to be seen how this topic will develop in the future, but at least a big step in the right direction has been taken, also thanks to the many supporters. Now we have to fight for further development: Management of signatures via PowerShell, use of AD attributes and the use of other clients which access the mailbox via ActiveSync.