Forum Discussion
Solved
"Outlook for Windows: Signature cloud settings" - more detailed functionality description?
Hey Everyone, We can see from here, that new exciting feature is about to be rolled out: https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=&searchterms=signature Great timing as ...
Pawel Jarosz Well, for a feature still being in development stage as per the roadmap I think that Mr Redmonds article pretty much gives you an idea about it. As for supported versions there's always "first versions supported" with more to follow.
For the record it's not only signatures
https://support.office.com/en-us/article/outlook-roaming-options-f5ed5b9b-2df8-4c2d-aed3-d90bb14e5a59?ui=en-US&rs=en-US&ad=US
The roadmap
https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=&searchterms=63037
When this will happen
- We will begin rolling this out to Microsoft 365 Monthly Channel, Targeted, in late May. (This is Insiders Slow Channel which will soon be called Microsoft Beta.)
- We expect to roll this out to the Monthly Channel, Production, in late June.
GregTPACIf at least there was some reliable update on this.
I think the issue is that they moved some tenants over to the new roaming signature before they had any way of updating the new signature through a new API. So all the vendors that made api calls using the existing api to retrieve the cloud signature on these would just get back the old OWA signature that the user could no longer update and MS have no ETA on when an API will be available to do this, if the user has been migrated to the new cloud signature - you cannot update it with the old powershell commands. MS have well and truly messed this all up andwe are left with a mess of some users/tenants stuck on the old system and some on the new! But microsoft are too busy rewriting another outlook for mac and windows from scratch that no doubt will be as bad as the new Mac outlook which has no support for public folders, imap etc... I really hate the modern approach to software development, start a new one each time and release it without feature parity and force it upon every one and then call it exactly the same name so that you can't do a google search on issues related to the new version only.