Outlook's email signature has a well-known flaw: it is never quite the same from one device to the next. On Windows you get a polished template with a logo, on Mac you have to rebuild it by hand, and on iPhone or Android you are often left with a single line of plain text — when it hasn't disappeared entirely. This guide explains why the native behaviour is so inconsistent and how a client-side add-in applies the same signature across every Microsoft 365 platform, mobile included.
Why the native signature differs by platform
Each Outlook app manages its own signature, in its own configuration store. Outlook for Windows keeps it in a local folder, Outlook for Mac in its preferences, Outlook on the web in the mailbox settings, and the mobile apps in the device settings. There is no single source shared across these environments.
Microsoft introduced roaming signatures to sync the signature across some recent Outlook versions, but coverage remains partial: it does not extend to mobile, depends on the client version, and offers no central control on the organization's side. The result: without a dedicated tool, a company cannot guarantee that all its employees send the same signature, whatever the device.
Which Outlook platforms an add-in covers
An event-based Outlook add-in relies on two triggers: OnNewMessageCompose (when a new message, reply or forward opens) and OnMessageSend (at send time). Their availability varies by platform, which determines how the signature is applied:
| Platform | Insert at compose | Check at send | Full HTML signature |
|---|---|---|---|
| Outlook for Windows (classic and new) | Yes | Yes | Yes |
| Outlook on the web (OWA) | Yes | Yes | Yes |
| Outlook for Mac | Yes | Yes | Yes |
| Outlook for iOS (iPhone / iPad) | Yes | No | Yes |
| Outlook for Android | Yes | No | Yes |
On mobile, only insertion at compose is supported: the signature is added as soon as the user starts writing, rather than checked at send. In practice, the message goes out with the right signature in every case.
How the signature works on iPhone and Android
This is the area the native setting handles worst. The Outlook mobile apps only allow a plain-text signature, typed in manually by each user, with no logo, no formatting and no link to the desktop signature. At any scale, consistency is simply impossible to maintain.
With an event-based add-in, the OnNewMessageCompose event fires on iOS and Android the moment the user opens a new email, a reply or a forward. The add-in then inserts the full HTML signature — logo, contact details, social links — identical to the one on desktop machines. The user has nothing to configure on their phone.
Because the send event (OnMessageSend) does not exist on mobile, the per-seat licensing logic is triggered at compose time rather than at send — a purely internal difference, invisible to the user.
The Outlook for Mac signature
Outlook for Mac shares the same add-in engine as Outlook for Windows and the web. An event-based add-in therefore inserts the full HTML signature at compose time, exactly as on the other desktop clients. No more manually rebuilding the template in Outlook Mac's preferences, with the formatting drift that entails.
For the organization, this means one signature designed once, then applied across the whole fleet — Windows, Mac, web and mobile — with no special handling for Mac users.
The limits of the native setting
Before opting for an add-in, it is worth understanding why native management quickly hits its ceiling in a business:
- Local storage: each device keeps its own copy; nothing guarantees they match.
- Plain-text mobile: no logo or formatting on iOS and Android in native mode.
- No central control: the administrator cannot enforce or update a signature remotely.
- Frozen data: a change of title or phone number forces every employee to edit their signature by hand, on each device.
Centralized management with data kept current in real time via Microsoft Graph removes these gaps: the signature always reflects the organization's directory, on every device.
Deploying one uniform signature everywhere
In practice, here are the steps to get an identical signature on Windows, Mac, the web and mobile:
- Design the signature once in the visual editor (logo, contact details, social links).
- Target users by Microsoft 365 groups rather than device by device.
- Deploy the add-in centrally from the Microsoft 365 admin center.
- Confirm the mobile prerequisites are met (event-based add-in, mobile form factor support).
- Test on Windows, web, Mac, iOS and Android from a pilot account.
For the full centralized deployment walkthrough, see the guide on deploying a signature for the whole organization.
Frequently asked questions
Why isn't my Outlook signature the same on my iPhone?
Because the native signature is stored locally on each device. Outlook for iOS and Android only offers a short plain-text signature, with no logo or formatting, and no link to the one on your Windows or Mac machine. A client-side add-in fixes this inconsistency by inserting the same signature everywhere.
Can an add-in really run on Outlook mobile?
Yes. With event-based add-ins, the OnNewMessageCompose event is supported on Outlook for iOS and Android. The signature is inserted automatically the moment the user starts a new email, a reply or a forward, with no manual step.
Does the signature apply on Outlook for Mac?
Yes. An event-based add-in covers Outlook for Mac just like Outlook for Windows and Outlook on the web. The full HTML signature — logo, contact details, social links — is inserted at compose time, with no manual setup on each machine.
Does an email sent from my phone leave Microsoft 365?
No. The add-in runs client-side, inside Outlook. The signature is added to the message locally before sending; the email is never routed through a third-party server. Only the signature's configuration data is hosted on the provider side — in Canada in ATOM's case.
One signature, on every device. ATOM Signatures applies the same signature in Outlook for Windows, web, Mac, iPhone and Android — client-side, with 100% Canadian hosting.
Go further: the complete Microsoft 365 email signature guide and dynamic signatures via Microsoft Graph.
Sources
- Microsoft Learn — event-based Outlook add-ins and mobile support: learn.microsoft.com
- Microsoft Support — roaming signatures in Outlook: support.microsoft.com