How to Change an Outlook Signature by Surface, Account, and Message Type

Start with the symptom, not the menu

An Outlook signature problem usually belongs to one of three places: the saved signature content, the message-type assignment, or the final message that Outlook or Exchange produces. Editing the text fixes only the first place. In classic Outlook, you choose a signature for new messages separately from the signature for replies and forwards, and (none) disables automatic insertion for either message type. Exchange transport rules can also apply conditions and exceptions to messages, including rules based on external recipients or matching text in a subject or body.

Your first task is to identify the symptom before opening a settings screen. If the name, title, phone number, link, or formatting is wrong everywhere, edit the saved signature. If the content is correct in one message type but missing in another, inspect the defaults for new messages and replies or forwards. If the draft looks right but the delivered message differs, investigate the selected account and any Exchange-side rule. That order keeps you from repeatedly changing content when the actual problem is assignment or rendering.

Use the workflow in this guide as a diagnostic sequence: identify the Outlook surface, edit the existing signature, assign it to the message types you need, and test each relevant message context. Stop treating the result as a local editing problem when those checks pass but the final message still changes.

Overview

Changing an Outlook signature correctly requires four separate checks. First, identify whether you are using classic Outlook, Outlook on the web, Outlook for Mac, new Outlook, or Outlook mobile. Second, select the existing signature and edit its saved content. Third, choose where it should appear: new messages, replies and forwards, or both where those controls are available. Fourth, compose the relevant message types and inspect the rendered result. Classic Outlook has separate defaults for new messages and replies or forwards. Outlook on the web uses separate options for those message types, while Outlook for Mac sets defaults separately for each account. Exchange transport rules are a separate control point that can apply conditions and exceptions to messages.

Keep the sequence simple:

1. Identify the surface. Use the instructions for the Outlook experience open on your screen.
2. Edit the saved content. Change the existing signature rather than assuming its assignment will change automatically.
3. Set message-type defaults. Check new messages and replies or forwards independently.
4. Check the account. Confirm the account in the From field when several accounts, delegate access, or a shared mailbox are involved.
5. Test the result. Compose a new message and, where the client exposes the control, a reply or forward.
6. Escalate the control point. If the local draft is correct but the resulting message differs, investigate Exchange-side behavior.

Choose the Outlook surface before changing anything

The Outlook surface determines which signature path you should use. Before editing anything, identify whether the message window is in classic Outlook for Windows, Outlook on the web, Outlook for Mac, new Outlook for Windows, or Outlook mobile. The available paths differ: web Outlook reaches signature settings through Settings, Options, Mail, and Email signature under Layout; Outlook for Mac places signatures under Mail > Signatures; and the documented account-change behavior covers web Outlook, new and classic Outlook on Windows, Mac, and mobile in message compose mode.

Do not choose a path based only on the operating system. A Windows computer can run more than one Outlook experience, and the same account can be used on a computer and a phone with different controls. Look at the application or browser surface where you will send the message, then stay in that surface while you edit and test. Your goal is not to make one setting screen look familiar; it is to change the signature that the actual sending surface will use.

Use these routing questions before you begin:

• Are you working in a browser? Follow the web Outlook path.
• Are you working in Outlook for Mac? Use Mail > Signatures, then select the account.
• Are you working in classic Outlook for Windows? Use the classic signature editor and its separate message-type defaults.
• Are you working in new Outlook or on a phone? Treat the available signature controls as version-sensitive and verify the result in that client rather than copying classic menu names.

Once you have identified the surface, make the edit there and test there.

Write down the surface before you change anything: classic Outlook for Windows, new Outlook, web Outlook, Mac, or mobile. Add the device if you are troubleshooting a difference between locations. This simple record prevents you from applying a desktop result to a browser or phone without testing the actual sending surface.

Separate editing the signature from assigning it

The saved signature and its message-type assignment are separate settings. In classic Outlook, Select signature to edit identifies the saved signature, while Edit signature changes its content. The same classic Outlook settings then let you choose a signature for new messages and a separate signature for replies and forwards. Web Outlook likewise separates the signature text box from the options that automatically include the signature on new messages and on replies or forwards.

Suppose the existing signature contains the correct contact details but appears only when you start a new message. Editing the contact details again will not address that symptom. Check the replies-and-forwards assignment instead. Conversely, if the signature appears in both message types but contains an outdated title, edit the saved content first and then retest both message types.

Before saving, ask two different questions:

1. What should the signature say? This is the content decision.
2. Where should Outlook insert it automatically? This is the assignment decision.

Answer both questions explicitly. A correct signature with the wrong assignment still produces the wrong result for your workflow.

