Blog/ Outlook how-tos

New Outlook Signature Not Syncing? Here Is Why

Nafiul HasanNafiul Hasan· 14 min read
Illustration for a new Outlook signature not syncing: a signature file stranded on one desktop PC while a cloud-stored copy reaches a laptop, browser and phone

The short answer

New Outlook stores signatures in your mailbox in the cloud, per account. Classic Outlook stores them as local files on one PC. Nothing carries them across, so a classic signature simply is not there after you switch. The fix for most people is recreating it once in new Outlook, where it then roams with the account.

New Outlook signature not syncing? Signatures live in the cloud per account, not in classic Outlook's local files. Causes, fixes and per-client differences.

On this page
  1. 01Why is my new Outlook signature not syncing?
  2. 02Before you change anything, pin down four things
  3. 03The eight causes, and how to tell which one you have
  4. 04Fix 1: move a signature from classic Outlook to new Outlook
  5. 05Fix 2: get one signature onto every device
  6. 06Which Outlook client stores signatures where?
  7. 07Why does a shared or delegated mailbox use the wrong signature?
  8. 08Why are the images in my signature missing?
  9. 09When your admin's settings override yours
  10. 10How to stop this happening again
  11. 11Does any of this mean you should change email client?
  12. 12The short version

Why is my new Outlook signature not syncing?#

If your signature vanished, appears on one device but not another, or turns up as the wrong one, the cause is almost always a single fact: classic Outlook and new Outlook keep signatures in completely different places. Classic Outlook writes them to files on the PC where you created them. New Outlook keeps them in your mailbox settings in the cloud, attached to one specific account.

That one difference explains the whole list of symptoms. A file on a hard drive cannot follow you anywhere, which is why classic signatures were always per-machine. A cloud signature can follow you, but only to clients that read the same cloud settings, and only for account types that support it.

So there is no migration step you missed. Switching does not import your old signatures, because there is nowhere in new Outlook for a local signature file to land. As of July 2026 it has no local signatures folder at all.

For most readers this is a five-minute job: recreate the signature once in new Outlook, assign it to the right account and to replies as well as new messages, then check each device you send from. The rest of this post is for the cases where that is not enough.

Check which client you are actually in

Classic Outlook for Windows has a File menu. New Outlook does not, and shows a New Outlook toggle in the top corner. Signature advice is useless unless you know which of the two you are looking at, because the storage model differs in each.

Before you change anything, pin down four things#

Signature problems get misdiagnosed because people describe the symptom without the context that decides the fix. Answer these and the right row of the table below is usually obvious.

  • Which client: classic Outlook for Windows, new Outlook for Windows, Outlook on the web, Outlook for Mac, or Outlook for iOS and Android.
  • Which account the signature is attached to. New Outlook sets signatures per account, so one made on your work account does nothing on the personal one.
  • What kind of account it is: Microsoft 365 work or school, a personal Microsoft account, or a connected Gmail, Yahoo or IMAP account. They do not behave the same.
  • Whether your organisation applies signatures centrally. If it does, half the settings on your screen are decorative.

The eight causes, and how to tell which one you have#

Work down this table until a row matches. Only the last two need someone else's help.

CauseHow to confirmFix
The signature stayed behind in classicNew Outlook's signature list is empty, but the old files are still in the Signatures folder under your Windows roaming app data.Recreate it. Copy the rendered signature out of the classic editor, paste it into the new one, re-insert images.
It is attached to a different accountChange the account selector in the signature settings. It appears under one account and not the others.Create or duplicate the signature for every account you send from.
It is set for new messages but not repliesIt appears on a fresh email and is absent when you reply or forward.New Outlook assigns signatures separately for new messages and for replies and forwards. Set both.
The account type does not roam signaturesIt syncs for a Microsoft 365 work account but not for a personal Microsoft account or a connected Gmail or IMAP account.Set it separately in each client. Microsoft tells Microsoft account users to create the signature in both places.
Classic Outlook is on an older buildClassic never picks up a signature made in new Outlook or on the web, on any machine.Classic desktop reads roaming signatures only from Version 2303 and later. Update it, or accept that classic stays local.
The signature disappears a while after you save itIt works for a session or a day, then is gone without you touching it.Microsoft documented this: cloud settings data cached wrongly in the Windows registry stopped new signatures reaching the cloud, and the client then deleted them. Fixed in the 12 November 2024 updates.
Images did not survive the moveText arrives intact; the logo is a blank box or a broken-image icon.Re-insert each image in the new editor. Pasted markup often still points at a file path that exists only on the old PC.
An organisation-wide signature is being appliedRecipients see a signature you never created, and your own Sent Items copy does not contain it.It is added at the mail server by a mail flow rule or a signature management tool. Only an admin can change it.

