Resolving Outlook Signature Issues After Switching Accounts

If your Outlook signature disappeared, shows the wrong signature, or won’t edit after you switched accounts or profiles, the usual causes are: a different sending account/profile, missing local signature files, or a server/admin policy replacing or locking signatures. Run the quick triage to identify which cause applies, then follow the platform-specific steps (Windows, Mac, web, mobile) to restore or recreate the signature and set per-account defaults.

Quick triage — three checks to stop guessing

Start here to find which problem you actually have. Do these three checks before trying fixes so you don’t waste time.

• Check the sending account in a compose window.

1. Compose a new message and read the From: line.

1. If the wrong account is selected by default, change it and test whether the expected signature appears.

• Identify the Outlook client.

1. Note whether you’re using Outlook for Windows (classic Click-to-Run/MSO or Microsoft Store/AppX), Outlook for Mac, Outlook on the web, or Outlook mobile (iOS/Android).

• Look for signs of admin enforcement.

1. If the signature controls are disabled, settings revert after saving, or a corporate footer is added regardless of client choices, a server-side rule or management policy is likely in effect.

If the From: account is correct, you are on the same client as before, and you can edit the signature area, continue to the client-specific steps below. If any check fails, use the matching section: account/defaults, profile/files, or policy enforcement.

Before you start (applicability and safe checks)

Answer: This guide is for people who switched Outlook accounts or user profiles and now see missing, wrong, or locked signatures. Read the short checks before you change files or profiles.

• Scope: users who switched Outlook accounts or Windows/Mac profiles and have missing, wrong, or uneditable signatures.

• Permissions and access: you need read/write access to your current user profile. Get permission before accessing another user’s profile.

• Backups and restarts: back up signature folders before copying or replacing files. Restart Outlook after making changes.

• Versions and policies: Microsoft updates clients and admin controls. If a step depends on managed-policy behavior (Intune, Exchange Online), confirm details with your admin before broad changes.

Symptom section — what you see and when it happens

Answer: This section lists common symptom patterns and what they usually mean. Use it to pick the correct platform fix.

• Signature missing in compose windows: often local signature files were not moved when you switched profiles or the per-account signature is unset.

• Wrong signature appears: usually the message is being sent from a different account or a server-side signature is appended.

• Signature not editable or settings greyed-out: likely an admin policy, Exchange transport rule, or third-party signature manager is enforcing signatures.

• Images broken or HTML rendering poorly: caused by local file paths for images, unsupported HTML/CSS, or the recipient client stripping content.

If you see these symptoms, run the quick triage above and then use the platform-specific steps below.

If you use Outlook for Windows — fast fixes and profile recovery

Answer: For Outlook on Windows, check File > Options > Mail > Signatures and the local Signatures folder at C:\Users\<username>\AppData\Roaming\Microsoft\Signatures. Back up before you change anything.

1. Verify default signatures per account.

1. Open Outlook and choose File > Options > Mail > Signatures.

1. In the dialog, set the correct signature for New messages and Replies/forwards for each shown account.

Expected result: the signature appears on new messages and replies. If it doesn’t, continue.

2. Check the local signature files.

• Close Outlook.

1. Open File Explorer and go to the current Signatures path.

%APPDATA%\Microsoft\Signatures

1. If the folder is empty or missing your signature files (*.htm, *.rtf, *.txt and an images subfolder), look for the same folder under an old Windows user profile.

3. Recover signature files from an old profile.

1. Open File Explorer and navigate to the old profile path, for example:

C:\Users\OLDUSER\AppData\Roaming\Microsoft\Signatures

1. Copy all files and any images subfolder from the old Signatures folder into your current %APPDATA%\Microsoft\Signatures.

1. Start Outlook and verify File > Options > Mail > Signatures lists the signature names. If names are missing, open an existing .htm in a text editor, copy its HTML, then create a new signature in Outlook and paste.

Expected result: your HTML signature and images render correctly. If images are broken, they were probably linked to local paths — see the HTML/images section.

4. Special notes for Store (AppX) or Click-to-Run installs.

• The Signatures path is the same, but cached credentials or temporary profiles can cause Outlook to open under a different Windows account. Verify the Windows user account under Control Panel > User Accounts matches the folder you copied from.

5. Repair Outlook only if the client crashes or settings won’t save after restoring files.

1. Run Settings > Apps > Outlook > Modify > Quick Repair.

1. If Quick Repair fails, run Online Repair. Check with your admin before Online Repair on managed devices.

If none of the above restores the signature, a server-side rule may override client signatures — see the policy section.

If you use Outlook for Mac, Outlook on the web, or mobile — restores

Answer: Mac, web, and mobile have different storage and sync behavior. Follow these steps per platform to restore a signature or set a simple mobile signature.

Mac: restore signatures from your profile folder.

1. Quit Outlook for Mac.

1. In Finder go to the profile folder, for example:

~/Library/Group Containers/UBF8T346G9.Office/Outlook/Outlook 15 Profiles

1. Inside your profile folder look for a Signatures folder. If you find HTML or .mailsignature files, copy them into your current profile’s Signatures folder.

