We use CodeTwo with on-premises Exchange SE, but signatures currently appear only after sending. A manager wants everyone to maintain their own Outlook signature so they can see it while writing. Is there a way to keep central management and make the signature visible in the compose window?
Can we keep centrally managed Outlook signatures visible while composing?
Asked by
p6~notch.rough
Answers
Check the CodeTwo Outlook add-in. It can provide client-side signatures while a message is being composed, so you may not need to abandon central management. First confirm that the add-in and your current product version support your on-premises Exchange SE setup and the Outlook clients you use.
Test it with the manager and a small group before changing the organization-wide setup. Also check how it interacts with your existing server-side rules so messages don't end up with two signatures.
Reply to this answer
I'd frame this as two separate requirements: people want to see their signature, and the organization wants consistent details and branding. A centrally managed client-side signature could satisfy both. Manual templates put the update work on every employee and can drift when contact details or branding change.
Reply to this answer
Don't overlook the users who don't have access to Outlook. An Outlook add-in may solve the compose-window issue for some people but not every sending workflow. List the clients and ways people send mail, then check what happens in each before replacing the server-side setup.
Reply to this answer
Exclaimer also has an Outlook add-in, but a switch isn't necessarily the right answer here. Since data residency is a requirement, verify where any proposed service processes and stores data before considering it. The existing CodeTwo option is worth investigating first.
Reply to this answer
Add your answer
Answers are reviewed before publication.
p6~notch.rough:
That's the kind of compromise I'm looking for. I'll check the add-in and compatibility with our setup.