Email Signature Microsoft 365: Admin Setup Guide (2026)

TL;DR: Individual users can set up their own Microsoft 365 email signature in Outlook in under two minutes. Getting a consistent signature across your whole org — where every employee uses the right logo, disclaimer, and contact info — requires Exchange transport rules or PowerShell, both of which have real limitations. This guide covers both paths clearly.

What Is a Microsoft 365 Email Signature?

A Microsoft 365 email signature is the contact block automatically appended to emails sent from any Microsoft 365 account — Outlook on Windows, Mac, web, or mobile. It typically contains your name, title, phone number, company logo, and any legal disclaimers your organization requires.

Microsoft 365 email signature: A reusable block of text, images, and links added to the bottom of outgoing emails in Microsoft 365. Individual users configure client-side signatures in Outlook; IT admins deploy org-wide signatures through Exchange Online transport rules or PowerShell scripts.

Microsoft 365 supports two distinct types of signatures:

• Client-side signatures — set by individual users in their own Outlook settings, only applied when composing on that specific client
• Server-side signatures — injected by Exchange Online transport rules after the email is sent, applied consistently regardless of which client the user sends from

Understanding which type you need depends on your goals. For personal signatures, client-side works fine. For brand consistency across a team of 20+ people, you want server-side — but it comes with trade-offs worth knowing upfront.

How to Set Up Your Own Signature in Microsoft 365 (Individual Users)

Outlook for Windows

1. Open Outlook and go to File > Options > Mail
2. Click Signatures...
3. Click New, name the signature, and click OK
4. In the editing area, type your name, title, phone, and website
5. To add a logo, use the image icon in the toolbar — paste or insert from file
6. Under Choose default signature, select when this applies (new messages, replies)
7. Click OK

One thing to know: Outlook's built-in editor produces messy HTML if you copy-paste from Word or Google Docs. For anything beyond plain text, paste clean HTML directly. If you're using a tool like Signkit, you can generate the HTML and paste it in via Format > Switch to HTML mode.

Outlook on the Web (OWA)

1. Click the Settings gear (top right) and search "email signature"
2. Click Email signature in the results
3. Create your signature in the rich text editor or switch to HTML mode
4. Toggle Automatically include my signature on new messages if desired
5. Click Save

Outlook on Mac

1. Open Outlook and go to Outlook > Preferences > Signatures
2. Click the + button to add a new signature
3. Name it, edit the content, drag it to your email account

Microsoft 365 Mobile (iOS/Android)

Mobile signatures are set separately in the Outlook app:

1. Tap your profile photo > Settings
2. Tap your email account
3. Tap Signature
4. Edit and save

Note: mobile signatures are plain text only — no images, no HTML. This is a hard limitation of the Outlook mobile app.

How to Deploy Signatures for Your Entire Organization (IT Admin)

This is where things get more involved. Microsoft 365 doesn't have a single "deploy a signature to everyone" button. You have two main options: Exchange transport rules (the UI approach) and PowerShell (the scripting approach).

Option 1: Exchange Transport Rules (Recommended Starting Point)

Transport rules in Exchange Online let you automatically append a disclaimer or signature to every outgoing email that matches conditions you define.

1. Go to the Microsoft 365 admin center at admin.microsoft.com
2. Navigate to Exchange > Mail flow > Rules
3. Click + Add a rule and choose Apply disclaimers
4. Name the rule (e.g., "Company Email Signature — All Staff")
5. Under Apply this rule if, set the condition — typically The sender is a member of > select your All Staff distribution group
6. Under Do the following, choose Append the disclaimer and click Enter text...
7. Paste your HTML signature template
8. For Fallback action, choose Wrap (appends the HTML as an attachment if it can't be injected)
9. Set the rule enforcement to Enforce (not just audit)
10. Click Save

What works well: transport rules apply regardless of which Outlook client employees use. The signature lands consistently.

What doesn't work: the appended signature doesn't appear in the user's Sent Items — they send the email, it leaves without a signature visible to them, then Exchange injects it after the fact. Users often think it's broken. Also, you can't use per-user variables easily (like each person's own phone number or job title) without advanced setup.

According to Microsoft's Exchange documentation, transport rules are evaluated after the message leaves the sender's mailbox, which is why signatures don't appear in Sent Items.

Option 2: PowerShell for Granular Control

