Email Signatures for Your Entire Team in Microsoft 365

If your company runs on Microsoft 365, you've probably wondered: "Is there an easy way to set up email signatures for everyone on my team?"

The short answer is yes — but Microsoft doesn't make it straightforward. There's no simple "company signature" button in the admin centre. Instead, you have several options, each with trade-offs.

In this guide, we'll walk through every approach and help you pick the right one for your SA business.

Option 1: Exchange Transport Rules (Mail Flow Rules)

This is Microsoft's built-in solution. Transport rules let you append an HTML signature to every outgoing email at the server level.

How to set it up

1. Log in to the Microsoft 365 admin centre
2. Go to Admin centres → Exchange
3. Navigate to Mail flow → Rules
4. Click + Add a rule → Apply disclaimers
5. Paste your HTML signature template
6. Use dynamic variables to personalise:
   • %%DisplayName%% — Employee's full name
   • %%Title%% — Job title
   • %%Department%% — Department name
   • %%PhoneNumber%% — Office phone
   • %%MobilePhone%% — Mobile number

The limitations

While transport rules sound ideal, they come with significant drawbacks:

Users can't see the signature while composing. The signature is added after the email is sent, which means employees can't preview how their email will look. This is confusing and leads to support tickets.

HTML rendering is unreliable. Microsoft's transport rule engine can strip or modify your HTML, leading to broken layouts — especially with images and complex designs.

Images must be externally hosted. You can't embed images in transport rules. Every logo, photo, or icon needs a public https:// URL.

No signature on replies/forwards (by default). Transport rules apply to new messages. Getting them to work on replies requires additional configuration and can result in signatures stacking up in long email threads.

Difficult to manage for multiple templates. If different departments need different signatures (e.g., sales vs. support), you need multiple rules with complex conditions.

Option 2: PowerShell Scripts

For IT teams comfortable with scripting, you can use Exchange Online PowerShell to deploy signatures programmatically.

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

# Set signature for a specific user
Set-MailboxMessageConfiguration -Identity "user@yourcompany.co.za" `
  -SignatureHtml $htmlSignature `
  -AutoAddSignature $true

When this makes sense

• You have a dedicated IT person or team
• You need to deploy signatures to 50+ users at once
• You want programmatic control over the rollout

When it doesn't

• You don't have PowerShell expertise in-house
• You need non-technical managers to update signatures
• You want employees to preview their signature before sending

Option 3: Individual Setup (Copy & Paste)

The simplest approach: create a signature template and have each employee paste it into their Outlook settings.

In Outlook Desktop

1. Open Outlook → File → Options → Mail → Signatures
2. Click New and give the signature a name
3. Paste the HTML signature
4. Set as default for new messages and replies

In Outlook Web (OWA)

1. Click the gear icon → View all Outlook settings
2. Go to Mail → Compose and reply
3. Paste the signature in the editor
4. Save

In the new Outlook for Windows

1. Click Settings (gear icon)
2. Go to Accounts → Signatures
3. Click + New signature
4. Paste and save

Pros and cons

Pros: Full design control, employees see the signature while composing, works with any HTML template, no IT expertise needed.

Cons: Relies on employees to set it up correctly, manual process for updates.

Option 4: Third-Party Signature Tools

This is where tools like SendSignatures come in. Instead of fighting with transport rules or PowerShell, you use a visual editor to create branded signatures that employees copy and paste.

Why SA businesses prefer this approach

No IT department required. Any team member can create their signature in 2 minutes. No admin centre access, no PowerShell, no HTML coding.

Consistent branding guaranteed. Everyone uses the same template, colours, and layout. The only things that change are personal details.

Works across all email clients. The HTML is built with tables and inline styles — the only approach that reliably renders in Outlook's Word-based engine.

CDN-hosted images. Logos and profile photos are hosted on a CDN, so they display as images — not as email attachments.

Once-off pricing. Unlike competitors that charge per user per month (R70-R100/user/month adds up fast), SendSignatures Team plan is R2,500 once-off for 5+ users. That's it — no recurring fees.

Which Approach Should You Choose?

Factor	Transport Rules	PowerShell	Copy & Paste	SendSignatures
IT required	Yes	Yes	No	No
Preview while composing	No	No	Yes	Yes
Design flexibility	Limited	Limited	Full	Full
Outlook compatibility	Partial	Partial	Full	Full
Setup time	Hours	Hours	Minutes	Minutes
Ongoing cost	Free	Free	Free	R2,500 once-off

For most South African SMBs and mid-size companies, the combination of copy-and-paste simplicity with a professional signature tool is the sweet spot. You get the design quality and consistency of a centralised solution without the complexity.

Getting Started with SendSignatures for Teams

1. Sign up for a free account at sendsignatures.co.za
2. Design your template — choose colours, layout, and upload your logo
3. Upgrade to Team (R2,500 once-off) for 5+ signatures
4. Share the link with your team — each person fills in their details and copies their signature
5. Done — consistent, branded signatures across your entire company

No transport rules, no PowerShell, no IT tickets. Just professional email signatures that work.

Set up your team signatures →