Deploying email signatures in Outlook and Microsoft 365: transport rules or add-in?

Rolling out one consistent signature to every Outlook user is among the most common requests IT teams get on Microsoft 365. It is also one of the worst served by native tools. Here are the four possible approaches, and what each really involves.

Method 1: each user sets up their own signature

Each employee creates their signature:

• in classic Outlook for Windows: File → Options → Mail → Signatures;
• in new Outlook and Outlook on the web: Settings → Accounts → Signatures;
• in Outlook mobile: in the app settings, as plain text.

Microsoft introduced roaming signatures, stored in the mailbox rather than on the device, which reduces differences between devices. But the core problem remains: each person manages their own signature, with the usual errors, omissions and inconsistencies. See the hidden cost of manual signatures.

Method 2: mail flow rules (transport rules)

Exchange Online lets you create a rule that appends an HTML disclaimer to every outgoing message. The text can include directory variables (display name, title, phone…).

Pros:

• applied server-side, on every device;
• basic personalization through directory attributes;
• nothing to install.

Major limits:

• the signature is added at the end of the message, so below the whole history in a reply, not under the sender’s text;
• the sender doesn’t see it while composing, and it usually doesn’t appear in their Sent Items copy;
• the rule editor is poorly suited to building polished HTML;
• encrypted or digitally signed messages raise specific difficulties;
• managing scheduled, targeted banners quickly gets complicated (one rule per combination).

Transport rules are useful for a shared legal notice. For a real signature they hit their limits fast.

Method 3: the Outlook add-in

The modern approach recommended across the Microsoft ecosystem. An Outlook add-in uses event-based activation: as soon as a user opens a new message or a reply, the add-in inserts the signature automatically.

Pros:

• the signature is visible while composing, under the message, like a normal signature;
• it appears in Sent Items;
• the add-in is deployed once by an administrator from the Microsoft 365 admin center (Integrated apps), for the whole organization or specific groups;
• it works in Outlook on the web, new Outlook, classic Outlook for Windows and Outlook for Mac, and on mobile on supported versions;
• the signature is compiled server-side: a template change applies from the next message, with no user action.

Things to watch:

• check which Outlook versions are in your fleet: older perpetual-license versions don’t support event-based activation;
• plan to disable or remove old local signatures to avoid duplicates.

Method 4: an agent installed on each computer

Historically, some tools installed a small program on every computer to write the signature into Outlook. It covers neither the web, nor mobile, nor new Outlook, and requires device management. The add-in has largely superseded it.

Comparison

Criterion	Manual	Transport rule	Outlook add-in
Personalization	Manual	Basic (directory attributes)	Full
Visible while composing	Yes	No	Yes
Placed under the message	Yes	No (end of thread)	Yes
In Sent Items	Yes	Usually not	Yes
Targeted, scheduled banners	No	Hard	Yes
Deployment	Per user	One rule	Once, from the admin center

Deploying with a central tool

1. Connect Microsoft 365: the directory syncs through Microsoft Graph (users, groups, photos). See directory sync.
2. Design the template and assign it to the organization, teams or individuals.
3. Deploy the add-in from the Microsoft 365 admin center.
4. Clean up old local signatures.
5. Verify each employee’s status.

To run the project end to end, follow our rollout plan. And if part of the company runs Google Workspace, see the Gmail guide.