We're a 70-person manufacturing company, and our email signatures are all over the place. New hires often receive different versions, marketing updates a campaign banner every quarter but most employees never change theirs, and many mobile users still have "Sent from my iPhone" below the official signature. One salesperson even uses Comic Sans.
We currently use an Exchange transport rule to add signatures server-side. It helps with consistency, but mobile replies don't always behave properly, HTML can become messy in long reply chains, and the signature sometimes appears below the entire quoted conversation where nobody sees it.
What are other Microsoft 365 administrators doing in 2026? Are native transport rules good enough, or is a third-party platform such as CodeTwo, Exclaimer, WiseStamp, Xink, or Signature365 worth using?
5 Answers
A native transport rule can work if you only need a basic footer. Some organizations pull directory fields into an HTML template and apply different versions by department, which avoids paying for another service. The tradeoff is that native rules won’t fully solve signatures inside reply chains or user-added mobile signatures.
I’d separate the compliance footer from the branded signature. Keep the Exchange transport rule for a legal or regulatory disclaimer, since that works reliably as a server-side addition. Use CodeTwo, Exclaimer, or a similar product for the employee signature and campaign banner if you need it to appear properly while composing replies and on mobile devices.
The mobile and reply-chain problems are largely inherent to server-side stamping. Exchange receives the message as a finished blob, so it can’t reliably insert the signature at the cursor or distinguish an existing mobile signature.
The technology won’t solve everything by itself. Lock down user-created Outlook signatures where possible, publish a clear policy, and have HR or management support enforcement. Also test the mail flow of any third-party service carefully; signature relays can introduce delivery or reputation problems if their sending infrastructure is ever flagged.
We allow marketing limited access to update campaign banners, while all other changes require management approval. That has kept the system nearly hands-off.
We use WiseStamp and it’s been inexpensive and low-maintenance. Marketing controls the templates and handles new-hire setup, while IT doesn’t have to fix individual signatures. It also works across Outlook clients, including mobile, although you should test the exact apps your staff use.
We’ve used it for about a year without major issues, and having marketing own the content has made the process much easier for IT.
CodeTwo and Exclaimer are the most common solutions for this. They can centralize templates, pull user details from Microsoft 365 or directory data, handle new-hire setup, and let marketing manage banners without giving everyone permission to edit the signature. They’re generally much better than trying to maintain Outlook signatures manually.
CodeTwo has also been helpful for us because their support team assisted with the HTML design and troubleshooting.
Ideally Microsoft would provide a locked signature template with directory variables filled from Entra ID, but the native experience still has significant gaps.