How to roll out a branded email signature across an organisation
Roll out a branded email signature across an organisation by deploying it centrally instead of emailing staff a block of HTML to paste in. The reliable options are an Exchange transport rule that appends the signature at the server, a signature management platform that pulls names and titles from Entra ID, or a signature file deployed to each machine by script. Each one takes staff out of the process.
What are the deployment options, in order of control?
Five approaches exist, and the right one depends on the size of the organisation and how much the signature changes per person.
- Exchange transport rule. In the Exchange admin centre, Mail flow > Rules > Apply disclaimers appends HTML to every message leaving the organisation. It costs nothing and nobody can opt out. The trade-off is that staff cannot see the signature whilst composing, and it appends to every reply in a thread unless you add an exception.
- Signature management platform. A third-party service merges each person's name, title, phone number and office from Entra ID into a central template, syncs it into Outlook so staff see it as they type, and supports campaign banners. It carries a per-mailbox licence cost and is the standard choice above roughly 200 staff.
- Deployed signature file. Outlook reads .htm, .rtf and .txt files from %APPDATA%\Microsoft\Signatures. A login script can write those files and set the registry values under HKCU\Software\Microsoft\Office\16.0\Common\MailSettings to nominate the new-message and reply signatures. It costs nothing and needs IT to own it.
- Roaming signatures in Microsoft 365. Signatures are stored in the mailbox, so they follow the user into Outlook on the web and onto a new laptop. They interact awkwardly with script-deployed files, which is why a registry toggle to disable roaming exists.
- Staff building their own. This is how a 200-person organisation ends up with 200 variations, six logo versions and at least one signature still carrying an old office address.
Why does a signature that looks right in a browser break in Outlook?
Email HTML is a much older standard than web HTML, and Outlook on Windows renders messages using Microsoft Word's HTML engine. Modern layout techniques are ignored.
Build signatures with nested HTML tables and fixed pixel widths, because flexbox, grid and float are unreliable. Put all styling in inline style attributes on each element, since style blocks in the head are stripped by several clients. Host images on a public HTTPS URL with absolute paths, and avoid CSS background images entirely.
Web fonts do not load, so specify a web-safe stack such as Arial or Georgia with a generic fallback. Set every colour explicitly, including on text that looks black by default, because dark mode in Outlook mobile and Apple Mail inverts undeclared colours and can turn a navy logo panel into something unrecognisable. Keep the total width at or under 600 pixels.
Should the signature be an image?
No. An image-based signature fails the moment a recipient's client blocks images, which many do by default, leaving an empty rectangle where the sender's contact details should be.
Live text stays selectable, so a recipient can copy a phone number, and screen readers can announce it. Image-heavy signatures also push messages toward spam filters and add weight to every send. Keep images to the logo and any social icons, always with meaningful alt text and explicit width and height attributes so the layout holds whilst images load.
What changes on mobile and Outlook for Mac?
Outlook for iOS and Android supports a single plain text signature per account unless the signature is pushed through Intune policy or applied at the server. Anyone sending from a phone will send without the branded block, which argues for a transport rule as a safety net even when a platform handles the desktop.
Outlook for Mac stores signatures separately from the Windows client and can strip formatting that Windows renders correctly. Test any signature in Outlook for Windows, Outlook for Mac, Outlook on the web, Apple Mail and Gmail before rollout, and test each one in both light and dark mode.
How do you keep signatures current after launch?
Tie the variable fields to one source of truth. When name, title, phone number and office address are pulled from Entra ID attributes, updating a record in the directory updates the signature everywhere, and nobody has to remember to edit anything.
Lock the template so staff cannot edit it locally, review the fixed elements such as the office address and any promotional banner on a set cycle, and give one named person ownership. At Ideaseed we build Outlook templates for enterprise and government clients, and the version that survives is always the one with a person accountable for it.
An email signature rollout succeeds on its deployment method. Choose central deployment, build the HTML with tables and inline styles so it survives Outlook's rendering engine, keep contact details as live text, and tie the variable fields to your directory. Every message then leaves the organisation looking the same.
If your signatures have drifted into dozens of versions, get in touch and we will take a look at what you have.
Need a branded template? We can turn it around overnight.
Australia's Microsoft Office template specialists with a South Africa team that delivers while you sleep.
RAVE REVIEWS
who we work with
.svg)
.svg)
.svg)
.svg)
