The article describes the issues that are related to the absence, improper configuration or resolution of CNAME record used for autodiscover service. For more information about this service refer to a Knowledge Base article on What Is An Autodiscover Record And Why Do I Need It?

Below are the symptoms that may indicate the problem with autodiscover process:

If you experience such issues, follow the suggested troubleshooting steps and read the information about autodiscover resolution process to know more about the root cause of the issue:

Read the symptoms description.

Outlook 2016 cannot connect to the mailbox

When configuring a profile for Outlook 2016, you may face the following error.

We are having trouble connecting to your account. Verify the settings below and make changes if necessary.

In most cases, this is caused by improper autodiscover resolution. Other causes are described in a Knowledge Base article on Why I Cannot Connect My Outlook 2016 To Exchange.

If autodiscover resolution gets corrupted or the corresponding CNAME record is erased when the profile is already configured, you will experience Send/Recieve errors and the Outlook profile won't sync.

Free/Busy information in your calendar is not available

If your account is hosted on the Exchange server and the Free/Busy information couldn't be retrieved in Outlook 2007/2010/2013 it is displayed as slash marks (\).

This can be caused by autodiscover, for other reasons read the Knowledge Base article on Why Is Free/Busy Information Unavailable In Outlook 2007/2010/2013?

Out of Office issues in Outlook

If you see the prompt below trying to set up Out of Office in Outlook, this is autodiscover related issue.

Your automatic reply settings cannot be displayed because the server is currently unavailable. Try again later.

Read the Knowledge Base article on How Do I Set Up Out Of Office Assistant? once the problem with autodiscover is resolved.

Offline Address Book synchronization issues

If your Outlook cannot pull current Offline Address Book from Exchange server, the issue can be resolved as described in the Knowledge Base article on Problems With Offline Address Book.

Sharing invitation does not work

If you see the prompt below when you try to send the invitation, that means that autodiscover does not resolve correctly.

Error while preparing to send sharing message.



For more information about sharing Calendars, Contacts, etc via Sharing Invitation read the Knowledge Base article on How Do I Share (Let Others See) My Outlook Folders (Inbox, Contacts, Calendar etc.)?

Shared mailbox auto-mapping does not work

If you shared a mailbox with the user and it does not show automatically on Navigation Pane in Outlook application, you need to check how autodiscover resolves on the affected PC. For more information about auto-mapping read the Knowledge Base article on How Does Mailbox Auto-Mapping Feature Work in Exchange 2010/2013?

Public Folders are not accessible in Exchange 2013/2016

Starting from Exchange 2013 Public Folder feature requires the presence of autodiscover record for a domain name for the email address you use to connect Outlook to the mailbox.  In case record is absent or resolves incorrectly the user won't see the Public Folders which admin made accessible for the user. For more information about Public Folders read the Knowledge Base article on Public Folders In Exchange 2013/2016.

Read the information about autodiscover resolution and troubleshooting process.

Autodiscover resolution

Important: the issues above can happen due to a different root cause, however absence of autodiscover record is the first suggestion to check.

In case autodiscover record is properly configured via your DNS hosting provider, there are no typos and mistakes, there can be a problem with the resolution of the record when Outlook fails to find the server autodiscover points to. Below are the steps Outlook performs when tries to find the autodiscover server:

  1. SCP lookup 
    Outlook gets information from Active Directory (on-premises Exchange server). 
    If the record cannot be obtained from local domain, the SCP lookup fails.
  2. HTTPS root domain query
    Outlook, which is not connected to domain, uses the domain name part of SMTP address for this query: https://domainname.com/autodiscover/autodiscover.xml
  3. HTTPS Autodiscover domain query
    In case HTTPS root domain query fails, the lookup of https://autodiscover.domainname.com/autodiscover/autodiscover.xml is happening.
    Note: if your website stores XML file mentioned in step 2 or 3, the autodisvoer process will fail. Contact your Web developer to remove the page from the site, so that the response of the links will be, for example, 404 Page not found.
  4. HTTP redirect method
    This step lets the Outlook find the Intermedia auodiscover server. In case correct DNS record is configured for your domain name, Outlook will successfully finish autodiscover process.

Also, the value of autodiscover record can be kept in your computer's OS cache or in a local hosts file, which was formerly used for resolution of IP addresses to domain names on user's machines. In this case, Outlook won't follow 4 steps described above but will refer to this value.

Troubleshooting

Follow the steps below to resolve the autodiscover related issues.

  1. Make sure you have correct CNAME record configured for autodiscover feature. Follow the Knowledge Base article on What Is An Autodiscover Record And Why Do I Need It? to have proper instructions.
  2. Clear DNS cache on your PC or Mac.
    • On PC: open Command prompt and type in ipconfig /flushdns. Execute the command.
    • On MAC OS X Yosemite: open the Terminal and type in  sudo killall -HUP mDNSResponder. Execute the command.

  3. Run Test E-mail AutoConfiguration tool in Outlook to review on what step Outlook fails to connect. If you do not see the failed step in the log,  contact Support and provide us the results, so that we could further assist you. Alternatively, you can run Microsoft Remote Connectivity Analyzer, choosing Outlook Autodiscover radio button under Microsoft Office Outlook Connectivity Tests section. Follow the instructions and provide Support with results of the test.
  4. If the Autodiscover for your domain resolves correctly, but there is one machine affected where you cannot setup profile automatically or features that depend on autodiscover does not work, modify the hosts file following the Knowledge Base article on How Do I Find And Modify Entries In The HOSTS File?
  5. If the Autodiscover resolves using your local ActiveDirectory values and does not find the values kept by DNS hosting provider, follow Step 4 of the article How Do I Disable Autodiscover For On-Premises Exchange? to use HTTP redirect method and skip all initial lookups.
    Note: the article provided in this step helps to resolve the issue of incorrect DNS resolution for all working stations included to your domain in case you were utilizing on-premises Exchange prior to migration of your mailboxes to Intermedia.

  6. If the test shows that autodiscover fails due to a presence of XML file on your website, contact your web developers to remove the files.
  7. If you have an existing Outlook profile and you utilize Outlook 2010 or 2013, which were set up manually or with Outlook Profile Helper, in Outlook navigate to File > Account Settings > Account Settings > Change > More Settings > Connection > Exchange Proxy setting and make the following changes:
    • Switch Basic Authentication to NTML Authentication
    • Check Only connect to proxy servers that have this principal name in their certificate check box
    • Type msstd:exchXXX.serverdata.net, where XXX depends on your proxy server information that you can find in HostPilot > Home >Exchange Servers and Settings > Exchange Proxy Server
    Then you will get a security prompt, check the box Don’t ask me about this website again and then click Allow.
  8. Outlook 2016, which only can be configured when there is an existing autodiscover record for your domain, may take to long to connect to the mailbox, to resolve this refer to the known issue #2 in the Knowledge Base article on How Do I Configure Outlook 2016 To Connect To Exchange.
  9. When Outlook implements HTTPS root domain query it can fail due to incorrect SSL installed on your website. For more information read the Knowledge Base article on Autodiscover Security Certificate Error.