Microsoft 365 lets you create email signatures without any third-party software, through two built-in means: the local Outlook signature, which each person sets up themselves, and the Exchange transport rule, applied automatically by the server. It's free and already included in your subscription. But as soon as an organization wants signatures that are consistent, carry a logo, and stay up to date on every device, the native route quickly shows its limits. Here they are, honestly, and what a client-side add-in changes.
What are the limits of the native Office 365 signature?
Both native methods share a base of limits that come up constantly in organizations:
- Unreliable images. A logo or banner added by a transport rule often arrives as an attachment for the recipient, or shows as an empty box if the image is merely linked by URL.
- Missing from Sent Items. With a transport rule, the sender never sees their own signature in the sent copy — no way to verify the rendering.
- No fine-grained targeting. Adapting the signature by department, country or role means multiplying Exchange rules, which quickly become unmanageable. There's no simple selection by Microsoft 365 group.
- Manual maintenance. Changing a title, number or logo means editing the HTML by hand, rule by rule, or relying on each employee for the local signature.
- Cross-platform inconsistency. The local Outlook desktop signature does not sync reliably to Outlook web or mobile: the same employee sends different signatures depending on the device.
Why the signature is missing from Sent Items
This is the least understood limit of the transport rule. The sequence is: the user sends their message, a copy is immediately saved to their Sent Items, then the Exchange server applies the signature after that moment, as the message travels on to the recipient.
The result: the recipient gets the signature, but the copy kept by the sender has none. No one in the organization sees what the recipient actually receives, which complicates verification, support and trust in the tool. It's a direct consequence of the server-side architecture.
A client-side add-in reverses the logic: it inserts the signature at compose time, in the draft. What the sender sees on screen is exactly what leaves — and what ends up in Sent Items. This is the approach ATOM Signatures takes.
Inline images: why they break with native
Email clients handle images in two ways. Linked images (by URL) often show an empty box, because many clients block remote loading by default. Embedded images (encoded in the message) tend, with transport rules, to appear as attachments, which clutters the message and sometimes trips filters.
An add-in that builds the signature at compose time controls the final HTML and how the image is referenced more tightly, for more stable rendering in Outlook. On Outlook's quirks — explicit image width and height, tables — see the guide to deploying a signature for the whole organization.
Comparison table: native signature vs ATOM
Here we compare the two native routes (transport rule and local Outlook signature) with ATOM Signatures, a client-side add-in hosted in Canada.
| Criterion | Exchange transport rule | Local Outlook signature | ATOM Signatures |
|---|---|---|---|
| Centralized management | Yes (by admin) | No (each user) | Yes (console + visual editor) |
| Visible in Sent Items | No | Yes | Yes (inserted at compose time) |
| Image reliability | Low (attachments) | Variable | Controlled (managed Outlook HTML) |
| Targeting by Microsoft 365 group | Limited (multiply rules) | None | Yes, by group |
| Up-to-date data (Graph) | No | No | Yes (real time via Microsoft Graph) |
| Desktop / web / mobile consistency | Yes (server), no Sent Items | No | Yes, across Outlook platforms |
| Email leaves Microsoft 365 | No (stays with Microsoft) | No | No (client-side, no third-party routing) |
| Config data hosting | Microsoft | Device / Microsoft | 100% Canada |
| Cost | Included | Included | CAD $1 per user / month |
Note: the transport rule keeps the email within Microsoft — it does not ship it to a third party, unlike some external server-side solutions. Its weakness lies elsewhere: rendering, targeting and Sent Items.
When native is enough, when to choose ATOM
The native signature can be enough if…
- Your team is small and a single static signature suits everyone.
- You have no logo, no banner, no per-department variants.
- You accept that each employee maintains their signature, or that a server rule is enough without verifying it in Sent Items.
- You want zero additional cost and zero deployment.
ATOM pays off if…
- You want reliable images and logos, with controlled rendering in Outlook.
- You need variants by Microsoft 365 group (department, region, role).
- You want centralized updates and current data pulled from Microsoft Graph.
- You require consistency across desktop, web and mobile, with the signature visible in Sent Items.
- Canadian data residency and Law 25 compliance matter to your organization.
ATOM Signatures inserts the signature client-side in Outlook, at compose time: the email never leaves Microsoft 365, the configuration data is hosted in Canada, and administration runs from a console with a visual editor. On the Law 25 angle, see the email signatures and Law 25 guide.
Frequently asked questions
Can you manage signatures without software in Microsoft 365?
Yes, with two native means: the local Outlook signature, set by each user, and the Exchange transport rule, applied by the server. Both work, but neither handles images reliably, offers fine-grained group targeting, or avoids manual maintenance. A rule-based signature also does not appear in Sent Items.
Why doesn't a transport-rule signature appear in Sent Items?
Because the rule runs on the Exchange server after send, once the message has already left the sender's mailbox. The copy kept in Sent Items is saved before that processing, so it has no signature. The user never sees what the recipient receives.
Are native signature images reliable?
Not always. Images embedded by a transport rule often arrive as attachments or are blocked by the recipient's email client. Linked images can show an empty box. An add-in that inserts the signature at compose time produces better-controlled HTML and more stable images.
When is the native signature enough?
For a very small team, a single static signature with no images or per-department targeting, the native route can be enough. As soon as you need reliable visuals, per-group variants, centralized updates or consistency across desktop, web and mobile, a dedicated tool pays off.
Go beyond native limits. ATOM Signatures brings group targeting, reliable images and a signature visible in Sent Items — client-side, hosted in Canada, at CAD $1 per user per month.
Go further: the complete Microsoft 365 email signature guide, the Exchange transport-rule signature and deploying for the whole organization.
How does the native Microsoft 365 signature work?
Without a third-party tool, Microsoft 365 offers two distinct mechanisms that should not be confused:
Our guide on the Exchange transport-rule signature covers the step-by-step setup and its constraints. For an overview of the available methods, see the complete Microsoft 365 email signature guide.