Since Microsoft released “Roaming Signatures” it has been expected that there will come support for this in the Graph API, so that external applications, for instance IAM systems, can update signatures on behalf of all users in a company.
https://web.archive.org/web/20231208072313/https:/github.com/MicrosoftDocs/office-docs-powershell/issues/8537#:~:text=Greetings.%20A%20new,API%20is%20available regarding this.
https://feedbackportal.microsoft.com/feedback/idea/eba07341-ac9a-ee11-a81c-000d3a02ba69 from the feedback portal.
From the discussion where it says that the support for this is on the roadmap, however no one can say when it will be released.
We are in desperate need for this API-support as the application we use now for managing signatures has EOL later this year, and it does not support Exchange Online due to this lack of API-support. Our organization (approx. 8000+ users) will then loose the managed signatures. This is particularly bad since we are facing a transition to the New Outlook.
We hope sincerely that Microsoft will prioritize this and release support for Roaming Signatures within the Graph API very soon.
17 Comments
Hear, hear! Give us Graph API ability to set the HTML of our users' Roaming Signatures! It is crazy how long this hasn't been an option! Once you do release the API functionality, You better give us AMPLE time to adjust our signature deployment scripts before sunsetting old Outlook
Need facility in Graph for managing user mail signatures · Community (microsoft.com)
No progress nor information, Microsoft product group - Exchange - completely ignoring this feedback, request for information etc.This feature has been out since 2021, it's been more than enough time for this feature to be rolled out as a cmdlet or through the GraphAPI.
Please can we understand where Microsoft are with delivering Exchange Roaming Signature management tools/documentation? The New Outlook client does not support local signatures and is being installed on more and more machines as the days go by so the tools to properly administrate the Roaming Signatures have not been in any way optional or nice to have for some time now?
Please can we at least have a clue when the cmdlets and APIs for managing this are expected to be officially documented and made available to your customers, it's apparent that they are available to some developers for use in their proprietary tools for some time and we just need to publish the documentation so normal people can use it for themselves?
Please can you recognise and rapidly correct that you're railroading your customers onto a solution that you haven't released the basic tooling for large businesses to use yet? Can you please either fix the broken local signature functionality of the New Outlook client, have it respect the intended DisableRoamingSignatures registry keys, OR release the belated Exchange Roaming Signatures tools and documentation?
The https://learn.microsoft.com/en-us/powershell/module/exchange/set-organizationconfig?view=exchange-ps#-postponeroamingsignaturesuntillaterhttps://learn.microsoft.com/en-us/powershell/module/exchange/set-organizationconfig?view=exchange-ps#-postponeroamingsignaturesuntillater also refers to the upcoming API:
We're working on API support so admins and ISVs can configure roaming signatures directly.
It would be helpful with an ETA.
As an alternative to Graph API support, Microsoft could release an Exchange PowerShell command to set the roaming signatures.
