Why Your Email Signature Does Not Show Up on Mobile

TL;DR: After a company-wide signature rollout, the most common complaint is not that the signature looks wrong. It is that the signature does not appear when someone replies from their phone. Mobile is a different problem from desktop, not a smaller version of it. Outlook mobile handles signatures separately from desktop and from Microsoft’s roaming signatures, and deployment methods differ a lot in whether they reach it. This article explains why, and gives you a test to run on any tool before rollout.


Why mobile is a different problem

It is tempting to treat mobile as a small part of the desktop problem: get the desktop rollout right and mobile should follow. It does not. A large share of email is read and replied to on phones. Litmus tracks email client and device market share, and mobile clients are consistently a big part of the mix. So “does the signature appear on mobile?” can block a rollout.

The reason is that “Outlook” is not one app with one way of handling signatures. 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 handle signatures in their own way. Several are only loosely connected.

Microsoft’s roaming signatures store a signature against the mailbox in the cloud, not on one device, so it can follow a user between some apps. That is a step towards one signature everywhere. But Microsoft’s support documentation says roaming signatures are not currently available in Outlook Mobile for iOS and Android. Mobile has its own separate signature setting. A rollout can work on Windows and the web and still leave mobile untouched. (For where that setting is, and the desktop equivalents, see How to Add or Change an Email Signature in Outlook.)

The deployment methods, tested against mobile

Native Microsoft 365 mail flow rules (transport rules). These work on the mail server. They add a disclaimer or signature after the message leaves the sender’s mailbox and before it is delivered, so they do not depend on which app sent it. This is the one method that reliably reaches every device, mobile included. The trade-offs are no preview while writing, no control over replies and forwards, and limited personalisation. How to Set Company-Wide Email Signatures for All Employees in Microsoft 365 covers them.

Server-side third-party tools (Exclaimer, CodeTwo, Letsignit, Rocketseed and similar) work on the same principle. Mail is routed through the vendor’s servers, which add the signature. So, like mail flow rules, they cover mobile without extra work. That is a real advantage of the server-side model, separate from the data-routing trade-offs in Email Signature Tools and GDPR: What Your DPO Needs to Know.

Roaming signatures cover new Outlook for Windows and Outlook on the web. They sync a cloud-stored signature between those two. As above, they do not cover the Outlook mobile app. They also do not cover on-premises Exchange mailboxes, POP/IMAP or third-party mail.

Add-in-based signatures insert the signature when someone starts writing a message. Signature Management for Microsoft 365: Server-Side vs Add-In covers the approach. The mobile picture is more mixed than most coverage says, so it is worth being exact.

Add-ins have mostly been a desktop and web technology. An add-in can put a signature into the compose window in classic Outlook, new Outlook, Outlook on the web and Outlook for Mac. It cannot reach a native mobile mail app. The Outlook mobile app is separate code from desktop Outlook, and native apps such as iOS Mail or Android Gmail never run Outlook add-ins.

One thing has changed. Microsoft’s Office Add-ins platform now has an event-based activation feature for Outlook mobile. An add-in can handle an OnNewMessageCompose event to insert a signature when someone starts a message in the Outlook mobile app. Android and iOS both support it, from specific app versions. This is a real feature, not a roadmap promise. Microsoft’s API reference confirms that the setSignatureAsync method works on mobile from Mailbox requirement set 1.10.

The catch is that it is not automatic. The vendor must build the add-in with a mobile-specific manifest setting (a MobileFormFactor element and a LaunchEvent extension point). That is extra engineering work on top of a standard desktop and web add-in. Most add-in-first tools may not have built it yet, so for most organisations today, add-in signatures still do not reach mobile. But that is a gap in individual tools, not a limit of the platform. Native, non-Outlook mobile apps are different: no add-in can ever reach them, however it is built. Ask any add-in-first vendor directly whether they support Outlook mobile event-based activation. Do not assume that “add-in” means “no mobile”.

The test to run

The reliable way to know whether a tool reaches mobile is to test it:

  1. Send a message from the Outlook mobile app (iOS or Android). Check that the signature appears.
  2. If anyone in your organisation uses a native mail app on the same device, send from that too. A different result from step 1 is normal, not a bug.
  3. Send from desktop and Outlook on the web as a baseline.
  4. Repeat the test after any change to how the tool is deployed or set up. Mobile coverage that worked at rollout can quietly stop working after a routing or configuration change, as with the check in Why Adding an Email Signature Can Break DKIM and S/MIME.

Gmail and Google Workspace have the same split

Gmail works the same way. The Gmail app on Android and iPhone has its own Mobile signature setting, separate from the signature set on a computer. Google’s help page on Gmail signatures says that if someone has not created a signature in the app, it uses the one from their computer. So an old mobile signature, typed once and forgotten, keeps overriding a newer one set centrally.

Two other things trip up Gmail signatures on phones:

  • Images from Google Drive only show if the file is shared publicly.
  • Google’s Append footer, which an admin can add to every outgoing email, is added after sending, so it reaches phones too. But it is the same for everyone and cannot hold personal details.

How to manage email signatures in Google Workspace compares the options for keeping phone and desktop signatures in step.

What this means when choosing a tool

If mobile coverage is a hard requirement, treat it as a deciding factor. A sales or field team that sends most email from a phone is the obvious case. Ask the vendor directly and test it live during evaluation. Do not rely on a feature list. The email signature software buying checklist has a place for this question.

Server-side deployment (native mail flow 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 if the vendor has built mobile event-based activation. Confirm it either way.

This article is about whether the signature appears at all. How it looks once it does, including in dark mode, is covered in The Best Email Signature Designs for 2026.


Frequently asked questions

Why is my email signature missing when I reply from my phone?

Most likely the deployment method your organisation uses does not reach the Outlook mobile app or your native mail app. Mobile handles signatures separately from desktop. Microsoft’s roaming signatures do not extend to Outlook Mobile for iOS and Android, and older or non-mobile add-ins cannot reach the mobile app at all.

Which email signature deployment method works on mobile?

Native Microsoft 365 mail flow rules and server-side third-party tools both reliably reach mobile. They add the signature at the mail server, whichever app sent the message. Add-in-based tools can reach the Outlook mobile app if the vendor has built Microsoft’s mobile event-based activation feature, so confirm it with the vendor. No deployment method reaches a native, non-Outlook mobile mail app.

Can an Outlook add-in insert a signature on mobile?

Yes, but only inside the Outlook mobile app, and only if the vendor built the add-in to support it. Microsoft’s platform supports this through an OnNewMessageCompose event and a setSignatureAsync method, but it takes deliberate mobile-specific work. It cannot reach native iOS Mail, native Android Gmail or Mail, or any other non-Outlook mobile app, however the add-in is built.

How do I know if my signature tool reaches mobile?

Test it. Do not rely on a vendor’s feature list. Send a message from the Outlook mobile app, and separately from any native mail app your people use, and check the signature appears on both. Run the test again after any deployment change, since mobile coverage can stop working without anyone noticing.

Sources

  1. Microsoft Learn — Implement event-based activation in Outlook mobile add-ins — Microsoft Learn
  2. Microsoft Learn — Insert disclaimers, signatures, footers, or headers in Exchange Online — Microsoft Learn
  3. Microsoft Support — Outlook roaming signatures — Microsoft Support
  4. Litmus — Email client market share — Litmus