Why Your Email Signature Doesn't Show Up on Mobile (And What Actually Fixes It)
Drafted with AI assistance and reviewed before publishing. How we write and source articles →
TL;DR: The most common complaint IT admins hear after rolling out a centrally managed signature isn’t that it looks wrong — it’s that it doesn’t appear at all when someone replies from their phone. Mobile is a genuinely different problem from desktop, not a smaller version of the same one: Outlook mobile has its own signature handling, separate from desktop and from Microsoft’s newer roaming-signature feature, and deployment methods vary sharply in whether they reach it at all. This article covers why, and gives you a concrete test to run against any tool before rollout.
Why mobile is a genuinely different problem
It’s tempting to treat mobile signature coverage as a subset of the desktop problem — get the desktop deployment right, and mobile should just follow. It doesn’t, and the reason is architectural rather than incidental. A significant share of email is read and replied to on mobile devices — Litmus tracks ongoing email client and device market share, and mobile clients are consistently a large share of that mix — which makes “does the signature actually appear on mobile” a rollout-blocking question, not a nice-to-have.
The core issue is that “Outlook” isn’t one client with one signature mechanism. Classic Outlook for Windows, new Outlook for Windows, Outlook on the web, Outlook for Mac, and the Outlook mobile app for iOS and Android each have their own signature handling, and several of them are only loosely connected. Microsoft’s own roaming signature feature — which stores a signature against the mailbox in the cloud rather than on a single device, letting it follow a user between some clients — is a genuine step toward unifying this, but Microsoft’s own support documentation is explicit that roaming signatures aren’t currently available in Outlook Mobile for iOS and Android. Mobile has its own, separate signature configuration, full stop — a rollout that “just works” on Windows and web can still leave mobile untouched.
The deployment methods, tested against mobile specifically
Native Microsoft 365 mail flow rules (transport rules). These operate at the mail server level, inserting a disclaimer or signature into a message after it leaves the sender’s mailbox and before it’s delivered — completely independent of which client sent it. This is the one method that reliably reaches every device, including mobile, precisely because it doesn’t rely on the sending client to apply anything at all. The tradeoffs — no compose-time preview, no reply/forward control, limited personalisation — are covered in How to Set Company-Wide Email Signatures for All Employees in Microsoft 365.
Server-side third-party tools (Exclaimer, CodeTwo, Letsignit, Rocketseed, and similar) work on the same underlying principle — mail is routed through server-side infrastructure to have the signature applied, which means mobile coverage comes along for free in the same way native transport rules provide it. This is a genuine, real advantage of the server-side model on the mobile question specifically, independent of the GDPR/data-routing tradeoffs covered in Email Signature Tools and GDPR: What Your DPO Needs to Know.
Roaming signatures cover new Outlook for Windows and Outlook on the web, syncing a cloud-stored signature between those clients — but as covered above, not the Outlook mobile app, and never on-premises Exchange mailboxes, POP/IMAP, or third-party mail.
Add-in-based, compose-time insertion — the approach covered in Email Signature Management for Microsoft 365: Server-Side vs Add-In — is where the mobile picture is genuinely more nuanced than most coverage of this category treats it, and worth being precise about rather than repeating a blanket claim.
The historical, and still generally accurate, position is that Outlook add-ins are a desktop-and-web technology: an add-in injects a signature into the compose window inside classic Outlook, new Outlook, Outlook on the web, and Outlook for Mac, but has no reach into a native mobile mail app at all — the Outlook mobile app is a genuinely separate codebase from desktop Outlook, and a native iOS Mail or Android Gmail app doesn’t run Outlook add-ins under any circumstances.
What’s changed is that Microsoft’s Office Add-ins platform now includes an event-based activation feature for Outlook mobile specifically — an OnNewMessageCompose event, supported on both Android and iOS since specific app versions, that an add-in can handle to insert a signature automatically when a user starts composing a message in the Outlook mobile app. This is a real capability, not a roadmap promise, and Microsoft’s own API reference confirms the specific method (setSignatureAsync) is supported on mobile as of Mailbox requirement set 1.10.
The honest caveat is that this capability isn’t automatic — it requires the add-in itself to be built with a mobile-specific manifest configuration (a MobileFormFactor element and a LaunchEvent extension point), which is additional engineering work beyond a standard desktop/web add-in. Most email signature tools built on the add-in-first model haven’t necessarily implemented this yet, so the practical experience for most organisations evaluating a tool today is still that add-in-based signatures don’t reach mobile — but that’s a current-implementation gap in individual tools, not a hard platform ceiling the way it is for native, non-Outlook mobile mail apps, which remain permanently out of reach for any add-in regardless of how it’s built. Worth asking any add-in-first vendor directly whether they’ve implemented Outlook mobile event-based activation specifically, rather than assuming “add-in” automatically means “no mobile coverage.”
The concrete test
Theory aside, the reliable way to know whether a deployed tool reaches mobile is to test it directly:
- Send a message from the Outlook mobile app (iOS or Android) and check whether the signature appears.
- Send a message from a native mail app on the same device, if anyone in your organisation uses one instead of the Outlook app — a different result here than step 1 is expected and normal, not a bug.
- Send from desktop and Outlook on the web for comparison, to confirm the baseline is working as expected.
- Repeat this test after any change to how the tool is deployed or configured — mobile coverage that worked at initial rollout can silently regress if a routing or configuration change is made later, in the same spirit as the DKIM/S-MIME test covered in Why Adding an Email Signature Can Break DKIM and S/MIME.
What this means for evaluating a tool
If mobile coverage is a hard requirement for your organisation — for example, a sales or field team that sends most of its email from a phone — that’s a legitimate, deciding factor that should be asked about directly and tested live during any vendor evaluation, rather than assumed from a feature list, in the same spirit as the broader evaluation framework in How to Manage Email Signatures Across a Company. It’s exactly the kind of question the email signature software buying checklist exists for. Server-side deployment (native transport rules or a server-side vendor) is the safest default for guaranteed mobile coverage today. An add-in-first tool can also cover the Outlook mobile app specifically, provided the vendor has built mobile event-based activation — worth confirming directly rather than assuming either way, and distinct from The Best Email Signature Designs for 2026’s coverage of how a signature looks once it does render, including dark mode — this article is about whether it appears at all.
Frequently asked questions
Why doesn’t my email signature show up when I reply from my phone?
Most likely because the deployment method your organisation uses doesn’t reach the Outlook mobile app or your native mail app. Mobile has separate signature handling from desktop — Microsoft’s roaming signature feature, which syncs signatures across new Outlook for Windows and Outlook on the web, explicitly doesn’t extend to Outlook Mobile for iOS and Android — and older or non-mobile-specific add-ins have no reach into the mobile app at all.
Which email signature deployment method actually works on mobile?
Native Microsoft 365 mail flow rules and server-side third-party tools both reliably reach mobile, because they insert the signature at the mail server level, independent of which client sent the message. Add-in-based tools can reach the Outlook mobile app specifically if the vendor has implemented Microsoft’s mobile event-based activation feature — worth confirming directly with any vendor rather than assuming. No deployment method reaches a native, non-Outlook mobile mail app.
Can an Outlook add-in insert a signature on mobile at all?
Yes, but only inside the Outlook mobile app itself, and only if the specific add-in has been built to support it — Microsoft’s platform has supported this since a specific app version via an OnNewMessageCompose event and a setSignatureAsync API, but it requires deliberate mobile-specific development work by the add-in vendor. It has no reach into a native iOS Mail app, native Android Gmail or Mail app, or any other non-Outlook mobile mail client, regardless of how the add-in is built.
Do Microsoft’s roaming signatures work on mobile?
No, not currently. Roaming signatures cover new Outlook for Windows and Outlook on the web, but Microsoft’s own documentation confirms Outlook Mobile for iOS and Android isn’t included — mobile has separate, local signature handling.
How do I know if my organisation’s signature tool actually reaches mobile?
Test it directly rather than relying on a vendor’s feature list: send a message from the Outlook mobile app, and separately from any native mail app your organisation’s users rely on, and confirm the signature appears on both. Re-run the test after any deployment change, since mobile coverage that worked initially can regress silently.
SigHQ is building an add-in-first email signature management tool for Microsoft 365 organisations of 50–250 employees — signatures applied in Outlook at compose time, without email routing through third-party infrastructure. Join the waitlist to follow progress.