= A third party update to customer managed web servers may be causing connectivity issues when using the Outlook client to connect to Exchange Online =

Hello! I was wondering if anyone else has been troubleshooting this issue over the last few days. Anyone have any workarounds or things to share?
A third party update to customer managed web servers may be causing connectivity issues when using the Outlook client to connect to Exchange Online Details A limited subset of customers have reported issues connecting to the Exchange Online service. Upon investigation, engineers identified that customers reporting the issue had recently updated their web servers that host their root domain which inappropriately enabled Internet Message Access Protocol (IMAP) and Simple Mail Transfer Protocol (SMTP). This caused web servers to acknowledge auto-discover requests sent by the Outlook client subsequently preventing connectivity to the Exchange Online service

User Experience: Affected users are unable to connect to the Exchange Online service via the Outlook client. Outlook Web App (OWA) connectivity is not affected by this issue

Potential Workaround: Customers have reported that disabling IMAP and SMTP on the recently updated web servers remediates end-user impact by preventing the web server from acknowledging the auto-discover request

httpblogs.technet.com/b/kristinw/archive/2013/04/19/controlling-outlook-autodiscover-behavior.aspx
Might want to test with a local XML file to see if that is indeed the case


Odd I had this very same thing this week at a client. Only 1 user suddenly dropped connection, and when going into the account properties, Outlook over RPC was disabled. Easy fix, right? just enable outlook over rpc and be on your way. Every time I checked the box, and applied it, it would remove itself almost immediately after opening outlook. Still en easy fix, right? Just create a new new outlook profile. That's when I realized that Autodiscover wasn't working properly. When using the online exchange analyzer for Outlook over RPC, it failed at the autodiscover portion. I checked the CNAME/Autodiscover record and it was all good, pointing to autodiscover.outlook.com. I happened to notice the warning that you posted while I was logged on as the admin. The customer in question is using dexaweb and the host said they could not disable IMAP and SMTP since it was a shared hosting environment. How I finally got it working was to follow Miker2's instructions here: httpcommunity.spiceworks.com/how_to/32548-manually-configure-outlook-to-connect-to-office-365?page=2
The only thing I actually did that was effective from this was to set the logon to be anonymous. Once I did that, the manual setup worked. It's a short term solution to get them working. In the interim, I'd be interested to know if there is a true solution to this aside from moving web servers

== About Community ==
Members
Online