Once upon a time in a land far, far away I wrote an article that told our action packed supportability story about the relationship of firewalls and Exchange servers. While the majority of response was positive to this purposefully lighthearted article (if you can’t enjoy your work why do it? :), there were other comments similar to the following:
“This isn’t official, it isn’t on TechNet!”
I’ll refer to the statement on the blog’s homepage:
“This is the official blog of the Exchange Server Product Group. All content here is considered authoritative and supported by Microsoft, unless otherwise specified.”
“It has a picture of cheese. I’m not using that as official guidance.”
You don’t like cheese? What did it do to you? Is it the smell? I’ll admit some of them do smell quite awful. I received a bruised toe from dropping a cheese wheel once.
“I don’t like spaghetti!”
Well that’s more for R5!
Terrible humor aside for a moment, we still recognized the need some of you had for something a bit more shall we say… polished. One of our wonderfully tenacious content developers, Chris Davis, took it upon himself to charge into battle and spent quite a bit of time tracking down everything required to put together this new article. In the end Chris has come up with a thorough TechNet article, without cheese, that we hope will provide you with everything required to stand up a perfectly healthy Exchange 2013 deployment all while staying within the support statement from the Exchange PG.
As a reminder we look at all Exchange servers across an entire organization’s deployment as one organic entity that rely on each other for proper function. Microsoft still does not support configurations when Exchange servers have network port restrictions that interfere with or alter communications with other Exchange servers, Active Directory servers, or Lync servers, as the new article states up front in much more clear wordage than before, and because of this the document focuses on client connectivity and mail flow into and out of the Exchange organization.
We hope the new article is put to good use and welcome commentary if there are any scenarios you feel we left out.
Senior Program Manager
Office 365 Customer Experience