1. Open Outlook and recreate the signature in Outlook > Preferences > Signatures, then paste the HTML if you have it saved.

Expected result: signature appears in compose windows for the correct account.

Web (Outlook web): edit the mailbox signature.

1. In the web client open Settings > View all Outlook settings > Mail > Compose and reply.

1. Edit or paste your signature into the web editor and Save.

Expected result: the web signature attaches to messages sent from the web. If you can’t edit this area or the setting reverts, a server-side transport rule or third-party manager may be enforcing a footer.

Mobile (iOS/Android): use a simple per-account text signature.

• Outlook mobile has per-account signature settings under Settings > Signature. Mobile signatures are usually plain text and do not sync with desktop HTML.

• If a server-side signature exists, the server may append a footer after mobile send; that is expected for server-side rules.

• For images or rich HTML on mobile, host images on HTTPS URLs and check your company’s signature management policy.

How to set default signatures per account when multiple accounts exist

Answer: Set a default signature for each account in the client you use most. Verify the From: dropdown when composing so the correct signature attaches.

Windows (Outlook desktop):

1. Open Outlook and select File > Options > Mail > Signatures.

1. In Choose default signature pick the account from the Email account dropdown.

1. Set the signature for New messages and Replies/forwards.

1. Repeat for each account you use.

Mac:

1. Open Outlook > Preferences > Signatures.

1. Create or select a signature, then choose the default account in the Default Signatures area.

Web (web client):

1. The web signature is usually mailbox-global. Open Settings > View all Outlook settings > Mail > Compose and reply to edit it.

If you send from shared mailboxes or multiple mailboxes, confirm the From: dropdown when composing. If defaults don’t stick, a policy or transport rule may be overriding them — see the policy section.

Policy, admin overrides and when signatures aren’t editable

Answer: If signature controls are disabled or a footer still appears, an admin or transport rule likely enforces signatures. Collect the right evidence before contacting IT.

• Detect enforcement: controls greyed out, changes revert after save, or a corporate footer appears in received messages despite local removal.

• Possible admin tools:

• Exchange transport (mail flow) rules that add or replace signatures on send.
• Microsoft 365 / Exchange Online disclaimer/footer rules.
• Entra ID and Intune / Microsoft Endpoint Manager policies that lock client settings or push managed Outlook settings.
• Third-party signature services (for example, Exclaimer or CodeTwo) that inject signatures in transit.

What to collect before you contact IT:

• Screenshot of the affected client’s signature settings showing disabled controls.
• A copy of a sent message as received and the full headers from the received message.
• Screenshot of the From: dropdown in compose showing the account used.
• Notes about which devices are affected and whether the footer appears only on external recipients.

Tell IT whether the issue affects new messages, replies/forwards, or both, and whether it affects multiple devices. That helps them distinguish client defaults from transport-level injection.

How to fix HTML, images and branding assets that render incorrectly

Answer: Broken images and weird HTML usually come from local paths or unsupported styles. Replace local image paths with HTTPS links or let Outlook embed images.

1. Check image references in the signature .htm file.

1. Open the .htm in a text editor and search for src="file:/// or local drive paths.

1. Replace local paths with HTTPS-hosted image URLs.

1. If you cannot host images on HTTPS, re-add the images using the Outlook signature editor so Outlook embeds them.

1. Simplify the HTML: use table-based layout and inline styles, avoid external webfonts, complex CSS, and background images.

Expected result: images load and HTML renders consistently in most mail clients. If an image still fails, the receiving client or a gateway may be blocking external content.

How to back up and sync signatures to avoid recurrence

Answer: Back up signature files so you can restore them when you move machines or profiles. Copy the whole Signatures folder to cloud or a share.

• Windows desktop: copy the entire %APPDATA%\Microsoft\Signatures folder to OneDrive, a company file share, or a local archive.

• Mac: copy signature files from your Outlook profile folder to iCloud Drive or another archive.

• Web: copy the signature HTML from the web editor and save an HTML file to cloud storage.

Recovery recipe when switching machines or profiles:

1. Back up the source machine’s Signatures folder.

1. Copy the files to the target machine’s Signatures path before opening Outlook.

1. Open Outlook and set default signatures per account in File > Options > Mail > Signatures (Windows) or Preferences > Signatures (Mac).

If images break after copying, edit the .htm and replace local file paths with HTTPS URLs or re-add images through the signature editor so Outlook embeds them.

Verify — how to confirm the fix worked

Answer: Test by sending to multiple external recipients and inspect the received message and headers. That confirms client vs server behavior.

1. Send test messages to at least two external recipients to check consistency.

1. Inspect the received message for the full signature, image display, and HTML structure.

1. For suspected server-side injection, save the received message and view full headers; match the sending account in the headers to confirm which mailbox sent it.

Expected output: your chosen signature appears in compose windows and in received messages as intended. If a footer still shows or settings are locked, collect the screenshots and headers described earlier and escalate to IT.

Conclusion

If you followed the platform steps and either copied a working Signatures folder or set defaults per account, the signature should be restored. If settings remain locked or a server-injected footer persists, gather the screenshots, a sample received message with headers, and the client details above and forward them to your administrator.