How to Set Up a Company-Wide Email Signature in Microsoft 365

On this page · 12 sections
  1. The five options at a glance
  2. Option 1: Ask everyone to set it by hand
  3. Option 2: Push it with PowerShell
  4. Option 3: An Exchange mail flow rule
  5. Option 4: An Outlook add-in, deployed to everyone
  6. Option 5: A signature management platform
  7. Shared mailboxes and send-as
  8. A variant for finance: adding a payment link
  9. Which option fits “set this up for all employees”?
  10. Before you switch it on: a pre-launch checklist
  11. Summary
  12. Frequently asked questions

TL;DR: There are five ways to give every employee the same signature in Microsoft 365. You can ask people to set it by hand, push it with PowerShell, add it on the mail server with a free Exchange mail flow rule, deploy an Outlook add-in, or buy a signature platform. This guide walks through each one step by step. It also covers shared mailboxes and send-as, and how to give one team, such as finance, its own variant.


Someone has asked you to “set up the email signature for everyone.” Maybe there is a new logo. Maybe legal wants a disclaimer on every outgoing email. Maybe someone noticed that half the company still uses a job title they had two roles ago.

The request sounds like a five-minute job. For the simplest version, it can be. This guide is about the set-up itself: what each option takes, what it does to shared mailboxes, and where it stops working.

The steps follow Microsoft’s own documentation, checked in October 2026. We have not yet run every one of them end to end in our own test tenant, so try each on a small pilot group first.

If you are still deciding what “central management” should mean for your organisation, start with Centralised Email Signature Management in Microsoft 365. This page assumes you have decided, and now need to switch it on.


The five options at a glance

OptionStaff see it while writingCovers phonesShared mailboxesCost
By hand in OutlookYesOnly where each person sets itEach person sets it for each mailboxFree
PowerShellYes, in Outlook on the webNoCan be set for the shared mailbox itselfFree
Mail flow ruleNoYes, every appFills in from the shared mailbox’s own detailsFree
Outlook add-inYesOutlook mobile only if the add-in supports itOnly if the add-in supports themSubscription, or build your own
Signature platformDepends on how it applies signaturesYes, if it routes mailVaries by vendorSubscription

Option 1: Ask everyone to set it by hand

The simplest option is to send everyone the approved signature and ask them to add it in Outlook. How to Add or Change an Email Signature in Outlook has the steps for each version of Outlook, so you can send staff that link rather than writing your own instructions.

It costs nothing, and staff see the signature while they write. It breaks down in four ways:

  • It drifts. Within weeks, people change the font, add a quote or never update the old version. Nothing enforces the design.
  • Every app needs its own copy. A signature set in classic Outlook on one PC does not always reach the Outlook mobile app or a native phone mail app. Each person has to set it in each place.
  • Changes mean asking again. A new logo or disclaimer means another email to everyone, and another round of chasing.
  • Starters miss it. Nobody tells the new hire, so their first emails go out without a signature.

This works for a handful of people. For anything larger, it is the problem the other options exist to solve.


Option 2: Push it with PowerShell

PowerShell can set a signature for many mailboxes at once, but it reaches less of Outlook than most admins expect.

What it can do

The Exchange Online cmdlet Set-MailboxMessageConfiguration sets the signature for a mailbox. Its main settings are:

  • -SignatureHtml: the signature for HTML emails
  • -SignatureText: the signature for plain text emails
  • -AutoAddSignature $true: add it to new emails automatically
  • -AutoAddSignatureOnReply $true: add it to replies too

Microsoft’s reference says these are Outlook on the web settings. They do not apply to classic Outlook, phones or other mail apps. Microsoft says some of the cmdlet’s settings also apply to new Outlook for Windows.

This sketch sets a name and job title for every user mailbox. It is written from Microsoft’s cmdlet reference, so try it on one mailbox before you run it for everyone:

Get-User -RecipientTypeDetails UserMailbox -ResultSize Unlimited | ForEach-Object {
  $html = "<p><strong>$($_.DisplayName)</strong><br>$($_.Title)</p>"
  Set-MailboxMessageConfiguration -Identity $_.UserPrincipalName -SignatureHtml $html -AutoAddSignature $true -AutoAddSignatureOnReply $true
}

What it cannot do

It stops working when roaming signatures are on. Roaming signatures are Microsoft’s newer way of storing Outlook signatures in the mailbox, so they follow people between computers. Microsoft’s reference says -SignatureHtml, -SignatureText and -AutoAddSignature do not work while roaming signatures are switched on. Admins can switch roaming off for now with Set-OrganizationConfig -PostponeRoamingSignaturesUntilLater $true. Microsoft describes that as a temporary switch, so do not build a long-term process on it.

It does not reach classic Outlook. Classic Outlook signatures are stored either in the mailbox (roaming) or as files on each PC. Writing those files means running a script on every computer. The free, open-source Set-OutlookSignatures project does this, and our review explains what it takes.

It is a one-off push. When someone’s job title changes, nothing updates their signature until you run the script again.

