Same Email Signature for All Staff in Microsoft 365: Admin Steps
To give every staff member the same email signature in Microsoft 365, an administrator creates an organisation-wide signature in Exchange admin center. It is built as a mail flow rule (Microsoft calls it an Apply disclaimers rule) that adds the HTML block to outgoing messages as they pass through Exchange Online. Employees cannot edit that rule. They can still keep personal signatures in Outlook, and those can clash with the company block, so the rollout needs a plan for them. The signature will not show in Sent Items, it cannot pull each person's name or job title automatically, and shared mailboxes and mobile apps need their own tests. If your company is a UK limited company, the registered details must appear on business email, and the law's section 82 of the Companies Act 2006 is the legal source. Use the free email signature generator on this page to draft the HTML before you paste it into the rule.
Work it out: Email Signature Generator. Free, no sign-up.
In short
- In Microsoft 365, a company-wide signature is an Exchange mail flow rule that staff cannot edit.
- Personal Outlook signatures can stack with the company block, so decide how to handle them before launch.
- Shared mailboxes and Outlook mobile apps need their own tests, using a separate rule and an Intune setting where needed.
- For a UK limited company, the registered details must appear in the email itself under section 82 of the Companies Act 2006.
- Test every rule on phones, in replies and on shared mailboxes before you switch it on for all staff.
The direct answer and the rule behind it
A single signature for the whole company is set in Exchange Online, not in each person's Outlook. Microsoft's own guidance describes this as an organisation-wide signature built with the Apply disclaimers action in the Exchange admin center. Staff cannot change it, because only an administrator with Exchange rights can edit the rule. That is the main control you gain. The trade-off is that the rule sends the same text to everyone, so names, job titles and phone numbers cannot be filled in per person.
On the legal side, the rule depends on where your company is registered. In the United Kingdom, section 82 of the Companies Act 2006 lets the Secretary of State require companies to state specified information on business documents, and the regulations made under it apply to email. The original trading disclosure regulations date from 2008, and they were later replaced by newer regulations, so check the current text on legislation.gov.uk before you copy wording from an old template. For a limited company, the place of registration, registered number and registered office address must appear in legible characters on business email. A link to those details in a footer is not enough. Sole traders and standard partnerships are not covered by this duty.
This guide uses the UK rule as its one worked legal example because it is the clearest public rule we could confirm. If you run a company in another country, look up that country's company registry or business law and treat this page as the technical setup only.
How the company signature is built, step by step
The work has three parts: decide the text, create the rule, then decide how it treats replies and exceptions. Most administrators spend their time on the second and third parts.
Write the signature in plain HTML. Keep it to a name block, company legal line and disclaimer. Avoid large images, because native mail flow rules do not support embedded images in the way many teams expect, and a company logo may not display as planned.
Sign in to the Exchange admin center through the Microsoft 365 admin center, open Mail flow, then Rules, and choose Add a rule and Apply disclaimers.
Under the conditions, choose to apply the rule to all messages, or to messages sent to recipients outside the organisation if you do not want internal mail to carry the block.
Paste the HTML into the disclaimer text box and choose whether it is appended at the end or prepended at the start of the message.
Choose a fallback action. Wrap sends the message as a new email with the original attached. Ignore sends the message without the disclaimer. Reject stops the message and returns a non-delivery report to the sender. Ignore is the usual choice for a signature, because a rejected email is worse than a missing footer.
Add an exception so the block is not repeated on long chains. Practical365 has described the common approach of excluding messages that already contain a snippet of the text.
Test with at least five internal and external accounts before you switch the rule on for everyone.
Worked example: a 300-person company with two shared mailboxes
Consider an illustrative company with 300 staff, a UK limited company registered in England and Wales, and two shared mailboxes called hello and accounts. The owner wants one signature for everyone, with the legal line on every outgoing email. The administrator creates one Apply disclaimers rule for all outbound mail to external recipients. The rule holds a short block with the company name, the registered number, the place of registration, the registered office address and a confidentiality notice.
The administrator sets the fallback to Ignore, and adds an exception so that replies do not stack a second block. Staff still type their own name and sign-off in the body of each email. The administrator then sends test messages from three accounts, two of which are shared mailboxes, and checks the result in Outlook on the web, classic Outlook on Windows and an Android phone. The table below shows what each setting does in this example.
| Setting | Value chosen in this example | Why |
|---|---|---|
| Scope | Outbound mail to recipients outside the organisation | Keeps the legal line on external mail and avoids clutter in internal chats |
| Position | Appended at the end | Standard for a footer, although replies will also carry it at the bottom of the thread |
| Fallback | Ignore | Keeps the email moving if the block cannot be added |
| Exception | Skip messages that already contain the block text | Limits stacked footers on long threads |
| Mobile | Default app signature set to off through Intune where managed | Stops the Outlook app's default text from appearing under the company block |
The example company does not need to track any percentage of time saved or any error rate. The point of the test is simple: the legal line appears, the footer does not repeat, and nobody's personal signature conflicts with it.
What each employee can still edit
Staff keep control of their own message body, greeting, sign-off and any text they type into a new email. They can also add personal signatures in Outlook, and Outlook on the web and desktop will let them choose one. That is where double signatures come from. The company block is added on the server, after the user has finished writing, so a person who has a personal signature will see two blocks in the sent message.
On mobile, the picture is different. Outlook for iOS and Android has a Default app signature setting. Microsoft's documentation says that when it is set to off, the default text is not used, but users can still add their own signature. The setting can be delivered through an Intune app configuration policy, and Microsoft describes two channels for it: managed devices and managed apps. Choose the channel that matches how your phones are enrolled, because the wrong one will not reach the right people.
Staff cannot see the company block in Sent Items. Practical365 notes that transport rules do not update the sent copy, so the message a person sees in their Sent folder can differ from what the recipient receives. Tell staff this in writing, so that nobody thinks the footer has been lost.
Cases that change the answer
Several situations need a different setup. The table below covers the common ones.
| Case | What changes | What to do |
|---|---|---|
| Shared mailbox such as hello or accounts | Outlook on the web can offer only one signature per shared mailbox, according to Microsoft community answers from 2024 | Create a separate Apply disclaimers rule with the condition that the sender is that shared mailbox |
| Reply or forward | The block goes to the bottom of the whole thread, not under the new text | Accept this in the first version, or use a third-party tool that inserts the block under each reply |
| Staff who use a personal signature | Two blocks can appear in one message | Remove personal signatures from the Outlook settings through policy, or agree a clear rule for them |
| Staff on Android with signature add-ins | A signature vendor reports that one Intune setting can block all signatures on Android | Test on a real Android device before you roll out the setting to the whole group |
| Staff who need different names or titles | Native rules send the same static text to everyone | Use a directory-based signature tool, or accept a generic block with names typed by staff |
| Sole traders and standard partnerships | The UK trading disclosure duty does not apply to them under the Companies Act 2006 | Check local business name rules with an adviser |
Each of these changes the answer to the question of who edits what. A shared mailbox needs its own rule, and a dynamic name or title needs a different tool. Do not assume the first rule will cover everything.
Testing on phones and in shared mailboxes
Testing is where most rollouts go wrong, so give it a fixed checklist. Use at least one account on each of these: Outlook on the web, new Outlook for Windows, classic Outlook for Windows, Outlook for iOS and Outlook for Android. Send a new message, a reply, a forward and a message to a Gmail account and to a company domain. Check the sent folder, the recipient's inbox and the footer text on a phone screen.
For shared mailboxes, send from the shared address itself, not from a staff account that is acting on its behalf. A common failure is that the staff member's personal signature appears instead of the mailbox signature. Microsoft community answers have described the same problem, and they suggest a transport rule that matches the shared mailbox as the sender. Test every shared mailbox separately, including any that were created last month.
Automation can run the send-and-check steps again whenever a rule changes, but it cannot judge whether a legal line reads correctly for your company. A person must still read the final wording and sign it off.
Common mistakes
- Pasting a signature with large images or a tracking pixel into the rule, then finding that the image does not show on phones.
- Switching on a rule for all mail before testing replies, which leads to long footers on every thread.
- Leaving personal signatures switched on, so every message has two blocks.
- Assuming a footer link to the company registration details is enough. For a UK limited company, the details must be written in the email itself.
- Forgetting shared mailboxes, which often keep their own personal sign-off from an earlier setup.
- Choosing Reject as the fallback, which can stop real customer mail from being delivered.
What to check with HR or a lawyer
Ask a lawyer to confirm the legal wording for your company, the place of registration and any regulated activity line that your sector requires. Ask HR to confirm which staff should appear with a name, job title or phone number, and whether any signature can be used by a person who has left. Ask IT to confirm who holds Exchange admin rights, because those people can change the company signature for everyone.
Where a signature change also touches roles or hours, for example a new job title for a team, the country's notice, consultation and severance rules apply, and the change should be agreed with the employee or checked with a lawyer. A signature change alone does not usually do that, but a change in someone's title on their contract can.
This explains the rule in general terms; it is not legal or tax advice for your case.
How employers take routine HR and payroll work off staff with AI workers
Many HR and payroll teams spend part of each week on the same routine tasks: copying new starter details into several systems, chasing missing timesheets, matching payroll exports to the accounts ledger and sending reminders for signed forms. AI workers can take over those repeat steps, pull the data from the source systems, prepare the record and flag the exceptions for a person. The person still approves pay runs, handles sensitive cases and decides on anything that changes an employee's terms. The same pattern applies to email signatures: the directory holds the facts, the automation keeps the template current, and a person checks the legal wording.
How AiStaffo would automate this
AiStaffo would start by reading the staff list from the Microsoft 365 directory, so that each name, job title and phone number comes from the record HR already keeps. An AI worker would then build the signature template and keep it in step when someone joins, moves team or leaves. It would also run a test send from each shared mailbox and each platform, and report the results for review. The owner or operations head still signs off the legal wording and decides which fields staff may show. To see how this would fit your own Microsoft 365 setup, book a free automation audit.
Questions people ask
Can I force one email signature on every staff member in Microsoft 365?
Why does the signature not appear in my Sent Items folder?
Does a company signature on Outlook mobile work?
How do I set one signature for a shared mailbox?
What must a UK company show on its business emails?
Can the signature include each person's name and job title automatically?
Book a free automation audit
Thirty minutes. We look at one process you run every week and tell you exactly what an AI worker would take off your desk, and what it would not.
