Why did my Outlook signature disappear after password change

Short answer: changing your account password does not delete signature files on disk. The forced reauthentication that follows can make Outlook use a different profile, lose a roaming copy, or enter a reduced state. That explains why signatures may disappear from the client UI. Fix this by signing in interactively, checking Outlook on the web (OWA) for the mailbox copy, and restoring the client copy from OWA or from the local Signatures files on Windows, macOS, or mobile.

Symptom: what you see and when it appears

Direct answer: the signature usually goes missing right after a password change, an SSO/MFA reauth, or a device re-enrollment. You can see different behavior in each client and that timing helps identify the cause.

You may notice these signs:

• New-composed messages show no signature or the signature list is empty.
• The signature appears in OWA but not in the desktop client.
• The Signatures folder on disk exists but Outlook’s signature UI is blank.
• Outlook opened a new profile and shows a different mailbox name or reduced settings.

These symptoms map to three root causes: Outlook using a different profile; a mailbox or tenant-level change that made roaming signatures inaccessible; or client tokens or policies blocking access to the local signature store until you sign in interactively.

Before you start (applicability and safe checks)

Direct answer: check that you can sign in with the new password and complete MFA, and close Outlook before you copy or restore files. Stop and escalate if IT told you not to touch profile files.

• Make sure you can sign in and finish any MFA prompts.
• Close all Outlook instances before copying or restoring files.
• If your organization applied device re-enrollment, Intune, or new group policy at the same time, contact IT before overwriting files. Policies can redirect %APPDATA% or profile folders.

UI labels and paths are stable across recent Outlook builds, but verify exact menu names if your client looks different.

Fast triage: identify the client and fingerprint

Direct answer: run a short checklist to identify which client and which symptom fingerprint you have. That tells you which fix to try first.

1. Which client are you using: Outlook for Windows, Outlook for macOS, OWA (browser), or Outlook mobile?

2. In OWA: open Settings > View all Outlook settings > Mail > Compose and reply. Is the signature present?

3. On Windows: check if Outlook opened a new profile via File > Account Settings > Manage Profiles. Look for the Signatures folder:

%APPDATA%\Microsoft\Signatures

4. On macOS: quit Outlook and search ~/Library for *.mailsignature files or folders named Signatures.

5. On mobile: open Outlook Settings > Signature and see if the signature field is blank.

6. Note concurrent events: the password change time, Intune prompts, or tenant/mailbox moves.

Match your findings to one of these fingerprints: signature present in OWA but missing in desktop; Signatures folder missing; files present but UI blank; mobile blank but OWA has signature; profile was recreated after reauth.

One-line fixes by fingerprint (single direct action each)

Direct answer: pick the single step below that matches your fingerprint and try it first. Each item is one immediate action to restore your signature.

Windows (new profile or local folder not linked): Copy your backup into %APPDATA%\Microsoft\Signatures of the active Windows profile and restart Outlook.

Windows (files present but UI blank): Close Outlook, clear the Outlook cache, restart Windows, then sign in interactively. If that fails, run a profile repair.

macOS (signature files not loaded): Move the correct *.mailsignature files into the active Outlook profile container and restart Outlook.

OWA shows signature present, desktop doesn't: Copy the signature from OWA (Settings > Mail > Compose and reply) and paste it into the desktop signature editor.

Mobile blank: Paste the OWA signature into the mobile app Settings > Signature. If a device policy blocks this, contact IT.

SSO/MFA reauth or device re-enrollment: Sign out fully and sign back in interactively to refresh tokens. If a profile was recreated, restore local files into the new profile.

Exchange/tenant move or admin policy: Ask IT to confirm a mailbox move or roaming-signature policy change. If roaming was disabled, reapply the signature in OWA and distribute it centrally if needed.

Windows: ordered restore steps (diagnose then fix)

Direct answer: diagnose whether local signature files exist, back them up, then restore them into the active profile’s Signatures folder. Follow the steps in order.

1. Diagnose: Verify whether local signature files exist.

%APPDATA%\Microsoft\Signatures

2. Back up the folder now.

$src = "$env:APPDATA\Microsoft\Signatures"
$dst = "C:\Users\$env:USERNAME\OneDrive\Outlook-Signatures-Backup"
New-Item -ItemType Directory -Force -Path $dst
Copy-Item -Path $src\* -Destination $dst -Recurse -Force

3. If Outlook created a new profile after the password change, copy your backup into the active profile’s %APPDATA%\Microsoft\Signatures folder.

4. Start Outlook. Open File > Options > Mail > Signatures and confirm signatures appear.

If the folder is missing and you have no backup: check other C:\Users profiles for a Signatures folder, or copy the signature manually from OWA into the desktop editor.

If the UI still shows no signature after restoring files: close Outlook, clear the Outlook cache, sign out and back in, and then run a repair via Control Panel > Programs > Microsoft Office > Change > Quick Repair.

