Exchange account set-up missing for Outlook 2016

Anonymous
2015-05-10T20:07:40+00:00

I recently upgraded to Office 2016 Preview from Office 2013.  I had several POP / IMAP and Exchange accounts that all worked fine prior to the upgrade.  After the upgrade the POP / IMAP accounts work fine but non of the Exchange accounts work.  I got 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" Ok, so deleted the account and tried to set it up again however, under "Add Account" there is no longer an option to set up an Exchange account. There are only two options: 1) Outlook.com or Exchange ActiveSync compatible service or 2) POP or IMAP. The Microsoft Exchange Server or compatible service option is missing?

Microsoft 365 and Office
Microsoft 365 and Office

A comprehensive suite of productivity tools and cloud services that enhance collaboration, communication, and efficiency. Combining classic Office apps with advanced Microsoft 365 features, it supports both personal and business needs

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

101 answers

Sort by: Oldest
  1. Anonymous
    2015-08-04T20:58:15+00:00

    Ok, so after nearly three (3) hours on the phone with Microsoft, I was able to get the issue fixed. This is what I did...

    Open "regedit"

    Navigate to "HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\AutoDiscover"

    On the right, right-click, select "New" -> "DWORD (32-bit) Value"

    Name it "ExcludeHttpsRootDomain"

    Double-click the value after adding and set "Value data" to "1" and leave Base as Hexadecimal

    What was causing the issue...

    Evidently the root domain server was actually responding to the "autodiscover" request so outlook never made it to "AutoDiscover.[Domain.com]", it held up at "[Domain.com]:443". By adding this registry entry, it is telling outlook to ignore the root domain and go directly to the next option on the list (e.g. "Autodiscover.[Domain.com]".

    Hopefully this will help someone else having a similar issue.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2015-08-04T21:01:21+00:00

    Microsoft sent over these additional options to add as reg keys. If the one I used doesn't work for you, maybe one or more of these (or a combination thereof) will:

    0 to disable, 1 to enable Outlook Autodiscover behavior.

    “ExcludeScpLookup”=dword:00000001

    “ExcludeHttpsRootDomain”=dword:00000000

    “ExcludeHttpsAutoDiscoverDomain”=dword:00000000

    “ExcludeHttpRedirect”=dword:00000000

    “ExcludeSrvRecord”=dword:00000000

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-08-05T00:28:01+00:00

    thanks for taking the 3 hours!!

    This worked for me.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2015-08-06T16:46:57+00:00

    Thanks for the info.  I believe this has fixed my issue.  I was receiving the error and attempted setting some of these values and nothing changed.  I rebooted as well and no change.  So that was disheartening.  But then I went and recreated my profile again with the ExcludeHttpsRootDomain and ExcludeHttpsAutoDiscoverDomain set as those were the ones that failed in my tests.  It's been working fine for the last day even after reopening outlook and waking from sleep and all the normal stuff I do.  It's a little early to get too excited but I think the issue usually showed up shortly after.  So that fast that it's been a day now is a good sign.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2015-08-10T21:27:36+00:00

    Seems to have worked for a few days at least.  I didn't really touch it over the weekend.  But as of this morning, the error has returned.  Maybe those registry settings didn't do anything after all.

    Was this answer helpful?

    0 comments No comments