Microsoft Lystavlen - the Online display board

Lystavlen is the danish word for 'the display board'. This blog is all about sharing the beauty of Microsoft Online Services

How to create auto signatures centrally in Office 365 Exchange Online

How to create auto signatures centrally in Office 365 Exchange Online

  • Comments 31
  • Likes

Many are asking if they can make use of centralized auto signatures in Exchange Online in Office 365. The answer is yes - and its done using Disclaimers.

To automatically apply disclaimers to e-mail messages, you use Transport Rules. You create Transport Rules in the Exchange Control Panel - just click Manage My Organization > Mail Control > Rules and start building the desired rule.

Clicking New will present you with a dialog in which you can specify that you want the new rule to fire on all messages and you want it to append a disclaimer to evey message.

Next up is specifying the appropriate text in the disclaimer. The disclaimer text can include HTML tags and you can add user attributes to disclaimers. For example, you can add DisplayName, FirstName, LastName, Department, and Company to create personalized signatures. Here is an example of a (very) basic disclaimer:


When the disclaimer is added to the message, the attribute names are replaced by the corresponding values from the sender's user account.

Testing the disclamer

Compose a message (with no signature to begin with - will be inserted by the transport rule)

The recipient sees the message with the signature inserted by the Transport Rule:

Here is more on how to build your own centralized auto signatures - Link

Bonus info: Loryan Stant (Office 365 MVP) elaborates a bit on the variables and an exception you can apply - link

  • The difference is a disclaimer always appends to the bottom of an email, if you're replying to an email you wont want it at the bottom of the email, you'll want it at the bottom of your addition to the email

  • Agree with Jim, using the disclaimer option will always append to the bottom of an email, which is fine when initially sending the email but should someone reply from within your organisation, their signature will append under your original one.  You could set up an exception to not appeand if RE: is in the subject field but this causes other issues.

    It seems strange that there isn't a global signature option.

  • Probably the easiest way is to take some unique text from the disclaimer and use that instead of the RE: suggestion. #justathought

  • Thanks Stephen, that's a good suggestion.  I might add a unique phrase to the signature and since it's html, i'll be able to hide it.  This could be a good workaround. Cheers

  • Stumbled upon this post a few days ago when I was looking for a signature tool for our E3 on Office 365. There is also a bunch of third party signature managers for composing and centrally adding sigantures for Office 365 and OWA. We're now trailing this one

  • Agree with all of these -- rather useless as a good signature tool because the sig alwasy ends up at the end.

    I do see ways that rule logic could be used to better manipulate...but M$ has broken that ability to do this!  They limit the total length of the rule so severely that creating a normal marketing signature along with needed logic rules is not possible.

  • One command is all you need - set-mailboxmessageconfiguration -identity <alias> -signaturehtml (get-content <path to html file>) -autoaddsignature $true

    Downside to this, it has to be done for each user. So, I created a CSV with all the variables (such as name, job title, telephone etc) and then ran a powershell script to echo the lines of html and varibles in a foreach loop to an html file ($_.alias.html) and then ran the above command (in the same loop). Happy to post if any one needs some help

    FYI, to replace a user signature, update the html file (and on csv file) and run the command/script again and it will be replaced.

    Signature automatically appears as it would do in outlook. This works for OWA and Outlook

    If you are doing this for Office 365, give 15 minutes (theoretically up to 48 hours) for changes to replicate across all Hub transport servers

    FYI, in Exchange 2013 (Office 365 Wave 15), you can also add -autoaddsignatureonmobile $true. Speaks for itself

    Hope that helps, it has worked wonders for me!

  • @Chris Howett - i would very mush like for you to post your solution.

    If you could do so, it would be a great help, thank you.

    BR David

  • Just FYI, I checked out the tird party tool from: and it inly works for OWA and Windows Outlook; not Mac and not Mobile.

  • Hello Chris,  It would be great if you would post you work around for the signatures in Powershell.  It is a little vague and I would love to try.



  • Hi Jesper,

    Thanks for your post.

    Please could you tell me what version/plan of 365 comes with the transport rules feature.

    This is my main requirement for sourcing a hosting solution, so need to know what version to purchase.

    If you could please also tell me if this adds the disclaimer to users using an email client (Outlook, Outlook for Mac, Mac mail etc..) not just when sending through webmail.

    Any help would be greatly appreciated.




    and Yes

  • @Chris Howett - i would very mush like for you to post your solution.

    If you could do so, it would be a great help, thank you.

  • Chris, we would apreciate very much if you could post the code.

    Thanks in advance.

  • I'll give Chris Howett's solution a try. I'll post it here if I manage to nail it. Wish me luck!  

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment