Perhaps you already know what works for you when it comes to email signatures in your company. But do you know what will definitely NOT work, while you are persistently trying to achieve it? This article will give you some insight into the Exchange Server 2013 and 2016 limitations related to email signature management in your organization.
Note: For the purpose of this article, I assume that your company uses Microsoft Exchange Server 2013 or 2016 that controls internal and external email flow. The second assumption is that you create an email signature directly on the server side (not within an email client e.g. Microsoft Outlook).
Recently the world of Exchange was on the edge of their seats waiting for Exchange 2016 to come out. Now, those who already had some time to play with it must have noticed that Exchange 2016 brings some interesting innovations. One of the changes is related to OWA as well, which is now replaced with a brand new and shiny Outlook on the Web that brings some new features to provide you with even better experience.
If you haven’t had a chance to set up a new email signature in your Outlook on the Web yet, just follow the steps below to learn more.
Note: Now, by signing in to any Microsoft email account, you are actually signing in to Outlook on the Web.
Possibly the biggest surprise brought about by the release of Exchange 2016 is… how similar it is to Exchange 2013. In fact, in terms of email signature management it’s pretty much identical (if you’re familiar with the 2013 version of Microsoft’s email server, you’ll see what I mean). However, many of you may have never had the opportunity to poke around Exchange 2013, so let’s get to work: