You can try editing this XML but will need your LegacyDSN. A sample autodiscover.xml for my Office 365 account is here. Copy it the folder you entered in the registry, delete the previously created autodiscover file and rename the copy to autodiscover.xml. It will be named something like this: 9a2b291a2545a44e9fa74ac13aad98c2 - Autodiscover.xml.
Type or paste %localappdata%\microsoft\outlook in the address bar of Windows Explorer to open Explorer to the folder where the autodiscover file is stored. If you have access to a computer with Outlook 2013 or older, you may be able to use the autodiscover file it used. If the Exchange server is not properly configured, you'll need to create an autodiscover.xml containing all of your account information.
Note: you'll get a redirect warning and may need to supply your username and password twice. If the Exchange server is properly configured, your account will be configured in Outlook automatically. Now try adding your account to your Outlook profile using Auto Account Setup, entering your name, email address and password. HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\AutoDiscover Next, edit the registry to add an autodiscover reference: Don't forget to change the domain in redirecturl. Paste this into notepad and save as autodiscover.xml. If your company doesn't publish autodiscover in DNS, you can try creating an XML file. Use a value of 1 to enable, delete the key if you no longer want to exclude these checks. The other records you can exclude, also under the Autodiscover key are as follows. HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\AutoDiscover\ If Outlook is slow finding the autodiscover records, you may need to tell Outlook to exclude the root domain or other records. It's not needed when you use MAPI over HTTP as Outlook "talks" to the Exchange server over HTTPS. If you don't want to edit the registry, you can use this ready-to-use registry file: MapiHttpDisabledĪfter the account is automatically configured in Outlook, the connection tab is missing. HKEY_CURRENT_USER\Software\Microsoft\Exchange This will cause Outlook 2016 to fall back to RPC over HTTP. If your Exchange Server does not have MAPI over HTTP enabled, you'll need to set a registry key to disable MAPI over HTTP. Otherwise, go to Control panel, find Mail and set Outlook to ask which profile or set this profile as the default.ĭo not disable MAPI over HTTPS if you are using Office 365 Exchange Online. If this is the only profile you have, open Outlook.
I recommend deleting any Outlook 2016 profiles of the same name or renaming the profile before adding this key to the Outlook 2016 profiles. This method does not work 100% of the time, but it takes only minutes to try. If you are upgrading from Outlook 2013 and your Exchange account wasn't moved to the new profile, you might be able to restore the old profile.
Using our solution you have full control to test responses as different versions of Outlook, without Outlook required to be installed! Extremely helpful when you have a mix of Outlook clients you are supporting in your environment.
The Priasoft AutoDiscover Testing Tool is a great free utility for testing and reviewing AutoDiscover for both Office 365 and Exchange On Premise. To identify the root cause of these issues, the app runs checks such as: Checks licenses, Verify users' credentials and that Office 365 servers are reachable, Checks for updates to Outlook clients, Checks authentication, Network checks, Protocol checks
The app diagnoses common Outlook issues like account setup, connectivity issues, password issues, or Outlook stops responding or crashes. Microsoft Support and Recovery Assistant is a new tool that helps users troubleshoot and fix issues with various Office 365 apps and services. Microsoft Support and Recovery Assistant for Office 365