Expected result: signatures appear in File > Options > Mail > Signatures and in new messages. If not, escalate to IT because the profile or a policy may be blocking local signatures.

macOS: ordered restore steps

Direct answer: find and back up *.mailsignature files, move the correct files into the active profile container, then relaunch Outlook and confirm the signatures list.

1. Diagnose: Find existing signature files.

• In Finder choose Go > Go to Folder and enter ~/Library.
• Search for *.mailsignature and folders named Signatures under ~/Library/Group Containers or ~/Library/Application Support.

2. Back up any found files by copying them to the Desktop or another safe folder.

3. Move the correct *.mailsignature files into the active Outlook profile container you found.

4. Start Outlook for Mac and open Outlook > Preferences > Signatures to confirm the text appears.

If you cannot locate usable files: open OWA, copy the signature text, and recreate it in Outlook > Preferences > Signatures.

Expected result: signature entries appear in the Signatures pane and are added to new messages. If not, contact IT because a policy may block the client or the files may be incompatible.

OWA and mobile: quick restore and immediate workarounds

Direct answer: OWA often holds the mailbox-stored signature. Copy it there, then paste it into the desktop or mobile signature editor. That gives you an immediate working signature.

1. In a browser, sign in to OWA and go to Settings (gear) > View all Outlook settings > Mail > Compose and reply. If the signature is present, select all and copy it.

2. Paste into the desktop Outlook signature editor (File > Options > Mail > Signatures) or into Outlook mobile Settings > Signature.

Short-term workarounds if you need a signature immediately:

• Paste the copied signature into a new email and save it as a template or draft for reuse.
• Use a plain-text local signature in the client until full reauthentication occurs.

If a mobile app refuses to save it, a device or policy restriction is likely — check with IT.

Expected result: you can use the signature content in the client you pasted into immediately. If it won’t save, escalate to IT.

Verify the fix

Direct answer: compose and send a test email to confirm the signature appears in the client and in OWA. If the signature still shows only in OWA, you’ll need to escalate.

1. Compose a new email in the client you restored and confirm the expected signature appears automatically.

2. Send a test email to yourself and view it in OWA and the client to ensure formatting is preserved (HTML/RTF/plain text).

3. If signatures appear in OWA but not in any client after these steps, collect diagnostics and escalate to IT or Microsoft support.

Expected output: signature displays in the compose window and in sent messages. If not, gather the items listed below before opening a ticket.

Preventing future loss and simple backup recipes

Direct answer: back up local signature files before planned account or device changes. For organizations, use central signature management to avoid client-side sync problems.

Short-term personal backup (Windows): schedule a login copy of %APPDATA%\Microsoft\Signatures to your OneDrive folder.

$src = "$env:APPDATA\Microsoft\Signatures"
$dst = "C:\Users\$env:USERNAME\OneDrive\Outlook-Signatures-Backup"
New-Item -ItemType Directory -Force -Path $dst
Copy-Item -Path $src\* -Destination $dst -Recurse -Force

• For macOS, copy found *.mailsignature files to a persistent folder in iCloud Drive or another cloud location.
• For organizations, use a centralized signature management solution or Exchange transport rules to apply corporate signatures server-side; this removes dependence on local files.

When to back up: before password changes, device re-enrollment, or mailbox moves. If you edit signatures often, keep a weekly automated copy.

When to escalate and what to collect

Direct answer: escalate to IT when profiles were recreated, many users lost signatures, Intune or group policy applied, or you suspect a mailbox move. Escalate to Microsoft if the signature exists in OWA but won’t sync to any client after you try repairs.

Escalate to IT when:

• Profiles were recreated after a password change.
• Multiple users in your tenant lost signatures.
• Intune or group policy applied at the same time.
• You suspect a mailbox move or tenant-level change.

Escalate to Microsoft support when the signature is in OWA but won’t sync to any client after interactive sign-in, profile repair, and client repair.

Collect before you open a ticket:

• Screenshots: OWA signature settings and the desktop signature UI showing the mismatch.
• Exact local paths and directory listings for %APPDATA%\Microsoft\Signatures (Windows) or signature files in ~/Library (macOS).
• Time of the password change and any enrollment prompts that appeared.
• Outlook client version/build (Help > About Outlook) and whether Cached Exchange Mode is enabled.
• Any relevant error messages from Outlook’s activity center or sync logs.

Provide these items to speed diagnosis.

Conclusion

If you need the signature right away, copy it from OWA into the client or paste it from a local backup. If local files exist but the client doesn’t show them, restore the files into the active profile folder and sign in interactively. If profiles were recreated, policies applied, or the signature is in the mailbox but won’t sync to any client, collect the files, screenshots, and timestamps listed above and escalate to IT or Microsoft.