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 signatur...
That’s a shame.
Last week Microsoft re activate roaming signature on our tenant and all our user have lost their signature.
When Microsoft want to release the powershell command that replace the old command and let us put the défaut signature of our users ?
it’s incredible to change a feature and activate it whitout a solution to do what it was previously possible.
We've been stuck with this problem for a few days now. We don't know if it's a Microsoft bug or if they intentionally removed the Postpone function. With PowerShell, you can get (GET) the PostponeRoamingSignaturesUntilLater option but you can no longer change (SET) it.