All articles
Guides · 2 October 2026 · The Footer365 team

The Exchange Online mail flow rule signature, and its limits

The Exchange Online mail flow rule signature, and its limits

Can you add a signature to every user in Microsoft 365 without buying anything? Yes: an Exchange Online transport rule signature, which Microsoft calls a disclaimer rule, adds the same block of HTML to every message that matches it. It works, and for a small organisation with a plain text footer it may be all you need. The limits only show once it is live, so it is worth knowing them before you start.

How to add a signature to all users with a mail flow rule

Microsoft documents the whole procedure in Organization-wide message disclaimers, signatures, footers, or headers in Exchange Online. In short:

  1. In the Exchange admin center, go to Mail flow, then Rules, select Add a rule and choose Apply disclaimers.
  2. Under Apply this rule if, choose which messages get it. For outbound mail only, pick The recipient, is external/internal and Outside the organization. By default a mail flow rule applies to incoming mail as well as outgoing.
  3. Under Do the following, keep append a disclaimer and enter the text. It can be HTML with inline CSS, and it can use tokens such as %%DisplayName%%, %%Title%%, %%Phone%% and %%MobilePhone%%, which Exchange fills in from the sender's directory entry.
  4. Choose a fallback action for messages the rule cannot change, such as encrypted mail: Wrap, Ignore or Reject.
  5. Add an exception that looks for a phrase from your footer, so a reply does not collect a second copy, then test the rule before you set it to Enforce.

That is a working company-wide footer, and it costs nothing beyond the licences you already have.

Where it starts to pinch

A disclaimer rule was designed for legal text, and it shows when you ask it to be a signature.

It sits at the very bottom of the message

Append adds the text to the end of the message body. On a new email that is where a signature belongs. On a reply, the end of the body is below every earlier message quoted in it, so your footer ends up under the whole thread instead of under the few lines the person just wrote. The other choice, prepend, puts it at the very top, above the greeting. Neither is where a signature normally goes on a reply.

The same design for everyone in the rule

The tokens fill in each person's details, but the layout is one block of HTML. There is no way to say "leave this line out when it is empty", so when someone has no mobile number, the "Mobile:" label you wrote beside %%MobilePhone%% goes out with nothing after it. Different designs for different teams, brands or offices mean a separate rule each, and each rule is HTML typed into a box with no preview.

Nobody sees it while writing

The rule runs in Exchange Online transport, after the message has left the mailbox. The sender does not see it in the compose window, and the copy in their Sent Items does not have it, because that copy was saved before the rule ran.

Images and photos are up to you

Microsoft's own example adds a logo with an <img> tag pointing at a web address. That works, but the image is downloaded when the message is opened, so many recipients see an empty box until they allow pictures. There is no token for each person's photo.

Repeats depend on your exception

The exception that stops a reply from getting a second footer looks for text from the footer. Change the wording later and forget to change the exception, and threads start collecting copies.

When the native rule is enough

Use the mail flow rule when:

  • you need one short, text-only notice on every external email, such as a company registration line;
  • everyone can share the same layout; and
  • it does not matter where the footer sits on a reply.

Many organisations run exactly that for years, and there is nothing wrong with it.

What changes with a server-side signature service

Footer365 also works in Exchange Online transport, so like the native rule it signs mail from every device and every mail app, with nothing installed on anyone's computer. The difference is what happens to the message on the way through. Footer365's own transport rules route each outbound message through its relay, which writes the signature in and hands the message straight back to your tenant. Our article on how mail flows through Footer365 shows the path step by step.

Mail flow ruleFooter365
Position on a replyBottom of the whole message, or the very topAbove the quoted earlier message
Missing detailsThe value is left out, the label staysThe line is removed with its label
Different designsOne rule per design, typed as HTMLTemplates built in an editor, assigned by group, department, job title or domain
ImagesLinked from a web address you hostEmbedded in the message or hosted, chosen per image
Seeing it while writingNoOptional, with the Outlook add-in

Footer365 also decides whether a message is a new email, a reply or a forward, so a rule can give replies a short signature. If an older disclaimer rule is still switched on when you move across, it will keep adding its own footer below the new signature, so turn it off once the new one is live.

Where to go next

If the native rule does what you need, keep it: test it with a plain-text and an HTML message as Microsoft suggests, and forward a test to yourself to check the exception. If you have outgrown it, the Footer365 features page covers templates, rules and campaigns, and the 30-day trial needs no card.

Ready to see it on your own mail?

Start a 30-day trial - no card required.

Start free trial

Keep reading

Email signatures after a merger or tenant migration
Guides

Email signatures after a merger or tenant migration

Two companies, two brands and often two Microsoft 365 tenants. How to handle email signatures after a merger, from day one to the tenant move.

29 October 2026
Email signatures with Mimecast, Proofpoint or another gateway
Guides

Email signatures with Mimecast, Proofpoint or another gateway

Running Mimecast, Proofpoint or another email gateway? How a server-side email signature fits in the mail flow, what to check, and what never to change.

28 October 2026
What a charity's email footer needs to say
Guides

What a charity's email footer needs to say

Charity email footer requirements in England and Wales: when the Charities Act requires the registered status, and the company details charitable companies add.

27 October 2026
Why email signature images arrive as attachments
Guides

Why email signature images arrive as attachments

Logos turning up as image001.png, a paperclip on every email, or a blank box: why signature images misbehave, and how to choose the right fix for each.

26 October 2026