These symptoms look unrelated because people compare them at the wrong level. Missing after a switch, wrong on a shared mailbox and different on a phone are not three bugs. They are three consequences of where the signature is written.

Two storage models side by side: classic Outlook signature files sitting on a single PC and unable to reach other devices, next to one cloud-stored signature read by a desktop, a browser and a phone
A file on one machine can never roam. A cloud signature roams only as far as the clients reading the same mailbox settings.

Fix 1: move a signature from classic Outlook to new Outlook#

There is no import button, and copying the signature files across does nothing. What works is copying the rendered signature from one editor into the other, then repairing the images by hand.

  1. 1

    Open the signature in the classic editor

    Classic keeps signature editing inside its mail options. Open the one you actually send with — most people have three and use one.

  2. 2

    Select the whole signature and copy it

    Copy from inside the editor pane, where it is rendered. That carries fonts, colours, spacing and links. Copying the underlying file instead gives you markup new Outlook will not take.

  3. 3

    Paste it into a new signature in new Outlook

    The signature editor lives in new Outlook's settings, under the account you want it on. Give it the same name you used in classic so you can tell devices apart later.

  4. 4

    Test every link

    Hyperlinks usually survive the paste, but not always. A dead booking or phone link can sit in a signature for months before anyone mentions it.

  5. 5

    Re-insert each image from a file or URL

    Do not trust the pasted copy. Classic stores signature images in a folder beside the signature file on that PC, and that reference means nothing to a cloud-stored signature.

  6. 6

    Assign it to the account, and to replies

    New messages and replies and forwards are separate assignments. Skipping the second is the commonest reason people say the signature only works half the time.

  7. 7

    Send two tests

    One to yourself, one outside your organisation. The external test is what catches blocked images and a server-side signature being appended on top of yours.

  8. 8

    Keep the classic files for now

    That folder is your only backup. Do not clear it out on switch day; give the new setup a few weeks.

Fix 2: get one signature onto every device#

Roaming works well between new Outlook and Outlook on the web on a Microsoft 365 work or school account. It works less well elsewhere, and not at all on phones. Set expectations accordingly.

  1. 1

    Pick one client as the place you edit

    For a Microsoft 365 account, make new Outlook or Outlook on the web your canonical editor. Both read the same cloud mailbox settings, so a change in one is a change in the other.

  2. 2

    Wait a few minutes, then restart the other client

    Roaming is not instant. Clients usually refresh cloud settings on start, so restart before concluding sync is broken.

  3. 3

    Update classic Outlook if you still use it

    Classic reads roaming signatures only from Version 2303 and later. Older builds see the local folder and nothing else.

  4. 4

    Set mobile by hand

    Roaming signatures are not supported on Outlook for iOS and Android as of July 2026. Switch on per-account signatures in the app and set each one there.

  5. 5

    Make the mobile version plainer on purpose

    Mobile handles rich HTML signatures poorly and tends to flatten them toward plain text, which turns logos into junk. Name, role, company, one link.

  6. 6

    Re-test after any change

    Editing a roaming signature on one client rewrites it for the others. Where two people share a mailbox, the last save wins.

Mobile is the one that will not roam

If the signature is right on the laptop and wrong on the phone, nothing is broken. Outlook mobile keeps its signature on the device, and it will keep whatever was typed there in 2022 until you change it.

Which Outlook client stores signatures where?#

Check this before you blame sync. Behaviour as observed in July 2026 — Microsoft moves these, so verify on your own build if a decision rests on it.

ClientWhere the signature livesRoams with the account?Per-account signatures
New Outlook for WindowsCloud mailbox settings. No local folder.Yes for Microsoft 365 work and school accountsYes
Outlook on the webThe same cloud mailbox settingsYes, and it shares new Outlook's signature listYes
Classic Outlook for WindowsLocal files on that PC, plus a folder of imagesOnly from Version 2303 and later; older builds are local onlyYes
Outlook for MacAccount settings on the MacMixed and rolling out unevenly. Verify on your build.Yes
Outlook for iOS and AndroidOn the deviceNo. Not supported as of July 2026.Yes, once per-account signatures is on

Why does a shared or delegated mailbox use the wrong signature?#

Because the signature belongs to the account you are signed in as, not to the address in the From field. Change the From to a shared mailbox and new Outlook still inserts your own signature, since nothing binds a signature to a sending address automatically.

That bites hardest on team mailboxes — support, accounts, bookings — where a personal signature under a shared identity reads as careless. Microsoft's feature comparison also still lists shared mailbox delegate access as only partially available in new Outlook, updated April 2026, so expect rough edges here.

  • Where permissions allow, add the shared mailbox as its own account rather than an extra folder. It then gets its own per-account signature and picks it automatically.
  • Otherwise create a second signature named after the shared mailbox and select it by hand. Reliable, but only as reliable as the person remembering.
  • For a team that must never get it wrong, apply the signature at the server. It is the only option nobody can forget, and it needs an admin.

Watch where the signature lands on a reply

When a shared mailbox is used inside your primary account in new Outlook or Outlook on the web, an inserted signature can appear at the cursor rather than at the end of the message. Click at the bottom of the draft first, and read the message back before sending.

Why are the images in my signature missing?#

Only the first cause below is really about syncing. The rest are about how the image was added and what the recipient's client does with it.

  1. 1

    Re-insert rather than paste

    A pasted signature can carry an image reference pointing at the old machine. Insert the file itself so the signature owns a copy.

  2. 2

    Resize the file before inserting it

    Dragging an image smaller in the editor changes how it looks, not what it weighs. Export it at display size and insert that.

  3. 3

    Choose embedded or hosted deliberately

    Embedded images always render but add weight to every message. Images linked from a URL keep messages small and show as a placeholder for anyone blocking remote content, which is a lot of people.

  4. 4

    Never put information only in an image

    A phone number inside a logo is invisible to anyone blocking images, to screen readers and to plain-text clients. Keep the text as text.

  5. 5

    Test outside your organisation

    Internal mail is treated more generously than external mail. Send to a personal address and open it on a phone, where layouts break first.

When your admin's settings override yours#

Two organisation-level settings explain a lot of reports that look like sync failures, and neither is visible from your signature editor.

The first is a server-applied signature. Exchange Online can add a signature, disclaimer or footer as messages pass through mail flow, using a mail flow rule. Because that happens at the server, your Sent Items copy does not include it — which is why people insist a signature is missing while every recipient can see it. Set your own signature as well and recipients get both.

The second is roaming being switched off on purpose. Exchange Online has a tenant-wide setting that disables roaming signatures for new Outlook and Outlook on the web while leaving classic desktop alone. Organisations use it because the PowerShell that pushes managed signatures to mailboxes stops applying once roaming is enabled. If your edits keep reverting to a corporate template, that is usually why.

Neither is fixable from your own settings. Ask IT which is in play before rebuilding a signature that will be overwritten anyway.

How to stop this happening again#

Signatures break at predictable moments: switching clients, a new laptop, a rebrand, a job title change. A few minutes of housekeeping makes each one a non-event.

  • Keep a master copy outside Outlook — the text in a note, and the image files at the size you use.
  • Name signatures by purpose rather than Signature1. External, Internal, Reply and Shared Mailbox tell you what to pick under pressure.
  • Edit in one place. For a roaming account, pick new Outlook or Outlook on the web and always change it there.
  • Set the reply signature at the same time as the new-message one, every time. It is the step people skip.
  • Keep the classic signatures folder until you have run several weeks on new Outlook without missing anything.
  • If several people need to look consistent, stop doing it per person and push it centrally.

Does any of this mean you should change email client?#

No. A signature that will not sync is a settings problem with a settings fix, and swapping clients over it would cost more than it saves.

For disclosure: we build AI Emaily, an AI email client that connects Outlook, Gmail and IMAP accounts in one place, with per-account signatures documented at /docs/signatures and replies drafted from a Personal Context you set yourself. Worth a look if your real problem is the hours the inbox takes. Not if it is a missing logo.

The short version#

Classic Outlook signatures are files on one PC. New Outlook signatures are cloud settings on one account. Nothing moves between them, so the signature you had is not lost — it is somewhere new Outlook cannot see.

Recreate it once in new Outlook, re-insert the images, assign it to the right account and to replies, then set mobile by hand because phones do not roam. If it still misbehaves, the cause is a shared mailbox, an old classic build or an admin setting, and the causes table tells you which.

Frequently asked

Nafiul Hasan

Written by

Nafiul Hasan

Nafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.

EntrepreneurAI Automation System BuilderAI EnthusiastBuilds AI Enterprise Solutions10+ years experience
More from Nafiul
Ready when you are

One client for Outlook, Gmail and IMAP — with an AI chief of staff

AI Emaily keeps every account in one inbox and drafts from a Personal Context you set, with approval before send, undo and an audit trail. Start free at app.aiemaily.com/signup.

  • 7-day free trial
  • Cancel anytime
  • Every provider