Hey everyone, I'm having some trouble with a PowerShell script I've created that installs default email signatures for all our users in the classic Outlook client. While it sometimes syncs to the new Outlook, most of the time it doesn't, and I'm not really keen on relying on an unreliable sync process. I've turned off roaming signatures, and I've also used the Set-MailboxMessageConfiguration command to add HTML for the signature and enable AutoAddSignature as a test, but nothing appears when I create an email in OWA. The only settings I adjusted were AutoAddSignature, AutoAddSignatureOnReply, and SignatureHtml. I even tried changing the signature name, but that didn't help either. Has anyone else dealt with this issue? It seems odd that there wouldn't be better support for this feature, especially since Microsoft isn't integrating signatures into Graph yet. I have checked with Get-MailboxMessageConfiguration, and I can see that my changes are there. Any help would be greatly appreciated, thanks!
2 Answers
Honestly, I feel your pain! We tried managing signatures with PowerShell, but it turned into a headache. In the end, we just switched to CodeTwo, and I've got to say, it’s been a lifesaver. It’s surprisingly affordable and super reliable—never had a single issue in three years. Plus, it works regardless of the email client being used, since it handles everything server-side.
Right? "Screw Microsoft" for not properly supporting their own Cloud Roaming signatures with the API. It's frustrating to see features that are supposed to work so inconsistently.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures