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: Oldest
Most helpful Newest Oldest
  1. 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
  2. Anonymous
    2015-08-11T02:51:48+00:00

    Interesting.  Well, like I said previously, I'm using Exchange Online (office 365) so it's microsoft's own servers I'm running on.  BUT, we do have it setup with our logins to Exchange are ******@sec-domain.com while our email addresses are ******@pri-domain.com.  This is because we're part or a larger company who manages the primary email domain themselves.  But we run our own exchange email system as that works better for us.  All email goes first to our primary email hosting and is auto-forwarded to our secondary domain which is our exchange online account.  I set our primary domain email addresses as our reply to accounts for all of our users.  So for all anyone can see, we are all sending/receiving emails from our primary domain.  But we actually log into our exchange accounts using our secondary domain.

    I wonder if this is where the problem is coming from?  This setup has been working for years before and after moving to Exchange Online.  And continues to work for Outlook 2010 and 2013.  Outlook 2016 initially can connect up this way.  But maybe at some point it tries to validate something and assumes that the login account is the same as the reply address and freaks out.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-08-11T03:14:43+00:00

    For those of us too timid or too stupid to use RegEdit, anyone know if Microsoft plans to release a "Fixit?"  Also, is Office 2016 actually released or is it still in beta?

    Was this answer helpful?

    0 comments
  4. Diane Poremsky MVP 17,526 Reputation points MVP Volunteer Moderator
    2015-08-11T03:53:44+00:00

    Office 2016 is still in beta status. Probably won't be released until fall or winter.

    I have a ready to use reg file at http://www.slipstick.com/doit/ExcludeAutoDiscover.reg. - you can open it in notepad to review and change any values from 0 to 1 as needed. Double click to run it (changing the file extension to reg if your browser changes it to txt when it's downloaded.) .

    Was this answer helpful?

    0 comments
  5. Anonymous
    2015-08-11T12:42:54+00:00

    Thanks. Will try it when I upgrade my PC to Win 10.

    Was this answer helpful?

    0 comments