Email signature generator › Microsoft 365

Setting a signature for all users in Microsoft 365

Microsoft 365 does organisation-wide signatures through mail flow rules — the same mechanism used for compliance disclaimers. It works, and it behaves differently from what most people expect.

The path

1. Exchange admin center → Mail flow → Rules.
2. Add a rule, choose Apply disclaimers.
3. Set the condition — usually the sender is inside the organisation and the recipient is outside.
4. Enter the HTML, and choose the fallback action if the disclaimer cannot be applied.

Like Google Workspace, the HTML supports attribute placeholders that pull from each user's directory entry, so one rule produces a personalised block.

The fallback choice matters more than it looks

A disclaimer cannot be applied to an encrypted or signed message without breaking the signature or the encryption. The rule asks what to do in that case: wrap, ignore, or reject.

Wrap puts the original message inside a new envelope, which changes how it appears and can break threading. Reject bounces the message. Ignore sends it without the disclaimer. For most organisations Ignore is right — a missing footer on a handful of signed messages is a smaller problem than bounced mail — but if the footer is a regulatory requirement, that reasoning inverts and you should know which case you are in.

Replies stack

The rule applies to every outbound message, including every reply in a thread. Because the disclaimer is appended to the whole message, a five-message exchange with an external party accumulates five copies of the block, each one under the quoted history of the previous.

There is a common mitigation: add a condition that skips the rule when the subject already indicates a reply, or when the body already contains a marker string from the disclaimer. The second is more reliable, and it is why many organisations include an invisible marker in their footer HTML.

HTML limits

Keep the disclaimer to a table with inline styles, like any signature. There is no external CSS, and remember that the recipient may well be on Outlook for Windows, where the Word engine applies. Images must be hosted at a public URL; you cannot embed them in a mail flow rule.

Roaming signatures, separately

Distinct from mail flow rules, Microsoft 365 also has per-user signatures that roam with the mailbox rather than living on one machine. Those appear in the compose window, sit above the quoted text, and are the right place for personal contact details. The mail flow rule is for what the organisation requires.

The marker trick, in practice

The standard way to stop the disclaimer repeating on every reply is to include a string in the footer that nothing else would contain, and add an exception to the rule for messages whose body already includes it.

Use an HTML comment or a zero-width character rather than visible text, so readers never see the marker. Then set the rule's exception to "the subject or body includes" that string. From then on, the first message in a thread gets the disclaimer and subsequent replies do not, because the quoted history already carries it.

The limitation is that the marker travels in the quoted text, so it only works while the recipient's client quotes the previous message. A correspondent who trims quotes will start receiving the disclaimer again, which is harmless.

Testing a rule before it reaches everyone

Mail flow rules have a test mode that logs what the rule would have done without changing any message. Run the rule in test mode for a day and read the message trace: it will show which messages matched, which were skipped, and which hit the fallback because they were signed or encrypted.

That last number is the one to look at before choosing the fallback action. If your organisation signs a lot of mail, the fallback is not an edge case and the choice between Ignore and Wrap deserves a real decision rather than a default.

Order matters when there are several rules

Rules run in the priority order shown in the admin center, and a rule that stops processing prevents later ones from running. If a disclaimer rule sits below an encryption rule that halts processing, the disclaimer never applies and nothing reports an error — the rule simply does nothing, for a subset of mail, silently. Check the priority list whenever a rule appears not to work.

Frequently asked questions