Server-side signatures are the dependable kind: they apply on every device and cannot be bypassed. Two questions still come up in almost every project: "Why can't I see my signature while writing?" and "Why is it missing from my sent folder?" Both have the same cause — and, for Microsoft 365 mailboxes, the same fix: an Outlook add-in that places the centrally managed signature in the compose window.
Why the sent folder has no signature
Outlook files the copy in "Sent Items" before the mail reaches the signature server. The signature is added in transit: the recipient sees it, the sender's own copy does not. That is not one vendor's quirk; it is true of every purely server-side signature solution. The compose window stays empty for the same reason. When replying, you can't tell whether the signature lands above or below the quote.
What the add-in changes
The add-in inserts the signature into every new mail, reply and forward — and recalculates it when recipients change, for example when an external address is added. Template and rules still come from the server: the add-in queries the same rule engine the gateway and the policy tester use. What you see is exactly what the server would have appended.
Because the signature is already in the draft, it is also in the copy in "Sent Items".
Where it works — and where it doesn't
- Outlook on the web and new Outlook (M365 subscription): yes.
- Classic Outlook for Windows (2021 or later, or M365 subscription): yes.
- Outlook for Mac (new interface): yes.
- Outlook on iPhone, iPad and Android with an M365 mailbox: yes, with no visible interface.
- Outlook with Exchange on-premises (2016, 2019, SE): the add-in loads but cannot set the signature. The server stops at requirement set 1.5; the required setSignatureAsync belongs to 1.10.
- Outlook with an IMAP or POP account (STRATO, IONOS, All-Inkl, 1&1): no. Office add-ins require an Exchange mailbox.
- Apple Mail: no. MailKit offers no API for the compose body.
Wherever the add-in doesn't apply, the server appends the signature on send as before. The add-in is convenience on top, not a replacement for the server path. Thunderbird 128 and later has its own add-on built on the same principle.
Rollout: one manifest in the admin center
- In the Microsoft 365 admin center: Settings → Integrated apps → Upload custom apps.
- App type Office Add-in, then "Provide link to manifest file".
- Assign people or groups and deploy.
Windows, Mac, web, iOS, Android https://app.signaturehub.de/addin/outlook/manifest.xml
One manifest covers every device: it registers the events for desktop and web and also for Outlook on phones. If you uploaded a second add-in "SignatureHub Mobile" earlier, remove it and update the existing "SignatureHub" once to the current version. Sign-ins are kept.
It can take up to 24 hours until every user sees the add-in. That is Microsoft's distribution cycle. To test beforehand, sideload it: Outlook on the web → Manage add-ins → My add-ins → "Add from URL".
Sign-in: an eight-character code
The user opens a new mail, clicks SignatureHub → Signature, confirms their mail address and requests a code. The eight-character code arrives by mail and is typed in once. It is valid for 15 minutes, single-use, and burned after five failed attempts.
After that a device token with a 365-day lifetime is attached to the account. Users see and revoke it in the self-service portal under "Mail client add-ins", admins on the mail users page.
On the phone
On iPhone, iPad and Android there is nothing to set up and nothing to see: no button, no bar. Three things to know:
- Sign-in happens on the desktop. Outlook offers no add-in surface while composing on mobile. Anyone who has signed in once in Outlook on PC, Mac or the web is covered on the phone automatically — the token lives in the mailbox.
- Minimum Outlook app version: 4.2352 for new messages, 4.2425 for recalculation when recipients change.
- Quick replies: with "Reply" at the bottom of a mail, the signature only becomes visible once you drag the window to full height. That is how Outlook Mobile behaves.
Why the signature doesn't appear twice
If the add-in sets the signature and the server appends it again, it would be in the mail twice. Two markers prevent that: the header X-SignatureHub-Client and an invisible element at the end of the signature. When the gateway finds either, it skips its own injection and writes mail.client_addin_signature to the audit log.
Two markers, because Exchange Online strips unknown headers on some routes and Outlook Mobile cannot set any. From there only the body marker arrives. If both are missing, the server signs as before — without the add-in you lose nothing.
What to know beforehand
- Users can edit the signature before sending. It sits in the draft as ordinary text. If compliance rules that out, don't deploy the add-in and stay on the pure server path.
- No Exchange Online, no automation. Exchange on-premises and IMAP accounts stay on the server path — and with a sent folder without a signature.
- Updates need the admin. A new manifest version has to be approved in the Microsoft 365 admin center.
Bottom line
With Microsoft 365 mailboxes you don't have to choose between "reliable on the server" and "visible in the client". The server path remains the safety net for every device; the add-in shows the same signature while you write and gets it into the sent folder. The effort: one manifest URL in the admin center and one code per user.