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
    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
  2. 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
  3. 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
  4. 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
  5. Anonymous
    2015-08-04T20:43:41+00:00

    Interesting.  Thanks for the info.  I ran some autodiscover tests on our domain....

    1. Failed on https://<domain>:443/Autodiscover/Autodiscover.xml.  Makes sense as I didn't set my root domain to redirect to Microsofts servers.  Nor should I have to.  They're just hosting my email.
    2. Failed on https://autodiscover.<domain>:443/Autodiscover/Autodiscover.xml.  This doesn't seem good as I have a CNAME record for autodiscover.<domain> to autodiscover.outlook.com as the setup specifies I should.  It pings correctly to Microsoft but doesn't respond to https (443).
    3. Succeeded on autodiscover.<domain>.  Since I have the CNAME record, this works as I would expect.  Again, not sure why https isn't working on microsofts side.
    4. Everything else after this worked except a warning with "Analyzing the certificate chains..."  But again, I would expect Microsoft to support their own software.  Might be an incorrect assumption but what else can I do about it?

    So the end result is that it's successfully but there are a few potential issues in there.  Maybe the initial setup tries the first two and correctly moves on to the third before succeeding and works.  But then on subsequent connections, it for some reason expects one of the first two secure options to work and doesn't even try the non-secure third option.  I'm just guessing here.  I have no idea what it's doing.

    Was this answer helpful?

    0 comments