manually setup office 365 in outlook 2016

Manually setup office 365 in outlook 2016 how to#
Manually setup office 365 in outlook 2016 manual#
Manually setup office 365 in outlook 2016 full#

Manually setup office 365 in outlook 2016 full#

If asked for credentials (which in most cases is bound to happen), make sure to provide the full UserPrincipalName and the correct password! Then watch the magic happen 🙂 Now we should be done! Press “OK” to confirm the changes and once you are back in the “ Add Account” wizard, press the “ Check Name” button. Scary, I know, but that’s the reality of Exchange Online. Here, navigate to the “ Security” tab and under “ Logon network security“, select “ Anonymous Authentication“. Here’s how it should look like:īut wait… there is still more to do! Press the “ OK” button to return to the “ More Settings” dialog. Lastly, under Proxy authentication settings, select Basic Authentication. Click to select the On fast networks, connect using HTTP first, then connect using TCP/IP check box, and then click to select the On slow networks, connect using HTTP first, then connect using TCP/IP check box. Make sure that the “ Connect using SSL only” and the “ Only connect to proxy servers that have this principal name in their certificate“Ĭheckboxes are selected, and then type msstd: in the field below. In the first field, “ Use this URL to connect to my proxy server for Exchange”, type in the host address. 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.

Manually setup office 365 in outlook 2016 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.

Manually setup office 365 in outlook 2016 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. 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. 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.