- #Configure outlook for office 365 without autodiscover how to#
- #Configure outlook for office 365 without autodiscover manual#
- #Configure outlook for office 365 without autodiscover windows#
Outlook clients no longer connect to a server FQDN as they have done in all previous versions of Exchange. You can read more about them here, but here’s the relevant bit: Why? Because there are some architectural changes in Exchange 2013. First however, you will need to obtain the ExchangeGUID of the mailbox. In the rare case that you need to configure an Exchange Online account manually, you can do so by following the instructions below. Microsoft has since published an article to further clarify on this here. The prime example here is 1&1, but others might be doing the same. So no excuses there, go configure it! Unfortunately, some DNS registrars limit the creation of CNAME records and thus are causing problems. Don’t believe me? Here’s an official statement from Microsoft. Not only it makes your life easier, it’s a requirement now.
First of all, you should be using Autodiscover. I’ve reorganized the article accordingly, and left the older bits at the end.
#Configure outlook for office 365 without autodiscover windows#
Users can opt for this approach in case they want to setup Office 365 in Microsoft Outlook 2013 / 2010 for Windows OS, in the absence of AutoDiscover feature.NOTE: This article was first published almost an year ago, since then I’ve added some additional methods and, thanks to a post by Mark Galvin at Experts Exchange, discovered a much easier method that does NOT require knowing the GUID upfront.
#Configure outlook for office 365 without autodiscover how to#
The below-mentioned instructions give guidance to the readers to setup your Office 365 Exchange Online account with Outlook 2010 : Steps to Manually Configure Outlook for Office 365 Without AutoDiscover
#Configure outlook for office 365 without autodiscover manual#
This means that the manual procedure illustrated in this blog does not apply in this edition of Microsoft Office. General Information – By default, Microsoft Outlook 2016 supports AutoDiscover procedure to add Exchange Online tenants. Either Autodiscover records are not setup properly up to the mark or might not be working well due to some unknown reason whatever it is now you have to manually configure Outlook 2013 to connect to Office 365. This restricts the domain to properly utilize auto configuration feature provided in Microsoft Outlook. Sometimes a situation occurs in which the domain hosting firm is unable to configure autodiscover records of CNAME. A set of manual steps is described in this content through which enterprises can setup Office 365 in Outlook 2013 or below versions. Summary – The post is helps Microsoft users to configure Outlook 2010 for Office 365 without autodiscover.