Office 365 users can't connect to Exchange Online because of incorrect service settings
Office 365 users in your organization who connect to Exchange Online by using incorrect hardcoded service settings (or IP addresses) will be unable to connect to the service after these outdated service settings are discontinued on July 8, 2015. (The original date was June 26, 2015).
The services for which users may be using incorrect settings include the following:
- Autodiscover: A feature that's used to automatically discover server names for connectivity
- Exchange ActiveSync (EAS): A protocol that's used by email client applications on mobile devices
- POP3 and IMAP4: Protocols that are used by email client applications on desktop and mobile devices
- SMTP: Protocol that's used for sending email messages
The following table lists the features, protocols, and expected server settings that must be set, and provides links to the articles that contain instructions to configure these settings.
|Feature and protocol||Port||Server name|
|Autodiscover (CName Record)||443||autodiscover.outlook.com||Create DNS records at any DNS hosting provider for Office 365|
|Exchange ActiveSync (EAS)||443||outlook.office365.com||Set up a mobile device to synchronize with your account|
|POP3||995||outlook.office365.com||Settings for POP and IMAP access for Office 365 for business or Microsoft Exchange accounts|
|IMAP4||993||outlook.office365.com||Settings for POP and IMAP access for Office 365 for business or Microsoft Exchange accounts|
|SMTP||587||smtp.office365.com||Settings for POP and IMAP access for Office 365 for business or Microsoft Exchange accounts|
How to Allow a Multi-function Device or Application to Send E-mail through Office 365 Using SMTP
Windows uses a file that's named Hosts to map hostnames to IP addresses. This file is checked before DNS is used to resolve a server name. If the Hosts file on a Windows computer has an entry for any of the server names in the table, and if the entry is associated with a hardcoded IP address, DNS is not used to resolve that server name. Make sure that you reset the Hosts file on all such systems that may be experiencing the issue that's documented in this article.
For more information about how to reset the hosts file, see the following Microsoft Knowledge Base article:
972034 How can I reset the Hosts file back to the default?
Still need help? Go to the Office 365 Community website.
Article ID: 3067822 - Last Review: 06/22/2015 21:09:00 - Revision: 9.0
Microsoft Exchange Online
- o365e o365m o365022013 o365 o365a KB3067822