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

101 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2017-08-10T22:43:09+00:00

    oh, "never ever" is a long time - i bet it will be properly configured eventually.

    This may surprise you closed-minded people who think the world only runs Microsoft servers, however a lot of people use Exchange API (sold by Microsoft I might add) on Linux and other 3rd-party mail servers. Such as Kerio Connect. And no, not every one will ever have publically broadcast autodiscovery. 

    So no, your high-horse answer of "well they'll have to" is flat out wrong. MS had no business forcing autodiscovery only for the Exchange protocol in their latest version of Outlook.

    Here's how to get around this nonsense.

    • Open up Control Panel (Windows-S, then type "control panel" and select it).
    • In the control panel's Search Bar (top right), type "mail"
    • Select "Mail (Microsoft Outlook 2016)"
    • Click on "Email Accounts"
    • There's your old wizard.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2016-10-19T11:29:09+00:00

    Actually, there is some info that i forget to say. But, I stuck in "manually add" and just i forgot what happened in auto add account...

    when i enter my name, mail address and password and click next, successfully set in POP3 mode. Of course i don't want to use POP3 mode. Never set in Exchange mode. If i join our corp domain, there's no problem. But out of our domain, auto set account is only in POP3 mode. How can we correct this? I think, this is not related autodiscover issue...

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2015-08-11T02:26:27+00:00

    There are a couple of major instances as to why Autodiscover may not be enabled on a particular domain.

    1. Domain Aliases. For example -- 

       CompanyDomainName.com

       SomeotherNewCompanyDomainName.com

    If I have an account on SomeOtherNewCompanyDomainName, then I should not have to use CompanyDomainName (that has AutoDiscover working) in order to login to SomeOtherNewCompanyDomainName.com 

    Many companies that have multiple domains running on a single Exchange 2010 or even Exchange 2013 server will not be able to properly use Outlook 2016.

    1. SBS Servers everywhere ... Yeah, they were pretty broken on AutoDiscover. They will all fail to work on Outlook 2016. Out of the box, all these damn servers were setup on .LOCAL -- who was the idiot that designed this? Now Outlook 2016 will be incompatible with SBS servers.

    I don't understand why when even the iPhone Outlook app has a way of specifying additional login options that this is missing from the Outlook 2016 account creation process. The fix is pretty simple:

    1. Email Address
    2. Username 
    3. Host Name
    4. Password

    That combination is what is required in order to access a mail server that is different than the email address.

    I really don't understand what the "Product Designers" at Microsoft are thinking by rejecting a good 40% of the entire world's normal operating procedures. 

    Those people should be made to live a day in the life of an IT consultant and to experience the hell that was SBS server and the whims of a CEO before they decide to rip out an essential feature without a proper replacement.

    Outlook 2016 will be a failure out of the gate should they release it. No sane IT person will recommend it.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. 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
  5. 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