Why Deploy Signatures Centrally?
Relying on individual employees to set up their own email signatures leads to inconsistent branding, outdated information, and compliance gaps. As an IT administrator, deploying signatures centrally via Microsoft 365 ensures every outgoing email carries your organisation's approved branding, contact details, and legal disclaimers.
Transport Rules vs. Client-Side Signatures
Microsoft 365 offers two approaches to email signatures:
- Client-side (Outlook settings): Each user configures their own signature in Outlook. Gives users control but leads to inconsistency.
- Server-side (Transport rules): Signatures are applied at the mail server level via Exchange transport rules. Ensures consistency but has formatting limitations.
This guide covers the server-side approach using Exchange transport rules — the method that gives IT admins centralised control.
Step-by-Step: Deploy Signatures via Exchange Admin
- Sign in to Microsoft 365 Admin Centre — Go to admin.microsoft.com and sign in with your Global Administrator or Exchange Administrator credentials.
- Open Exchange Admin Centre — In the left sidebar, expand Admin centres and click Exchange to open the Exchange Admin Centre (EAC).
- Navigate to Mail Flow Rules — In the EAC, go to Mail flow → Rules in the left navigation.
- Create a New Rule — Click the + (Add) icon and select Apply disclaimers from the dropdown menu.
- Name Your Rule — Give the rule a descriptive name, e.g., "Company Email Signature — All Staff".
- Set Conditions — Under "Apply this rule if", select The sender is located → Inside the organisation. You can add further conditions to target specific departments or groups.
- Configure the Disclaimer — Under "Do the following", select Append the disclaimer. Click Enter text to open the HTML editor.
- Enter Your HTML Signature Template — Paste your HTML signature code, using dynamic variables to personalise per user (see variables section below).
- Set the Fallback Action — Choose what happens if the signature can't be appended (e.g., for encrypted emails). Select Wrap or Ignore.
- Save and Enable — Click Save. The rule will be active and applied to all matching outgoing emails.
Dynamic Variables
Microsoft 365 transport rules support Active Directory attributes as dynamic variables. Use these in your HTML template to personalise each user's signature automatically:
| Variable | Description |
|---|---|
| %%DisplayName%% | Full name |
| %%Title%% | Job title |
| %%Department%% | Department |
| %%PhoneNumber%% | Phone number |
| %%MobilePhone%% | Mobile number |
| %%Email%% | Email address |
| %%Street%% | Street address |
| %%City%% | City |
| %%Company%% | Company name |
These variables pull data from each user's Azure Active Directory profile. Make sure user profiles are up to date for accurate signature information.
Key Features of Centralised Deployment
🏢 Centralised Control
IT admins manage all signatures from one place. No more chasing employees to update their signatures when branding changes.
✅ Compliance
Ensure every email includes required legal disclaimers, ABN numbers, and regulatory notices — automatically and without fail.
🎨 Consistent Branding
Every email from your organisation carries the same professional, on-brand signature — regardless of which device or client the sender uses.
Limitations of Transport Rules
While transport rules are powerful, they do have limitations you should be aware of:
- No images in the disclaimer editor: The built-in HTML editor doesn't support image uploads. You must link to externally hosted images using absolute URLs.
- Users can't see the signature while composing: Since the signature is applied server-side, users won't see it in their compose window — only after the email is sent.
- Limited formatting: Complex HTML layouts may not render as expected. Keep the HTML simple with table-based designs and inline styles.
- One signature per rule: You'll need separate rules if different groups require different signature designs.
- Reply chain signatures: Transport rules append the signature to every outgoing message, including replies. This can result in multiple signatures stacking in long email threads.
Tips for IT Administrators
- Keep Azure AD profiles updated: Dynamic variables only work if user profiles contain accurate data. Audit your directory regularly.
- Test with a pilot group: Apply the rule to a small test group first before rolling out to the entire organisation.
- Use simple HTML: Avoid CSS grid, flexbox, or external stylesheets. Table-based layouts with inline styles work most reliably.
- Host images on a reliable CDN: Ensure your logo and banner images are hosted on a fast, always-available server.
- Consider third-party tools: For advanced formatting, user photo integration, or department-based signatures, third-party signature management tools offer much more flexibility than native transport rules.
- Document your rules: Keep a record of which transport rules are active, who they apply to, and when they were last updated.
🏗️ Need professionally designed signatures for your team? Create consistent, on-brand signatures that work perfectly with Microsoft 365. Create your signature →