This KB article acknowledges that Outlook 2013 won't connect to Exchange using EAS (Exchange ActiveSync) for non-Hotmail accounts, i.e., a corporate Exchange server. There is also a similar six-year old question on the topic, as well as further discussion here.

Has the situation changed any for Outlook 2016? The reason to ask is that the "free" Windows 10 mail client does support EAS connections (the same was true for Windows 8/8.1 too), so I would think Outlook would as well. It seems rather odd that I should lose functionality when "upgrading" my Microsoft-provided email client.

(And, no, other options aren't possible, such as the much-preferred Outlook Anywhere feature; the only supported "off site" configuration is EAS--for mobile devices.)

I'm trying to get Microsoft to weigh in: Can't add non-Hotmail Exchange ActiveSync account in Outlook 2016 .

  • I highly doubt Outlook 2016 will revert back to using EAS for direct Exchange connections. The official answer is to tell your Exchange Admin to enable Outlook Anywhere. :) – Ƭᴇcʜιᴇ007 Sep 22 '15 at 19:40
  • 1) The Exchange Admin won't enable Outlook Anywhere; and, perhaps much more importantly, 2) it works with the out-of-the-box Windows 10 mail client. – Ðаn Sep 22 '15 at 19:41
  • I'm not sure why you think that just because Windows Mail App (a lesser client) works with EAS, that any other mail client should be able to do it. Outlook 2013 preview worked with EAS, and then when they released it they decided to remove support for it, as they didn't feel it offered enough for full Exchange/Outlook interoperability. Also, if your Exchange admin won't enable it, ask him how you're supposed to use Outlook from home, perhaps they have alternative means they can provide you (ie: VPN into work network, or perhaps OWA). – Ƭᴇcʜιᴇ007 Sep 22 '15 at 19:47
  • @Ƭᴇcʜιᴇ007 Outlook 2016 isn't just "any other mail client," it is (presumably) Microsoft's premier email client. I can get email off this Exchange server from home in one of two ways: 1) on an iPad, iPhone, etc.; or 2) use the Microsoft-provided mail client on Windows 8/8.1/10. – Ðаn Sep 22 '15 at 19:50
  • 1
    And Microsoft's "Premier" Mail client expects it to have a "Premier" connection to Exchange, which EAS can't supply. If you want Outlook to work from home with a corporate Exchange server, then you need to configure the Exchange server properly. If you can't do that, then you're pretty much SOL. But anyway, none of this has to do with your question which is "Will Outlook 2016 support EAS to an Exchange server", to which you've already received the answer. – Ƭᴇcʜιᴇ007 Sep 22 '15 at 19:55

The best "answer" on this is from Roady [MVP] on this Microsoft community question. He says

Don't expect that Outlook will connect to Exchange via EAS. In fact, EAS support in Outlook will most likely be abandoned once Outlook.com accounts have been migrated to Exchange Online.

The article New ways to get more done in Outlook.com is also interesting as it outlines the move to hosting outlook.com on Exchange servers.


Actually Outlook 2016 supports EAS just like the Outlook 2013 does. But in a some weird way: you can connect to EAS servers that are not Exchange Server (like Outlook.com).

I believe this situation will change with the Exchange 2016 that introduces a new EAS protocol version.

  • The KB article says the error is Log onto Exchange ActiveSync mail server (EAS): The server cannot be found. which is exactly what I see when I try to connect to a non-Hotmail EAS server. – Ðаn Sep 22 '15 at 19:39
  • 1
    Yep. This is what I said: it supports EAS servers other than Exchange. It looks like you're trying to connect to Exchange using EAS. – thims Sep 22 '15 at 19:50
  • This problem stil not fixed in Outlook 2016. However It works well in Outlook 2013. Don't spend your time to configure this. or if you found a solution, please post your method. – OfusJK Aug 8 '18 at 5:00

Not the answer you're looking for? Browse other questions tagged or ask your own question.