en en en en en en en en en en en en en en en en en sv en en en en es en en en en it sv en en en en en en en en en en en en en en ca en en en en en ne en en en en en en fr en en sv en it en en en en es en ru en en en en en en en en en en en en fr en en en en en en fr en en it en th en en en en vi en en en en it en en en en en
Microsoft Office 365 + On-premise Exchange Server Connectivity : Autodiscover not working | Euclid Networks
info@euclidnet.com | 404.593.0083 | QuickSupport
January 21, 2021by Euclid Networks in Uncategorized
After migrating an e-mail account to Microsoft 365, or setting up a new account in Outlook 2010/2013/2016/2019/ Office 365, often times we find users unable to connect or – or Outlook’s web services don’t work as expected.
For example, when adding a new account, autodiscover will time out, saying it can’t contact the server giving the following message :
Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The Microsoft Exchange information service in your profile is missing required information. Modify your profile to ensure that you are using the correct Microsoft Exchange information service.
This, despite Microsoft’s (very useful) Remote Connectivity Analyzer reporting no configuration issues with Autodiscover, and being able to connect successfully using MS Activesync.
The issue we see here, is that Outlook is pre-configured by Microsoft 365’s profile configuration to prefer only M365 sources for autodiscover – ignoring DNS settings and local XML files.
This behavior is regulated by the registry, specifically keys under the Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\XX.0\Outlook\AutoDiscover location. XX.0 will vary, depending on the version of Office you have installed. Examples of these keys are :
[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover] "ExcludeLastKnownGoodUrl"=dword:00000001 "ExcludeHttpRedirect"=dword:00000001 "ExcludeScpLookup"=dword:00000001 "ExcludeHttpsRootDomain"=dword:00000001 "ExcludeSrvRecord"=dword:00000001
By toggling these switches to “0” – or “do not exclude” these autodiscover sources, Outlook connectivity to on-premise or 3rd party Exchange providers will be restored.
More detail available via Microsoft at the following KB’s :
Click to share on Facebook (Opens in new window)
Click to share on Twitter (Opens in new window)
Click to share on LinkedIn (Opens in new window)
Click to email a link to a friend (Opens in new window)
Click to print (Opens in new window)
Scam Mail & E-Mails – License Scheme Targeting Corporation and LLC Owners
Questions, comments? Let us know! Cancel reply
Resolving Time Synchronization issues on Virtualized Active Directory Servers January 5, 2022
Windows 10 End-of-Life & Windows 11 Preview : What this means for your business July 2, 2021
Hardware & Drivers Issues
Subscribe to our Newsletter via Email
Enter your email address to subscribe to this blog and receive notifications of new posts by email.
Join 199 other subscribers
Resolving Time Synchronization issues on Virtualized Active Directory Servers
We’ve run into the issue of virtualized Primary Domain Controllers (PDCs) on Windows Server 2016/2019/2022 that fail to properly sync…
ph. 404.593.0083 fx. 404.585.5686
113 Pearl Street SE
Euclid Networks | Technology Partners for your Business | Serving Atlanta's tech support needs since 2006
Computer support vendor for Atlanta, Sandy Springs, Dunwoody, Smyrna, Downtown, Decatur, Brookhaven, Buckhead, Midtown, Roswell, Alpharetta, Chamblee, Kennesaw, Norcross. Offering IT support for lawfirms, healthcare IT, tech support for attorneys, office tech help, and more!