Skip to main content

Configure MS Outlook for Office365 Exchange Server 2013

This procedure is for you if you are using the following online services provided by Microsoft.
  • Office365
  • Recently upgraded from Exchange Server 2010 to Exchange Server 2013.
  • MS Outlook 2007 or 2010
Microsoft sent out an email on how to manage MS Outlook using the new Exchange Server 2013 environment. The new environment provides many features that admin and users will be able to appreciate after your successful transition. I agree with you, the process provided by Microsoft (and even their customer service still using the old procedure when I called them as of 5/15/2013) is NOT detailed but I have a simple solution to fix it. The procedure that help me re-configure all MS Outlook to connect using Offic365 Exchange Server 2013.

If you have any users, having a connection problem using their MS Outlook. Here's what you need to do. 
  • Close MS Outlook
  • Go to Control Panel, Email, Email Accounts 
  • In Email Account, select click on the Name e.g. (this is user email address), then click Repair. This will automatically update the user mailbox connection setting via autodiscover for the domain name. The user need to enter their email password for authentication. 
  • Click on Close to update your setting. 
  • Open MS Outlook program, MS Outlook will ask you to restart to accept the new settings. 
  • Re-open MS Outlook, and make sure it is not connected Offline (lower right corner of the screen). 
If everything is configured correctly, you will see the current emails.

Let's figure out what changed:
In the Server Settings, the server changed from the fully qualified domain name e.g. to (where is equivalent of your Office365 domain name for your company). The random number is unique to every Office365 user, so don't try to copy this from userA to userB or userC. It will not work.

And in Exchange Proxy Settings:
Connection settings, changed from to

Only connect to proxy servers that have this principal name in their ceritificate: (remain the same)

Good luck with your Office365 transition using Exchange Server 2013.

Please don't hesitate to post your reply if you have additional information to share.
Thank you.

If this helped you, please take the time to share this post by sharing using Google+, Facebook, Twitter, or LinkedIn


  1. Thank you for the information! Would this process work also for an upgrade from an on premise exchange server to office 365? And would this process keep or remove the old emails, calendars and contacts from the old outlook settings or exchange server? Thanks!

  2. Excellent write up! In my limited experience, however, I’ve found out that to Convert edb to pst - EdbMails is the best option as it can handle most exchange recovery tasks gracefully. It supports export of mailboxes to PSTs and also has an extensive range of filtering options. It is a forensic recovery that can extract most data from even corrupt or inaccessible exchange databases.It supports public, private folder recovery along with migration to Live exchange and Office 365. Archive mailbox migration is also supported by edbmails


Post a Comment

Popular posts from this blog

Office365 - This resource doesn't accept meetings longer than 1440 minutes

When you create a meeting schedule for number of days , you will see an error  "This resource doesn't accept meetings longer than 1440 minutes". By default the mailbox or room was set for a maximum limit of 1440 minutes. Here's how you can disable this limit. Login to the Office 365 Administration Console In Microsoft Office 365 Exchange, click on Manage . In Manage My Orgnization , click the drop down arrow, and click on Select on Another User . This will prompt you to select the mailbox or room to manage. Select a Mailbox or Room , click OK . In Option, click on Settings. In Scheduling Options, un-check the "Limit meeting duration", then click on Save. That's all. You can now schedule a meeting or reserve a room for number of days. Hope this help you. If this helped you, please take the time to share this post by sharing using Google+, Facebook, Twitter, or LinkedIn

Out of Office Reply for Termed Employee

This is a sample Out of Office message that I used for termed employees, unless HR staff specified a different message. === Example for KING.NET Employee === John Doe (employee or consultant)  is no longer with KING.NET effective  June 1, 2013  (termination date). For matters relating to " Project Name here " please direct your concerns to  John Smith at (Manager or Supervisor) . For all other matters, please direct your email to Mary Smith HR at Please call our main office 703-345-6789 if you have other concerns. Thank you. === End of message === I posted this article year 2008 from my old blog. If this helped you, please take the time to share this post by sharing using Google+, Facebook, Twitter, or LinkedIn

Office365 Setting to scan-to-email

I've searched the Internet if someone successfully use the Office365 Microsoft Exchange Online without the use of TLS and SMTP Authentication . I found nothing, so I've decided to write this article so other administrators will benefit and save time. Hopefully give me credit of saving their precious time :) Office365 (Microsoft Exchange Online) a cloud based email powered by Microsoft Exchange Server with running latest version. SMTP Authentication and TLS protocol are required for your printer to scan and email the result to your corporate intended recipients. I've tested the SMTP Authentication and TLS settings using Toshiba eStudio printers , and works like a charm. It took a while to configure but it works. See the captured configuration. I enabled SMTP Client with all certificate without CA, the SSL/TLS as STARTTLS (this is the key to make scan to email using Office365 to work). My SMTP Server Address is . Microsoft recommend that you