PowerShell is also how you script the next option. Microsoft’s New-TransportRule cmdlet creates the same mail flow rule as the steps below.


Option 3: An Exchange mail flow rule

The fastest way to apply a signature to every employee’s outgoing email, with no third-party software, is an Exchange mail flow rule, also called a transport rule. Microsoft calls it a “disclaimer” rule, even when you are adding a signature.

The rule runs on the mail server after the email leaves the sender’s mailbox. That is why it reaches every app and phone, and also why nobody sees the signature while they write.

Setting it up in the Exchange admin centre

  1. Sign in to the Exchange admin centre. From the Microsoft 365 admin centre, go to Show all, then Admin centres, then Exchange.
  2. In the left navigation, go to Mail flow, then Rules.
  3. Select + Add a rule, then Apply disclaimers.
  4. Give the rule a name. Under Apply this rule if, choose the scope. To cover everyone, select Apply to all messages. Many organisations narrow this, for example to messages from senders inside the organisation, so the signature only goes on mail your staff send.
  5. Under Do the following, confirm Apply a disclaimer to the message and append a disclaimer. Select Enter text and paste in your HTML.
  6. Choose a fallback action for messages the rule cannot change, for example encrypted ones. The default, Wrap, sends the original message as an attachment inside a new one, which can look strange. For a signature, as opposed to a legal notice that must always appear, Ignore is often the better choice. It delivers the original message unchanged.
  7. Add an exception so replies in a thread do not collect a new copy each time. Under Except if, choose The subject or body, then Subject or body matches these text patterns. Enter a short, unique piece of text from your signature, such as a phone number.
  8. Set Rule mode to Test without Policy Tips first, so you can check the result. Switch to Enforce when you are happy with it.

Microsoft’s reference page covers the same steps, and the New-TransportRule version for scripting.

Personalising it with tokens

A mail flow rule can fill in each sender’s details. Exchange supports tokens such as %%DisplayName%%, %%Title%%, %%Department%%, %%Phone%% and %%MobilePhone%%. At send time, it swaps each one for the value on the sender’s account in Entra ID, Microsoft’s cloud directory of staff accounts. Put %%DisplayName%% | %%Title%% in the HTML, and everyone’s signature shows their own name and job title.

There are two catches. If a field is empty for someone, Exchange does not leave a blank. It drops the whole line that contains the token. And there is no other conditional logic: a different layout for each team means a separate rule for each team.

Where it stops

A mail flow rule has firm limits. Staff do not see the signature while writing, and it does not appear in their Sent Items. In a reply, it goes below the whole quoted thread, not under the latest message. You cannot embed an image, only link to one hosted on a website. The complete guide covers what mail flow rules can and cannot do in more detail.

For a legal disclaimer, these limits rarely matter. For a branded signature with a logo, colours and a banner, they start to bite quickly.

Microsoft 365: Setting Up Email Flow Rules

Option 4: An Outlook add-in, deployed to everyone

An Outlook add-in puts the signature into the email inside Outlook, as the person starts writing. An admin deploys it to everyone, or to chosen groups, from the Microsoft 365 admin centre with Centralised Deployment. Nothing is installed on each device, and staff do not need to do anything. The complete guide walks through deploying an add-in with Centralised Deployment, including how long it takes and what permissions to check.

An add-in solves the two problems mail flow rules cannot: staff see their real signature while they write, with the logo and formatting in place. The trade-off is that it only works inside Outlook. It covers desktop and web, and the Outlook mobile app only if the add-in has been built with Microsoft’s mobile support. It never covers native phone mail apps such as iOS Mail. Why Your Email Signature Does Not Show Up on Mobile explains why.

You either build an add-in yourself or use a vendor that provides one.


Option 5: A signature management platform

Most organisations beyond a certain size end up here. Mail flow rules are not wrong, but the requirements grow. Different teams want different signatures. Marketing wants to change a banner without raising an IT ticket. Starters and leavers need handling through the directory.

Signature platforms do all of this for a per-user subscription. Some route mail through their own servers, some use an Outlook add-in, and many offer both. Signature Management for Microsoft 365: Server-Side vs Add-In compares the approaches in one table.


Shared mailboxes and send-as

Shared mailboxes, such as accounts@ or support@, catch out every option in a different way. Decide what a shared mailbox’s signature should say before you roll anything out. Usually it is the team’s name and contact details, sometimes with the sender’s own name as well.

By hand. Each person who sends from the shared mailbox has to set its signature. In classic Outlook, a shared mailbox added automatically is not a separate account. So Outlook does not switch signature when someone changes the From address, and people pick the right one by hand.

PowerShell. Set-MailboxMessageConfiguration works on the shared mailbox itself, just like a user mailbox. The roaming signatures limit above still applies, and so does the Outlook on the web limit.

Mail flow rules. Tokens fill in from the sender. When someone sends as the shared mailbox, the sender is the shared mailbox, so the signature shows its name and details, not the person’s. Fill in the shared mailbox’s own directory details, such as display name and phone number, so its signature reads properly. Or scope a separate rule to it with the The sender is condition. Test “send on behalf” as well as “send as”, because a send-on-behalf message names both the person and the mailbox.

