Those who pay attention to details (unlike me often) might have noticed that Outlook 2013 rejoices in its ability to connect to email servers using ActiveSync (EAS). And then they ask the question why can’t they connect Outlook 2013 to Exchange via EAS? After all, if EAS is good enough for Hotmail (aka Outlook.com), why isn’t it good enough for Exchange? After all, EAS worked in the preview version of Outlook 2013, so the block was introduced between the preview and final version. The answer is that Exchange absolutely will support EAS connections, but not from Outlook. In fact, Exchange probably supports more EAS connections from different devices than any kind of other protocol, largely because of Microsoft’s success in licensing EAS to vendors such as Apple, Google, and just about every manufacturer of an Android smartphone (this page provides a good overview of the various EAS client implementations). But when it comes to Outlook connectivity, Exchange has a strong preference for MAPI, including MAPI when it’s securely wrapped in HTTP as in the case of Outlook Anywhere (aka RPC over HTTP), which is of course the predominant protocol for Outlook in Exchange 2013. Sure, it would be technically possible for Outlook 2013 to connect to Exchange using EAS, but Microsoft has blocked that option in code for very good reasons. First, EAS is not as rich a protocol as is MAPI....
More