Signatures Not Syncing from Classic to New Outlook

After migrating to the New Outlook interface, users frequently open a new message window only to find that their familiar email signatures are missing. The signature selector dropdown may be completely empty, or it may only offer a basic plain-text default. Because classic Outlook and New Outlook store and synchronize signature definitions using entirely different systems, client-side signatures do not automatically transition without specific conditions being met.

Fast Fix

Classic Outlook stored signatures locally on your hard drive, whereas New Outlook only reads signatures saved to your cloud mailbox. To resolve this, open Classic Outlook, ensure Roaming Signatures are enabled, or manually open %appdata%\Microsoft\Signatures, copy your HTML signature, and paste it into New Outlook under Settings > Accounts > Signatures.

---

Diagnostic Snapshot

Property	Details
Symptom	Email signature dropdown in New Outlook is blank or missing pre-existing signatures
Root Cause	Classic signatures were stored in local machine files rather than the Exchange Online cloud mailbox
Storage Mechanism	Classic: Local %appdata% directory; New Outlook: Exchange Online Cloud Settings API
Resolution Time	5 to 10 minutes

---

The Underlying System Break: Local Files vs. Cloud Roaming

Understanding why signatures do not carry over requires examining where each client reads its data:

1. Classic Outlook (Local File System): For years, classic Outlook stored signatures as individual files inside your local Windows user profile (%appdata%\Microsoft\Signatures). Each signature existed in three formats: .htm for HTML email, .rtf for rich text, and .txt for plain text.
2. New Outlook (Exchange Online Cloud Settings): New Outlook contains no code to read files from your Windows user directory. Instead, it queries the Microsoft 365 Cloud Settings service via Microsoft Graph. If your signature does not exist in the Exchange Online cloud mailbox, New Outlook treats your account as having no signatures configured.

Classic Outlook Signature Architecture
 └── C:\Users\<User>\AppData\Roaming\Microsoft\Signatures\
      ├── MySignature.htm  (HTML format)
      ├── MySignature.rtf  (Rich Text format)
      └── MySignature.txt  (Plain Text format)
      * Stored strictly on local machine disk *

New Outlook Signature Architecture
 └── Exchange Online Mailbox (Cloud Settings API)
      └── UserConfiguration: "OWA.UserOptions"
           * Retrieved via web payload; ignores local disk files *

When an organization transitioned to modern Microsoft 365 builds, a feature called Outlook Roaming Signatures was introduced to copy local signatures into the cloud mailbox automatically. However, if this synchronization feature was disabled by an IT policy, if your classic client was out of date, or if you used an unsupported email provider, the cloud copy was never created.

---

Progressive Troubleshooting and Migration Steps

Step 1: Check Signatures in Outlook on the Web (OWA)

To determine whether your signatures are already stored in the cloud or stranded on your local PC:

1. Open a web browser and navigate to Outlook on the web (outlook.office.com).
2. Sign in with your primary email credentials.
3. Click the Settings (gear icon) at the top right, then go to Mail > Compose and reply.
4. Check the Email signature section:
   • If your signature appears here: Your cloud signature exists. The New Outlook client simply needs a profile refresh. Sign out of New Outlook (Settings > Accounts > Sign out) and sign back in to pull the cloud configuration.
   • If this area is blank: Your classic signatures were never migrated to the cloud and must be moved manually or synced via classic Outlook.

Step 2: The Direct Migration Method (Copy and Paste)

If you have a customized signature with formatting, logos, and links, the most reliable method to migrate it is copying the raw HTML assets directly:

1. Press Win + R to open the Windows Run box.
2. Type the following path and press Enter: %appdata%\Microsoft\Signatures
3. Locate the .htm file corresponding to your signature name (for example, WorkSignature.htm).
4. Right-click the .htm file and select Open with > Google Chrome (or Microsoft Edge).
5. When the signature displays in your browser window, press Ctrl + A to highlight everything, then press Ctrl + C to copy it.
6. Open New Outlook.
7. Navigate to Settings (gear icon) > Accounts > Signatures.
8. Click + New signature, name it, and press Ctrl + V into the signature editor box.
9. Select your default signatures under Select default signatures for “New messages” and “Replies/forwards,” then click Save.

[ + New signature ]
Signature Name: [ Corporate Official ]
┌──────────────────────────────────────────────────────────┐
│ John Doe | Systems Administrator                         │
│ Example Corp | john.doe@example.com                      │
│ [Image: Company Logo]                                    │
└──────────────────────────────────────────────────────────┘
For New Messages:    [ Corporate Official ▼ ]
For Replies/Forwards:[ Corporate Official ▼ ]

Step 3: Resolving Image and Formatting Glitches

When pasting signatures into New Outlook, images and logos occasionally appear broken or as empty bounding boxes:

• Embedded vs. Linked Images: Classic Outlook allowed images to be pasted as local disk references (e.g., file:///C:/Users/.../image.png). New Outlook operates in a cloud context and cannot display local file links.
• Fixing Broken Logos: If an image fails to appear, delete the broken image placeholder inside the New Outlook signature editor. Click the Insert picture inline icon in the editor toolbar and upload the PNG or JPEG directly from your computer. This base64-encodes the image into the cloud signature payload.

Step 4: Verifying Roaming Signatures Group Policy (For Enterprise)

In managed enterprise environments, signatures may fail to sync because your IT department explicitly disabled cloud roaming signatures via Group Policy during past rollouts.

To verify whether this policy block exists:

1. Press Win + R, type regedit, and press Enter.
2. Navigate to: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Setup
3. Look for a DWORD value named DisableRoamingSignaturesTemporaryToggle.
4. If this value exists and is set to 1, classic Outlook is blocked from syncing local signatures up to Exchange Online.
5. Changing this value to 0 (or having your administrator remove the policy) allows classic Outlook to upload your local signatures to your Exchange Online mailbox automatically during its next send/receive cycle.

---

Third-Party Signature Solutions (Exclaimer, CodeTwo, WiseStamp)

If your organization manages corporate email disclaimers and branding using third-party signature management software, classic Outlook typically used a local Windows agent to inject signatures into new messages.

Because New Outlook does not support legacy desktop agents or COM hooks, third-party signatures must be deployed through modern Office Web Add-ins installed by your Microsoft 365 administrator:

• If your organizational signature does not appear automatically, verify with your IT department that their signature provider’s modern web manifest has been deployed tenant-wide.
• For more information on how add-in models function in this client, see:
  • Outlook Add-ins Not Loading (COM vs. Web Add-in Conflict)

---

Diagnostic Escalation

If your signatures reset, fail to save, or revert after every system reboot in New Outlook, your cloud profile options may be blocked by stale authentication tokens or a read-only mailbox configuration:

• How to Clear Office Credential Cache on Windows 11 (The Modern Way)

If you need to return to your classic desktop workflow while working with complex multi-signature setups:

• How to Revert to Classic Outlook after “Forced Update” (The Registry Fix)