Outlook signatures don't sync between desktop and web unless roaming signatures is on and your account qualifies. Here's the exact fix, by setup.
The MailSigCraft Team
MailSigCraft
You set your signature once in Outlook — desktop or web, doesn't matter which — and expected it to just be there everywhere else you sign in. Instead the other client shows blank, or worse, shows an old version from months ago. This isn't random flakiness. Outlook signature sync depends on a specific feature called roaming signatures, and it only works if your account type, your build, and a setting buried in Options all line up. Miss any one of the three and desktop and web silently diverge.
Account type — roaming signatures only exist for Microsoft 365 and Outlook.com mailboxes. Exchange on-premises, IMAP, POP, and other third-party accounts were never eligible, on any client.
Build number — classic Outlook for Windows needs build 2303 or newer. Check via File → Office Account → About Outlook.
The cloud-settings toggle — File → Options → General → "Store my Outlook settings in the cloud" must be checked. It ships on by default for eligible accounts, but IT policy or a manual opt-out can flip it off.
If all three check out and it's still not syncing, sign all the way out of the client that's missing the signature and sign back in — the cloud copy is pulled on session start, not on a background timer.
If that fixes it, you're done. The rest of this post covers why sync breaks in the first place, and what to do when the checklist above doesn't resolve it.
Outlook signatures used to live entirely on the device: a local file in %AppData%\Microsoft\Signatures on classic Windows Outlook, a separate local store on Mac, nothing shareable with the web client at all. Microsoft's fix — roaming signatures — moves the signature into your mailbox itself, alongside your mail, calendar, and contacts, so any client reading that mailbox can pull the same copy.
The catch is that this only applies to Outlook for Windows (classic and new) and Outlook on the web, and only for mailboxes hosted on Microsoft 365 or Outlook.com. Outlook for Mac and Outlook mobile read signatures from a different, separate store that roaming doesn't touch — so even a perfectly synced desktop-and-web pair won't extend to your phone.
That split trips people up because "Outlook" reads as one product with one settings panel, when it's really several codebases that happen to share a name and, on Windows and web at least, a mailbox. Desktop and web converge because Microsoft built a genuine shared store for them. Mac and mobile were built on different release cycles with their own local signature handling, and Microsoft hasn't unified them into the same roaming mailbox store — so treating "Outlook" as one syncing unit is the root of most of these support tickets, not any single misconfiguration.
Working as expected — this is where the roaming mailbox copy currently lives.
Check File → Options → General → "Store my Outlook settings in the cloud" is turned on, then sign all the way out of the affected client and back in — the cloud copy only pulls on a fresh session, not a background refresh.
Don't expect this to match automatically even once desktop and web agree with each other.
Based on Microsoft's published roaming-signatures requirements (build 2303+, Microsoft 365 / Outlook.com mailboxes only) and the documented cloud-settings toggle. Not a live check of your tenant — a reliability read on your setup.
Exchange on-premises servers, and any account added as IMAP, POP, or a third-party provider (Gmail, Yahoo, a custom domain not on Microsoft 365), never get a roaming signature store — there's no cloud mailbox for Microsoft to attach it to. If this is your setup, desktop and web were never going to sync automatically, and no toggle fixes it.
Set the signature independently on each client you use. This is the one case where "just configure it twice" genuinely is the correct fix, not a workaround.
Roaming signatures shipped to classic Outlook for Windows starting at build 2303. If your organization is on a slower update channel (Semi-Annual Enterprise Channel lags Current Channel by months), your desktop client may simply predate the feature — it'll keep using the old local %AppData% signature store regardless of what's set on the web.
Check File → Office Account → About Outlook for your build number. If it's below 2303, either wait for your update channel's next release or ask IT to move you to Current Channel if that's within policy.
Some IT deployments — or a leftover from an earlier troubleshooting attempt — set a value at HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Setup\DisableRoamingSignaturesTemporaryToggle. When that DWORD is 1, classic Outlook ignores the mailbox-stored signature entirely and falls back to the local file, even on an eligible account and a recent build.
Open Registry Editor, navigate to that key, and either delete the value or set it to 0. Restart Outlook. This is a per-user setting, so check it on each Windows profile that's affected.
File → Options → General → "Store my Outlook settings in the cloud" is the setting roaming signatures actually depends on — it controls more than just signatures (it also roams some UI preferences), so a well-meaning "reset my settings" pass can turn it off without anyone connecting that action to a signature going missing weeks later.
Re-enable the toggle and restart Outlook. If it's greyed out, a tenant-level admin policy is controlling it and you'll need your Microsoft 365 admin to adjust it centrally.
Even on a fully eligible setup, a freshly changed signature doesn't appear instantly on every client — it has to write to the mailbox, then get pulled by each other signed-in session. Outlook's own team shipped a fix in November 2024 (build 18205.15010) for a specific bug where this propagation could stall indefinitely rather than just being slow, but ordinary lag of a few minutes is still expected behavior, not a bug.
Give it two or three minutes, then sign out and back in on the client that's missing the update — that forces a fresh pull instead of waiting on a background refresh that may not fire while the app stays open.
Both read from the same roaming mailbox store once your account and build qualify. This pair is the most reliable sync relationship Microsoft ships.
Reads the same mailbox-stored signature as desktop, on any browser, on any device — no local install dependency at all.
Historically outside roaming signatures entirely; Mac keeps its own local signature file independent of the Windows/web mailbox store.
Signature is set under Settings → Signature inside the app itself, usually plain-text only, and is never pulled from the roaming mailbox store.
DisableRoamingSignaturesTemporaryToggle in the registry on affected Windows profiles.Not through the same mailbox store that desktop Windows and web use — Mac has historically kept its own local signature file. If your Mac and Windows signatures don't match, that's expected today rather than a bug to chase.
If you edited the signature on a client that isn't actually part of the roaming sync — for example a cached local copy on a device where the cloud toggle got disabled — that edit never wrote to the mailbox. The next sync pulls the older mailbox-stored version over your local change, and it looks like a revert.
Yes — "Store my Outlook settings in the cloud" and the roaming signatures rollout are both controllable via tenant policy in the Microsoft 365 admin center. If the toggle is greyed out in your Options, that's the tell.
Sign out completely and back in on the lagging client. There's no user-facing "sync now" button — the pull happens at session start, not on a timer you can trigger manually.
Just whether it appears and which version shows. Roaming signatures transfers the same HTML/CSS your client already renders — it doesn't re-render or strip anything in transit. If formatting looks different across clients, that's a separate cross-client compatibility issue, not a sync issue.
Not automatically — there's no roaming mechanism outside a Microsoft 365 or Outlook.com mailbox. The practical workaround is to keep your signature HTML in one place you control (the MailSigCraft editor, for example) and re-paste it into each client whenever you update it, rather than relying on any client to propagate the change for you.
Outlook signature sync isn't broken by default — it's gated behind three specific requirements (eligible account, current build, and an enabled cloud-settings toggle) that most people never see spelled out in one place. Confirm those three, force a sign-out/sign-in on the lagging client, and treat Mac and mobile as permanently separate stores rather than something to keep chasing into sync.
Sources: