How to set up different email signatures for a shared mailbox and user mailbox in Office 365?

Different signatures added to emails sent from shared and user mailboxes

It is a common and widely-spread practice in business email communications to differentiate signatures depending on the sender. Companies very often want to put different contact details, banners and even change the entire layout to indicate that the message arrives from a general mailbox like sales@ or from an individual like j.doe@.

There are three ways to achieve this: creating two separate signatures in Outlook, setting up mail flow rules on the server side or using CodeTwo Email Signatures 365 – an email signature management solution.

Method 1 – Use Outlook 2021, 2019 or 2016

For this, you need to add a shared mailbox to your Outlook as a second account. If you already have access to your company shared mailbox in Outlook, the steps are rather simple:

  1. In Outlook, go to File > Options > Mail > Compose messagesSignatures.
    Outlook for Microsoft 365
  2. In the Signatures and Stationery window, on the E-mail Signature tab, click New.
  3. Type the name for your shared mailbox signature and click OK.
  4. Use formatting tools available in the Edit signature section to create the signature. You can also prepare the signature in a signature generator and then just copy/paste it into your Outlook.
  5. In the Choose default signature section, select the shared mailbox and define whether the email signature should automatically appear in new messages or replies and forwards. Click OK to apply the changes.

    choose default shared mailbox signature
  6. Repeat the steps to set up another signature, this time for your personal account.

Plus points:

  • No additional costs.
  • Relatively easy to set up.

Minus points:

  • Every time you write a new email you need to remember to manually select the shared mailbox in the From field and select the shared mailbox’s signature back and forth.
  • Limited formatting tools and options in the Outlook signature editor.
  • Relatively difficult to create advanced signatures (because of limited editor functionalities).

Method 2 – Server-based rules in Microsoft 365/Exchange Online

In this method, you can set up user and shared mailbox signatures directly on the server, not in email clients:

  1. Open the Exchange admin center.
  2. Navigate to Mail flow > Rules.
  3. Click Add a rule and select Apply disclaimers.
  4. Set up the rule for a shared mailbox:
    a. In the Apply this rule if section, select your shared mailbox.
    b. In the Do the following section, enter the disclaimer text and select one of the fall back actions.

    Note: If you want your signature to look nice, you will need to wrap it in HTML code. If you don’t feel very comfortable with HTML coding, you can get some help from this signature generator. It’s free and allows you to convert one of the predefined email signatures (filled in with data you provided) to HTML, which you can later copy/paste into your mail flow rule.

    Server signature
  5. If you don’t want the signature to show up on replies, set up an exception to the rule in the Except if section (for example, The subject or body > subject includes any of these words). In the pane that opens, type RE:, then click Add and Save.
  6. Complete the remaining steps of the rule creation wizard. Take a final look at the rule settings, and if everything is set up correctly, click Finish.
  7. Once created, the mail flow rule is disabled by default. Select it from the rules list and use the toggle to enable the rule.
    Enabling the new mail flow rule.
  8. Repeat all the above steps to create a signature for a user mailbox.

    Note: Keep in mind that a user sending emails from a shared mailbox will get either the shared mailbox or their own signature depending on what delegate rights are assigned to the user. If the user has the Send as rights to a shared mailbox, emails will be stamped with a signature created for the shared mailbox. If the user has the Send on behalf of rights enabled, the signature specified for a user mailbox will be added.

Plus points:

  • The rule is handled on the server side so there is no need to manipulate signatures on the client side.
  • You can create both user and shared mailbox signatures from one place.

Minus points:

  • You need to have at least the basic HTML knowledge to code fairly professional signatures.
  • In replies, the signature will always appear at the very end of the conversation thread.

Method 3 – CodeTwo Email Signatures 365

In this method, you need CodeTwo Email Signatures 365 – a third party signature manager for Office 365, which allows you to control email signatures on the server’s or client’s side. To set up automatic signatures for shared mailboxes and user mailboxes, follow the steps below:

Note: To go with this method, you need a valid subscription of CodeTwo Email Signatures 365. If this solution is new to you, you can sign up for a free 14-trial here.

  1. Sign in to the signature management app.
  2. Add a new server-side rule and name it.
    Creating a server-side signature
  3. In the Senders step, use the Add button, click Selected senders and select the shared mailbox address.
    Signature management app - selecting senders
  4. Optionally, you can use the Recipients step if you want to add the signature to emails sent to selected recipients only, as shown on the screen below. You can also go to the Keywords step to set up specific keywords that will trigger or suppress this rule.
    Signature management app - selecting recipients
  5. Configure the settings in the Scheduler and Logic steps according to your needs.
  6. Finally, go to the Design step and click Edit signature to create your shared mailbox signature. You can either choose one of the templates available in the signature template library and adjust it to your needs or create your email signature from scratch in program’s signature template editor.
    Signature management app - editing the signature
  7. Once everything is set up correctly, click Save & Publish to save your changes and apply the rule in your organization.
    Signature management app - publishing the signature
  8. Repeat the procedure to set up the signature for a user mailbox.

Now all emails sent from the shared mailbox will be stamped with either shared or user mailbox signature, depending on the delegate rights of the sender.

Top benefits:

  • Set up and forget. Once configured, signatures are added automatically to emails.
  • Users don’t have to switch between accounts to send emails with a proper signature.
  • Each signature lands right under the reply, not at the bottom of an email conversation.
  • You can control all company signatures from one place.
  • Use graphical editor to create HTML and Plain Text signatures. No HTML knowledge required.
  • And many more

Downsides:

  • You need to buy a subscription to be able to use this solution in your organization. For some first-hand experience, there is an option to try the solution for 14 days at no cost.

For more details on adding signatures to Microsoft 365 shared mailboxes, see this article.

Useful links:

Tools for Exchange Server

Recommended articles

How to migrate from Exchange Server 2016/2019 to Microsoft 365

How to migrate from Exchange Server 2016/2019 to Microsoft 365

Migrating Exchange data to the cloud is not rocket science – explore your options and launch the migration stress-free. As you may already know, Exchange Server 2016 and 2019 have reached end of life and are no longer officially supported by Microsoft. If your organization still uses either of these platforms to manage email, contacts, calendars, and tasks, keep in mind that: Your environment may become vulnerable to newly discovered security threats – Microsoft will no longer provide security updates for Exchange 2016 and 2019 (unless you’ve enrolled in the Extended Security Update program, which ends in October 2026). Your emails may get blocked – Microsoft has started to throttle and block emails sent from unsupported Exchange Server versions to Exchange Online (as I covered in this article). That said, migrating to a supported platform is now the only viable long-term option for keeping your organization’s email environment secure, supported, and fully operational. If your organization wants or needs to keep things on‑premises (and continue using Microsoft’s solutions for that), upgrading to Exchange Server Subscription Edition (SE) is the only path forward. But given Microsoft’s clear preference for its cloud services – evident in the faster rollout of new features and the many security capabilities available exclusively in Microsoft 365 (Office 365) – now is a great time to leave your on‑prem environment behind and migrate to Exchange Online as part of Microsoft 365. While switching over to a new platform might seem like a rough ride, I’ll show you some easy ways to follow when migrating mailboxes from Exchange Server 2016/2019 to Microsoft 365. How to prepare for email migration to Microsoft 365 Before you start the migration process, you need to make sure your environment is ready for the move. For this purpose, you can use this guide in the Microsoft 365 admin center – it will help you connect your organization to Microsoft 365 and integrate your existing user accounts with Microsoft Entra ID. Microsoft also recommends completing the steps below: Set up an SPF record to determine valid email sources for your organization’s Microsoft 365 domain. Set up the Exchange Online Protection service as a means of protection against spam and malware. If you’re behind on updates, make sure to install the latest Cumulative Update (CU). And here is my quick, less obvious Microsoft 365 migration checklist: Verify if your software will work in Microsoft 365 (especially when it comes to server software). Microsoft 365 migration might be the time you learn that there is crucial legacy software that half the company uses and which is hard to replace. Encourage the whole company to clean up projects. It’s much easier to do this before the migration and start fresh. Gather as much information about your on‑premises environment as possible. For example, you might need to recreate access roles and permissions from scratch in the cloud or set up mail flow rules. Without prior research, it will be much more difficult. Verify if you need to migrate service accounts. There can be a lot of them on‑premises and in most cases, you won’t need them after the move. Review mailbox size limits in Exchange Online before migration to see which licenses you’ll need and whic
How to connect and remotely manage Microsoft 365 with PowerShell

How to connect and remotely manage Microsoft 365 with PowerShell

Microsoft 365 web interface was designed to make it easier to manage your tenant right down to its administrative bowels. On the one hand it really is quick and simple to navigate, on the other it definitely lacks some advanced configuration options so loved by sysadmins. Luckily there is the mighty PowerShell coming to the rescue! You should already know its potential, which can also be utilized in Microsoft 365. Find out how.
New-ComplianceSearch: how to use the newer version of Search-Mailbox

New-ComplianceSearch: how to use the newer version of Search-Mailbox

Microsoft retired the Search-Mailbox cmdlet – now what? Discover how to use New-ComplianceSearch, its key advantages and how to make the switch seamlessly.

Comments

  1. Hi, I did like proposed in method 1. But my issue is. We have an email contact@blabla.

    Configured on 4 different computers with outlook. And we want all to have a specific signature for this email for each of our accounts. issue is that when a colleagues change the default signature with his own signature it is changing for the other one also. is it possible to have for the same email, different signature?

  2. what works is configuring the shared mailbox permission with automap set to $false.
    This way you can add the shared mailbox as a separate mailbox into the outlook profile which also you to set a specific signature for it.

    When the shared mailbox is automapped , the signature settings of the primary mailbox are also set on the automapped mailbox which typically isn’t what the user needs.

    • avatar
      Adam the 32-bit Aardvark says:

      Thanks for the comment! Setting up permissions and automapping to false is a seperate subject, which is described in detail in this article.

    • avatar
      Adam the 32-bit Aardvark says:

      Do you have full-access permissions to the shared mailbox? Have you added the shared mailbox to your Outlook profile?
      If it’s a “yes” in both cases, then it looks like a bug.

  3. For Office 365 it appears that you have to log in to your account. A shared email (that is not licensed) does not have an accessible password. Is there a way to get around this?

    • avatar
      Adam the 32-bit Aardvark says:

      In Outlook go to File > Account Settings > Account Settings
      Then, double-click your account, go to More Settings > Advanced > Add and type in the shared mailbox address there.

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

*

CodeTwo sp. z o.o. sp. k. is a controller of your personal data.
See our Privacy Policy to learn more.