), for either product, 'Oh, and if you 'upgrade' to 'Outlook 2016' you won't be able to talk to your 'Exchange Server 2013' any more'.Īnd it's not just via autodiscover (which worked perfectly with 'Outlook 2013' as well. So what exactly do you expect customers to do now? Doesn't say anywhere in the release notes (that I can find, We cannot get 'Outlook 2016' to talk to (on-premise) 'Exchange Server 2013'. Now fix it.įine, but if you were (as we are) using 'Outlook 2013' to talk to 'Exchange Server 2013' and it all works, now after 'upgrading' to 'Outlook 2016' it doesn't, how does that become a customer problem? Should, or should not, be trying to use the EAS protocol, you did. Now, can someone actually report this back to the appropriate team and get it fixed? It is simply not acceptable for your own products to suddenly decide they're not going to talk to each-other. Posters should not be allowed to mark their own posts as the answer. It's not the answer that's incredibly arrogant and just makes you a laughing stock. I.e., yet again, you've broken things on upgrades, which only involve interoperability between your own products! Cheez, do you people seriously not have aĪnd please don't just post something and automatically mark it as the answer. In my case in particular, this worked fine under 'Outlook 2013' and broke as soon as I 'upgraded' (not.

The OP, and I'm sure many other people (such as myself), are having this problem with 'OutlookĢ01 6'.

The KB article you reference applies to 'Outlook 2013'.

How to connect outlook 2016 to exchange