Add-ins. An add-in only runs in a shared mailbox if its developer has built it to. Microsoft’s add-in platform also lets an add-in swap the signature when someone changes the From address. Microsoft supports this for shared mailboxes in Outlook on the web, Windows and Mac, but not on phones. Ask a vendor both questions directly.

Platforms. This varies by vendor. Ask how the platform handles send-as and send-on-behalf, and test both in your pilot.


Different teams often need slightly different signatures. A common one is a payment link for the accounts-receivable team, so customers can pay an invoice straight from an email.

You build it the same way as any other variant. Put the finance team in a group. Then either scope a separate mail flow rule to that group with The sender is a member of this group, or create a group-based rule in your add-in or platform. Give the rule a higher priority than the company-wide one, and add an exception so a sender never gets both.

A payment link in a signature also gives fraudsters something to copy. Criminals send lookalike emails with their own payment link or bank details. So, before you add one:

  • Tell customers how to check a link is genuine. Use one payment address that never changes, and print it on your invoices and website too. Customers can then compare the link with a copy they already trust.
  • Never change bank details by email. Say this on your invoices. If a customer gets an email saying your bank details have changed, they should call you on a number they already have.
  • Keep it to the finance team. A payment link in everyone’s signature is more for criminals to copy, and more for customers to check.

Consistent Email Signatures as a Phishing and BEC Defence explains how consistent signatures help staff and customers spot a fake, and where that help stops.


Which option fits “set this up for all employees”?

If the requirement is simple, such as a legal disclaimer or a basic name and title, a mail flow rule does it this afternoon, for free.

If staff need to see their signature while writing, or the design needs a logo and banner that render reliably, mail flow rules will not get you there. You are choosing between an add-in and a platform.

If different teams need different signatures, or marketing needs to own changes, a platform is usually the right choice. Rule-based assignment and a non-technical editor are the point of one.

If “all employees” includes people who send from phone mail apps or other non-Outlook apps, only server-side signing reaches them, through a mail flow rule or a platform that routes mail. Add-ins depend on Outlook being the app in use.

PowerShell and setting signatures by hand are fine for a small team, or as a stopgap. Neither keeps signatures consistent on its own.


Before you switch it on: a pre-launch checklist

Whichever option you choose, check these before the signature goes live for everyone:

  • Is the data in Entra ID accurate? Every gap or error in your directory will show up, or quietly disappear, in someone’s live signature.
  • Have you tested on a small group first? Use Test without Policy Tips mode for a rule, or deploy an add-in to a pilot group, before you switch it on for everyone.
  • Does an exception stop duplicate copies in reply threads? Without one, every reply in a long thread gets another copy of a rule-based signature.
  • What happens to encrypted or protected messages? Choose between Wrap, Ignore and Reject on purpose. The default is not always right for a signature.
  • Have you tested a shared mailbox? Send as one, and on behalf of one, and check what each signature says.
  • Does it render correctly in the apps staff use? Test Outlook desktop, Outlook on the web and Outlook mobile at least. Check classic and new Outlook for Windows if you still have both.

Summary

You can give every employee the same signature in Microsoft 365 for free, using an Exchange mail flow rule and its tokens. It is a useful start, with firm limits on design, placement and what staff see while writing. PowerShell and setting signatures by hand cost nothing, but they reach less of Outlook and drift over time.

The next step up is an Outlook add-in deployed with Centralised Deployment, which solves the visibility and design problems inside Outlook. Beyond that, signature platforms add team rules, directory sync and a non-technical editor, for a subscription.

Whichever you choose, test a shared mailbox and any team variant before you switch it on for everyone.


Frequently asked questions

Can I set up a different signature for different departments using mail flow rules?

Yes, but not within a single rule. Create a separate rule for each department, scoped with a condition such as The sender is a member of this group, each with its own text. Watch rule priority and exceptions. If someone could match more than one rule, make sure only the intended one applies, or they will get two signatures.

Why does an employee’s signature have a missing line?

Mail flow rules use tokens such as %%MobilePhone%% or %%Department%%, filled in from each person’s account at send time. If that field is empty in Entra ID, Exchange does not leave a blank line. It drops the whole line that contains the token. The fix is to fill in the missing directory field, not to change the signature.

Can I add my company logo to a mail flow rule signature?

Yes, by linking to an image hosted on your website, with an <img src="https://..."> tag. You cannot embed an image file in the rule itself. Host the image at an address that will not change. If it moves or is deleted, every employee’s signature will show a broken image.

Sources

  1. Exchange Admin Centre — Microsoft
  2. Microsoft Learn — Disclaimers, Signatures, Footers or Headers (Mail Flow Rules) — Microsoft Learn
  3. Microsoft Learn — Set-MailboxMessageConfiguration — Microsoft Learn
  4. Microsoft Learn — Automatically Update Your Signature When Switching Between Exchange Accounts — Microsoft Learn