Do not use the appearance of a signature in one draft as proof that its content and assignment are both correct. Check the saved text separately from the message type in which it appears. That distinction gives you a clear next action when only one part of the result is wrong.

Edit the existing signature in classic Outlook

Classic Outlook edits an existing signature through two linked areas: Select signature to edit and Edit signature. Open the signature settings, choose the saved signature you want to change, and place the cursor in the editing area. Change only the content that needs correction, such as a name, role, phone number, address, link, or outdated line. The editor supports changes to font, font color, size, and text alignment.

Work from the visible signature rather than rebuilding it by default. Preserve the parts that are already correct, then check the result as a complete block: name, role, contact details, links, spacing, and any image that belongs in the signature. If you paste formatted text, inspect the editor after pasting because the saved appearance is the part that will be carried into a new message.

The editor changes the signature that you selected; it does not, by itself, decide whether that signature appears in new messages or in replies and forwards. After the content looks right, move to the default settings for each message type. Treat that as a second task rather than assuming the edited signature is automatically assigned everywhere.

Before leaving the editor, compare the saved block with the change you intended to make. Check spelling, links, line breaks, and formatting while the signature is still visible in its editing area. Then record the signature name so you can select the same saved item in the message-type defaults.

Assign classic Outlook defaults by message type

Classic Outlook uses separate choices for New messages and Replies/forwards. Select the edited signature in the New messages drop-down if you want automatic insertion when you start a new message. Select a signature separately in Replies/forwards if you want automatic insertion in those conversations. Choose (none) for either message type when you do not want automatic insertion there.

Make the assignment from the message behavior you actually need. If your change is intended for outbound messages but not ongoing threads, set the new-message choice and leave replies or forwards at (none). If the same signature should appear in both contexts, select it in both places. If different signatures are available, do not assume that editing one changes the other; choose the required saved signature in each drop-down.

Record the intended result before you close the settings: new message—signature name; reply or forward—signature name or (none). That small check gives you a direct test later. It also separates a wrong assignment from a failed content edit when the message does not look as expected.

A message-type default controls automatic insertion; it does not replace the need to inspect the finished draft. If you intentionally choose (none), verify that the signature is absent in that context. If you choose a saved signature, verify that the inserted block is the one you edited.

Save classic Outlook changes with the open-draft exception in mind

Classic Outlook saves the signature settings when you choose OK, but an already-open message is a separate case. A newly created signature is not automatically added to the message that was already open, even when the new-message default was selected. Add the signature manually to that existing draft if you need it there.

Use a future message to test the automatic setting. Close or set aside the old draft, start a new message, and check whether the selected new-message signature appears. Then start a reply or forward if that message type is configured. A missing signature in the old draft does not, by itself, show that the saved default failed.

Treat the open-draft exception as a test condition, not as a reason to repeat the edit. If the signature appears in a newly created message but not in the earlier draft, the saved setting is behaving as described. Add the signature manually to that earlier draft and continue testing with newly composed messages.

Use this order after selecting OK:

1. Keep the earlier draft separate from the test.
2. Open a new message.
3. Check the new-message signature.
4. Open a reply or forward if that default is enabled.
5. Add the signature manually to the earlier draft only if you still need it there.

This prevents an old draft from producing a false failure.

Use the web signature control for web Outlook

Web Outlook reaches signature settings through Settings, Options, Mail, and Email signature under Layout. Open that path in the browser surface where you send mail. The signature editor is the text box in the email-signature settings, so change the existing signature there rather than editing a local desktop copy.

Replace or correct the outdated content in the web editor, then select the automatic-inclusion options that match your intended use. Web Outlook provides separate choices for new messages and for messages you forward or reply to. Select the new-message option, the replies-and-forwards option, or both. If neither message type should receive the signature automatically, leave both options unselected.

Choose Save after editing. Web Outlook applies the signature to the message types selected in the settings. Test the result in the browser by composing the relevant message type; do not use a desktop draft as the only check for a web change.

If the browser offers separate controls for new messages and replies or forwards, treat each as its own setting. Save after making the content and inclusion choices, then open the message type that matters to you. Check the account and the inserted text before sending.

Set web Outlook inclusion separately

Web Outlook separates automatic insertion for new messages from automatic insertion for replies and forwards. Select the option next to Automatically include my signature on new messages I compose when new messages should receive the signature. Select the option for messages you forward or reply to when those contexts should receive it. Select both when both contexts require the same saved signature.

Use the symptom to choose the next check. A signature missing only from replies points to the replies-and-forwards option, while a signature missing from new messages points to the new-message option. A signature that appears in both places but contains outdated text points back to the editor. This distinction keeps you from changing an inclusion setting when the saved content is the actual problem.

Select Save, then open a new message and inspect the signature. If replies or forwards are enabled, open one of those message types as a second test. Confirm the content and the message context separately; seeing the signature in one context does not establish that the other option is enabled.

If the signature is correct in a new message but absent in a reply, change the reply-and-forward option rather than the signature text. If it is absent in both contexts, check that the edit was saved and that you are testing in the same browser surface where you made the change.

Handle Outlook for Mac account by account

Outlook for Mac places signature settings under Mail > Signatures. Open that area, select the account whose messages need the change, and set the defaults for new messages and for replies or forwards. The account selection is part of the procedure, not an optional detail.

If Outlook for Mac contains multiple accounts, set the default signature separately for each account. Start with the account that sends the message you are troubleshooting, edit or select the correct signature, and assign its new-message and replies-or-forwards defaults. Repeat the check for another account only when that account also needs the change.

Compose a new message from the account you changed and inspect the inserted signature. Then test a reply or forward if its default is configured. If the expected signature is absent, check the account shown in the From field before changing the content again. A correct setting for one account does not establish the setting for another.

For each Mac account, record three choices: the signature selected for new messages, the signature selected for replies or forwards, and the result in a test draft. This makes an account-specific mismatch easier to separate from a problem with the saved signature itself.

Treat new Outlook and mobile as version-sensitive paths

New Outlook and Outlook mobile need a verification-first approach because the available menu path can vary by client. The documented account-change event is supported while composing a message, and it is the only one of the two documented account-change events supported on web Outlook, new and classic Outlook on Windows, and mobile. That event detail does not supply one complete signature-settings procedure for every client.

Open the signature settings exposed by the client you are using, identify the existing signature, and edit its content there. Look for separate controls for new messages and replies or forwards where the client provides them. Avoid copying the classic Outlook route into new Outlook or copying a desktop route into the phone app merely because the account is the same.

Compose a new message in the same client after saving the change. If the client exposes a reply or forward setting, test that context too. Check the selected account and the final signature text in each draft. When the client does not expose a particular control, treat that as a boundary and verify the message type that the client does support rather than assuming the missing control has the same behavior as classic Outlook.

For new Outlook or mobile, record the exact settings labels shown in your client instead of relying on a different Outlook surface. Note whether you changed the signature content, enabled automatic insertion for a message type, and tested the same account that will send the message. Use that record when the result differs between clients.

Check the account behind the signature

The account in the From field can change which signature behavior you see. The documented account-change behavior applies to Exchange accounts, and switching to a non-Exchange account can clear the signature set by the previously selected account. Check the account after opening a draft and again after changing the From selection.

Delegate and shared-mailbox scenarios also need a surface check. The documented account-change events support those scenarios on web Outlook, new and classic Outlook on Windows, and Mac, but not on Outlook mobile. If you are working from a shared mailbox or delegate account, run the test on a supported surface before treating a missing signature as a failed edit.

Use this account-focused sequence:

1. Start a new message in the Outlook surface you normally use.
2. Record the account shown in From before changing it.
3. Check whether the expected signature appears.
4. Change the From account only if that is part of the message you need to send.
5. Check the signature again after the account change.
6. Repeat the test with a shared mailbox or delegate context only when that is the actual sending context.

If changing the account clears the signature, restore the intended account and inspect its signature assignment rather than editing the previously selected account's content repeatedly. If the selected account is non-Exchange, the documented account-change behavior does not support assuming that the prior account's signature will remain.

Account for device-local storage

A signature created on one device may be stored locally on that device and may not be available when you use Outlook on another device. That possibility explains why an edit that appears successful on a desktop may not appear on a phone or another computer. Treat the device and Outlook surface as part of the test conditions.

When you need the signature on more than one device, test each device where the signature will be used. On every device, check the saved content, the account in the From field, and the message-type assignment that the client exposes. Do not use a successful desktop draft as proof that the mobile client has the same saved signature.

Record the device and surface alongside the result: for example, desktop classic Outlook, browser web Outlook, Mac, or mobile. That record turns a vague report such as the signature disappeared into a useful troubleshooting description. It also tells you whether the problem follows the account, the device, or the Outlook surface.

If the signature works on one device but not another, repeat the content and message-type checks on the device that fails. Do not assume that moving the same account to another client carries over a locally stored signature. Treat each device result as a separate observation until the same signature is visible in the required sending surfaces.

Run a two-message verification

A two-message test separates new-message behavior from reply-and-forward behavior. Classic Outlook chooses those defaults separately, web Outlook provides separate automatic-inclusion options, and Outlook for Mac sets the defaults separately for each account and message context. Test both contexts when both are part of your intended use.

Start with a new message in the surface and account you just configured. Check these points before sending:

• The From account is the one you intended.
• The signature appears if new-message insertion is enabled.
• The edited name, role, contact details, links, and formatting are correct.
• The signature is not present when you deliberately selected (none) or disabled new-message insertion.

Close the draft or leave it unsent after recording the result.

Open a reply or forward as the second test when that message type is configured. Check the same account and content details, then compare the result with the new-message test. If the new message passes but the reply does not, inspect the replies-and-forwards assignment. If both drafts pass but a received or sent message differs later, move to the Exchange-side check instead of changing the local signature again.

A completed test has a clear result for each message type: present with the expected content, absent by design, or different from the expected result. Keep the three cases separate. They point to different next actions.

Capture the result in a short table or note with these fields:

• Outlook surface and device
• Account in the From field
• Message type
• Expected signature and insertion setting
• Signature actually shown in the draft
• Difference, if any, after sending or receiving

This record gives you a usable stopping point and makes the next control point clear.

Distinguish local failure from Exchange-side behavior

A local signature setting is not the only possible control point. If the draft shows the expected signature, the selected account is correct, and the new-message and reply or forward tests pass, but the resulting message differs, stop repeating the local edit. Compare the draft with the sent or received message and note exactly what changed.

Exchange transport rules can apply conditions and exceptions to messages. The documented examples include conditions involving external recipients and exceptions based on matching text in the subject or body. Those rules are therefore a possible explanation when the final message changes according to recipient, subject, body text, or another rule condition.

Use the message difference to choose the investigation path:

• The draft is already wrong: return to the saved signature, assignment, account, device, or Outlook surface.
• The draft is right but the received message is different for external recipients: ask the Exchange administrator whether a transport rule applies to that recipient condition.
• The draft is right but a matching phrase changes the result: ask whether a rule uses subject or body text as a condition or exception.
• The behavior appears only in a shared-mailbox or delegate workflow: check the supported surface and account context before comparing local settings.

Give the administrator the Outlook surface, device, account, message type, recipient context, and observed difference. That information identifies the control point without requiring repeated signature edits.

Do not treat a transport rule as proof that the local signature is wrong, and do not treat a correct local draft as proof that the final message will remain unchanged. Keep those observations separate: local composition shows what Outlook inserted, while Exchange-side conditions may affect how a message is handled afterward.

Once the local draft passes and the difference appears only after sending or receiving, stop changing the signature content. Bring the recorded surface, account, message type, recipient context, and exact difference to the Exchange administrator. If the draft itself fails, continue with the local checks instead.

Use a stopping rule for unsupported or controlled environments

Your local Outlook change is complete when the edited content, message-type assignment, selected account, device, and final draft all match the intended result. If the signature is stored locally, another device may not have it. If the account changes, the documented Exchange account behavior can clear the signature set by the previous account. If the draft is correct but the resulting message changes, Exchange transport rules may be applying conditions or exceptions.

Use a stopping rule instead of continuing to edit indefinitely. If the new-message and reply-or-forward tests pass, stop the local troubleshooting. If they fail, document the Outlook surface, device, account, message type, selected default, and exact rendered result before making another change. If the issue appears only after sending or only under a recipient or message-text condition, take that record to the person who manages the Exchange configuration.

When your team needs a managed branded signature workflow beyond changing one Outlook signature locally, use the configured next step.

What should you check when the changed signature does not appear?

Why is an Outlook signature available on one device but missing on another?

A signature created on one device may be stored locally and unavailable on another Outlook surface. Repeat the content, account, and message-type checks on the device that fails instead of assuming the desktop setting transferred to web Outlook, Mac, or mobile.

What should be checked when an Outlook signature changes after the account is switched?

Check the account shown in the From field before and after switching. The documented account-change behavior applies to Exchange accounts, and switching to a non-Exchange account can clear the signature associated with the previously selected account. Delegate and shared-mailbox account-change scenarios are documented for web Outlook, Windows new and classic Outlook, and Mac, but not Outlook mobile.

What does it mean when the signature looks correct in the draft but changes in the delivered message?

The local signature settings may already be correct. Compare the draft with the sent or received message, then ask the Exchange administrator whether a transport rule applies based on the recipient, subject, body text, or another condition. Avoid repeatedly editing the local signature until the server-side behavior has been checked.