Test it yourselves: Exchange Server 2016 Preview is now available!

Exchange logo (2013+) in blue, with the text Exchange after it (also blue) Reading Time: 2 minutes

Today the Microsoft Exchange Product Team released the public Preview of Exchange Server 2016! See the announcement on the EHLO blog.

Now everybody can install, investigate and test the latest iteration of Exchange Server, which is part of the Wave 16 of all Office applications (such as Office 2016, Skype for Business, SharePoint 2016 etc.). Some of these features are already present in Office 365, others will be added in time.

As this is a Preview release, don’t install this in a production environment (even though builds are being tested by TAP (Technology Adoption Program, see here for an explanation) customers in production environments, but these customers get specific support from Microsoft you will probably not. If you do, you might encounter unsolvable issues. So, be sure to fire up a lab environment and test this build in there.The requirements to install this Preview are:

Note that these requirements might change at the General Availability of Exchange Server 2016. They already have changed from what was announced during Ignite in Ross Smiths IV session (with a clear disclaimer that this might change). 

The bits can be downloaded here.

At the same time (well, it was publicly accessible a few hours before this release 😉 ), the Exchange Product team also published the preliminary technical documentation on TechNet.

You can find the TechNet documentation here.

If you look at the link, you'll see that the version part of the URL has (v=exchg.160) in it. I expect that corresponding articles from earlier versions of Exchange only differ in the version number and not article ID. But don't assume.

For more information about Exchange Server 2016, be sure to check out the sessions from Ignite 2015:



  • Hi Dave I am looking at your "Granting Mailbox Full Access via Groups and keeping the Automapping feature in Exchange 2010" article. Great job by the way. Is it possible to not remove group objects when the script is run only user objects? I want to put the source group that is supposed to have permissions to the mailbox in the Shared Mailbox permissions so I can use it to rerun the script in the future. That way I don't have to maintain a CVS I can auto-generate it at will. Thanks


Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.