Applies to Exchange 2016, Exchange 2013, Exchange 2010 and Exchange Online (Office 365).
In corporate environments central management of email signatures is a must – you don’t want users messing up the company’s image by sending out emails stamped with notes in Comic Sans, lacking crucial contact info, etc.
So it’s a good thing that Microsoft Exchange platforms offer several means of controlling the email footer situation in your network. The most popular one is the Apply disclaimers feature available via Exchange transport rules, which I’ve talked about extensively on this blog (see respective guides for Exchange Online, 2016, 2013, 2010 and 2007).
Another way of deploying email signatures from one place across an Exchange organization, is using the Set-MailboxMessageConfiguration PowerShell cmdlet with the -SignatureHTML parameter.
This method allows you to populate the Email signature box in end-users’ Outlook Web App / Outlook on the Web clients with any type of HTML content: text, tables, images, links, etc.