This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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?
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.
Is it possible to ask your Exchange Administrator to enable IMAP? At least you can send and receive messages that way. You'll probably lose out on the Outlook Address Book.
Would be interested to see if it would work with just the autodiscover dns entries created.
We have offices in many city and each city AD domain is different. but we have Main Exchange server in Corp Office which one is common for all. but in Outlook 2016. I cannot configure all others domain users Emails since Outlook having only 'Autodiscovery' for exchange.
We spend huge money to upgrade to office 2016 ( more than 1500 user licenses) . last one month I lost my face due to this issues.....
Thanks
Ashok Nair
Even if local autodiscover.xml method is working correctly, we still won't add Exchange account manually in Outlook 2016, right?
Otherwise, our Exchange admins will never allow Exchange mode via auto setup for out of domain side...
There is no manual option in Outlook 2016 - certainly not like we had in outlook 2013. You put in the email address, outlook finds the account configuration using autodiscover. If you are using the xml file, autodiscover will work and should set it up as an exchange account - it will get the information it needs from the xml file, ping the server for details, and set up the account.
In Outlook 2013, we can add our accounts only manual way (in Exchange mode). We also cannot use auto setup in Outlook 2013!
I mean, we cannot use auto account setup both Outlook 2013 and 2016. We can set it manually in Outlook 2013 and we can use Exchange mode. But, we cannot add our account manually in Outlook 2016.
Even if local autodiscover.xml method is working correctly, we still won't add Exchange account manually in Outlook 2016, right?
Otherwise, our Exchange admins will never allow Exchange mode via auto setup for out of domain side...
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...
This could be caused by issues with autodiscover or they only allow pop3 or imap (or OWA) from the internet and only allow outlook access if connected to the network. (I forgot, it worked in 2013, so its definitely autodiscover in your case.)