For organizations that want per-user dynamic signatures (each employee's name, title, and phone number auto-populated), PowerShell is the practical path — but it requires scripting.

Basic PowerShell approach:

# Connect to Exchange Online
Connect-ExchangeOnline -UserPrincipalName admin@yourcompany.com

# Create a transport rule with HTML signature
New-TransportRule -Name "Company Signature" `
  -SentToScope NotInOrganization `
  -ApplyHtmlDisclaimerLocation Append `
  -ApplyHtmlDisclaimerText '<table><tr><td>%%DisplayName%%<br>%%Title%%<br>%%PhoneNumber%%</td></tr></table>' `
  -ApplyHtmlDisclaimerFallbackAction Wrap

The %%DisplayName%%, %%Title%%, and %%PhoneNumber%% placeholders pull from each user's Active Directory (or Azure AD) profile. This is how you get personalized signatures — but it requires that AD data is clean and accurate, which is often the actual challenge.

Reality check: If your org has 50+ employees with inconsistent job titles, missing phone numbers, or different naming conventions across departments, the AD-based approach can make things messier before it makes them cleaner.

The Limitations You'll Hit (and What to Do About Them)

Microsoft's built-in tools get you part of the way there. Here's where most IT admins run into friction:

1. Signatures don't show in Sent Items Because transport rules run server-side after sending, users never see the appended signature in their own sent folder. This is a known limitation with no workaround in Exchange Online — it's how the system is designed.

2. Images are unreliable Inline images in HTML signatures are treated as attachments by many email clients. The standard approach is hosting the image on a public URL and referencing it in the HTML — but if the hosting goes down or the URL changes, your logo disappears from every outgoing email.

3. Mobile doesn't pick up server-side signatures Mobile clients (iOS and Android) may display the signature appended by the transport rule, but users don't see it while composing. What they type is what they see — the server injects the signature invisibly. For users who care about previewing their signature before sending, this is frustrating.

4. Centralized updates require touching every rule If your logo changes, or your company rebrands, you have to update every transport rule manually. For a small company, that's manageable. For a growing org, it becomes a maintenance headache.

5. No approval workflow Anyone with access to the Exchange admin center can modify signatures. There's no draft-review-approve cycle built in.

For organizations where these limitations matter, purpose-built signature management tools handle the full lifecycle: design templates, per-user personalization from AD/HR data, logo hosting, and one-click updates across all employees. Signkit is built for exactly this — see how centralized signature management works.

Best Practices for Microsoft 365 Email Signatures

Keep the HTML clean. Exchange Online strips some HTML tags. Avoid <div> layouts, CSS classes, and media queries. Use <table> structures with inline styles. This is also what email clients like Gmail and Apple Mail expect.

Host images externally. Link to images hosted on a reliable CDN, not as inline base64 or attached files. If you're using Signkit, R2 hosting is handled automatically.

Populate Azure AD first. If you're using PowerShell with %% variables, audit your Azure AD user data first. Every field that's blank or inconsistent will show up in the appended signature.

Test across clients. A signature that looks perfect in Outlook for Windows may render poorly in Gmail or Apple Mail. Test with Litmus or send test emails to a cross-client test address before rolling out org-wide.

Add a legal disclaimer if required. Some industries (financial services, healthcare, legal) require specific disclaimers on every outgoing email. Add these to your transport rule alongside the signature — they're both appended at the server level.

For a full breakdown of what a professional signature should include, see our guide on what to include in an email signature.

Microsoft 365 vs Office 365: What's the Difference for Signatures?

Microsoft rebranded Office 365 to Microsoft 365 in 2022. For email signatures, the difference is mostly naming — the underlying infrastructure (Exchange Online, Outlook clients, transport rules) is the same. If you have instructions referencing "Office 365" admin center steps, they still apply. Our Office 365 email signature admin guide covers the steps in detail if you're following older documentation.

Frequently Asked Questions

How do I add an email signature in Microsoft 365 for all users?

Go to the Exchange admin center > Mail flow > Rules and create a new transport rule that appends HTML to all outgoing messages. You can scope the rule to a specific group or apply it to your entire organization. The signature is injected server-side after the email is sent, so it applies regardless of which Outlook client employees use. The downside is that users won't see the appended signature in their Sent Items.

Can I use images in a Microsoft 365 email signature?

Yes, but inline images are tricky. The reliable method is hosting your logo or banner on a public URL (like a CDN) and referencing it with an <img src="https://..."> tag in your HTML signature. Avoid embedding images as base64 or attaching them as files — most email clients treat these as attachments or strip them entirely.

Why doesn't my Microsoft 365 signature show in Sent Items?

Transport rule signatures are appended after the email leaves the sender's mailbox — they're added server-side during delivery. This is a design limitation of Exchange Online. The recipient sees the signature correctly, but the sender's Sent Items copy does not. There's no native fix; some organizations address this by having users set a client-side signature in Outlook that visually matches the server-side one.

How do I update the email signature for all employees at once?

In Exchange Online, edit the transport rule and update the HTML. All subsequent emails will use the new version immediately — no changes needed on individual user devices. If you need to update hundreds of employees across multiple rules, a signature management platform like Signkit lets you push updates centrally with one change that propagates instantly.

What variables can I use to personalize Microsoft 365 signatures?

Exchange Online transport rules support Active Directory attribute placeholders: %%DisplayName%%, %%Title%%, %%PhoneNumber%%, %%Department%%, %%StreetAddress%%, %%City%%, %%StateOrProvince%%, %%CountryOrRegion%%, %%Email%%, and a few others. These pull the values from each user's Azure AD profile at send time, so the signature is personalized per sender. Data accuracy in Azure AD is the bottleneck.

Key Takeaways

• Individual users set up Microsoft 365 email signatures in Outlook settings — it takes under two minutes and varies slightly by client (Windows, Mac, web, mobile).
• IT admins deploy org-wide signatures through Exchange Online transport rules or PowerShell — signatures are injected server-side and apply to all clients, but don't appear in users' Sent Items.
• Use %% Active Directory placeholders in transport rules to personalize signatures per employee — but audit your Azure AD data first, because missing or inconsistent fields will show up in every outgoing email.
• Inline images in signatures should be hosted on a public CDN and referenced by URL — embedding them as base64 or attachments breaks rendering in most email clients.
• For teams that need centralized control, approval workflows, and one-click updates, purpose-built signature management tools handle the complexity that Exchange Online's native tools don't cover.

---

Managing email signatures across a growing team is one of those problems that looks simple until it isn't. The Exchange transport rule approach works — but it has rough edges that become real problems at scale.

If you're hitting those edges, Signkit's free plan lets you start with one signature and see how centralized management compares. No credit card required.