![how to configure office 365 in outlook 2016 manually how to configure office 365 in outlook 2016 manually](https://tachytelic.net/wp-content/uploads/Outlook2013ManualAccountSetup.png)
- #How to configure office 365 in outlook 2016 manually how to#
- #How to configure office 365 in outlook 2016 manually manual#
Tick the “ Connect to Microsoft Exchange using HTTP” checkbox and press the “ Exchange Proxy Settings” button. We’re not done yet! Now, press the “ More Settings” button and navigate to the “ Connection” tab. Make sure the “ Use Cached Exchange Mode” checkbox is selected and adjust the slider as per your preference of keeping mail locally. This is where the important part starts, so be careful! In the “ Server” field, enter the Server Name we obtained above using Autodiscover, or if you were using PowerShell, enter the If you do not have the GUID, enter ( will also work here, can you guess why?). In the “ User Name” field, enter the primary SMTP address/UPN. On the next page, select “ Microsoft Exchange Server or compatible service” and press the Next button.
#How to configure office 365 in outlook 2016 manually manual#
Once you have started the “ Add Account” wizard, select the “ Manual setup or additional server types” checkbox and press Next. You can either directly press on “ E-mail Accounts” or create a new profile first, up to you. On the top right corner, change the view to Large or Small items and locate the “ Mail” icon, then double-click on it. I will discuss some other methods of obtaining it ‘manually’ later. For the moment, lets focus on creating the new account. Make sure Outlook is closed and navigate to the Control Panel.
#How to configure office 365 in outlook 2016 manually how to#
Now that we have cleared that part, how to actually configure the mailbox? Well, as mentioned in the top note, with Exchange Online it is not actually necessary to know the GUID, as we can ask Outlook to find it out for us. Please restart.” Only Outlook 2007 and higher versions are supported with Exchange 2013. This simple change results in a near elimination of the unwelcome message of “Your administrator has made a change to your mailbox. Outlook uses Autodiscover to create a new connection point comprised of mailbox GUID, symbol, and the domain portion of the user’s primary SMTP address. 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.
![how to configure office 365 in outlook 2016 manually how to configure office 365 in outlook 2016 manually](https://osiprodweuodcspstoa01.blob.core.windows.net/en-us/media/8a52e7ba-8827-49b7-b83d-16679afe7c62.png)
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.
![how to configure office 365 in outlook 2016 manually how to configure office 365 in outlook 2016 manually](https://i.ytimg.com/vi/vpa01q1X9Mk/maxresdefault.jpg)
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.
![how to configure office 365 in outlook 2016 manually how to configure office 365 in outlook 2016 manually](https://cdn.windowsreport.com/wp-content/uploads/2019/08/Fix-outlook-2016-does-not-support-manual-setup-for-exchange-accounts.png)
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.