Email Services/Office 365/Client Configuration Documents
< Email Services | Office 365
Jump to navigation
Jump to search
Desktop Client Changes and Configuration Documents
Outlook 2010 or 2013 for Windows
- No issues during migration. After migration completes, Client reports the following notification
- "The Microsoft Exchange Administrator has made a change that requires you to quit and restart outlook"
- Restarting Outlook reestablishes the connection. No client reconfiguration should be necessary
- If you have connectivity issues refer to the following setup documents
Outlook 2016 for Mac
- No issues during migration. After migration completes, Client reports the following notification
- "Outlook was redirected to the server autodiscover-s.outlook.com to get new settings for your account"
- To re-establish client connection do the following:
- check the "Always use my response for this server" check box
- click "Allow"
- If connectivity fails change your server settings
- from the Outlook menu, choose preferences
- make sure username is in the format [email protected]
- click advanced
- change the server name to https://outlook.office365.com/EWS/exchange.asmx
Outlook 2011 for Mac
- No issues during migration. After migration completes, Client reports the following notification
- "Outlook was redirected to the server autodiscover-s.outlook.com to get new settings for your account"
- To re-establish client connection do the following:
- check the "Always use my response for this server" check box
- click "Allow"
- If connectivity fails, verify your settings. Refer to the document Configuring Outlook for Mac 2011 for Exchange
Apple Mail
- Tested version 8.2 (OS 10.10.5)
- No issues during migration. After migration there were no warnings, but new mail would not synch
- Resolution is to delete and recreate the account.
- If you have connectivity issues refer to Apple Mail Setup
Apple Calendar
- Tested version 8.0 (OS 10.10.5)
- No issues during migration. After migration there were no warnings, but new items would not synch
- Resolution is to delete and recreate the account.
- If you have connectivity issues refer to Apple Calendar and Address Book Setup
Thunderbird (All Operating Systems)
- No issues during migration. After migration, received error, "Login to server mail.anl.gov failed"
- To fix the issue, the username and server names need to be changed
- change username to [email protected]
- change incoming server name to outlook.office365.com
- change smtp (outgoing) server to smtp.office365.com
- If the changes above do not reestablish connectivity, refer to Configuring Thunderbird for Office 365
Mobile Device Changes and Configuration Documents
Generic Settings
- For Generic IMAP setup, you'll have to delete and recreate the account, using the following settings
- change username to [email protected]
- change incoming server name to outlook.office365.com, port 993, SSL
- change smtp (outgoing) server to smtp.office365.com, port 587, SSL
Android Devices
- If you are connecting via IMAP and have issues, refer to Configuring Android OS Devices for Office365 IMAP
- If you have ActiveSync connectivity issues refer to the notes below or refer to Android Activesync Device Setup
- 4.3 jelly bean
- error saying "couldnt log in"
- had to remove the account through mail app--->settings, then highlight the account name and choose "remove account" from resulting menu
- recreated the account with same settings as old account. Refer to Android Activesync Device Setup
- had to respond to security settings update request
- 4.4.4 kitkat
- error saying "couldnt log in"
- had to remove the account through settings-->accounts-->corporate
- recreated the account with same settings as old account. Refer to Android Activesync Device Setup
- 5.0.2 lollipop
- Had to restart mail app
- If that does not work, see Android Activesync Device Setup
iOS Devices
- If you are connecting via IMAP and have issues, refer to Configuring Apple iOS Devices for Office365 IMAP
- If you have ActiveSync connectivity issues refer to the notes below or refer to iOS Activesync Device Setup
- iOS 9.02
- received a could not connect error initially, but did not have to reconfigure
- device reboot re-esatblished connectivity
- users who have "ANL" the "domain" field configured for the Exchange connection will have to clear that field
- users whose username field does not contain their username in the supported syntax "[email protected]" will have to edit that field appropriately.
- Please refer to Configuring Apple iOS Devices for Office365 for configuration examples
- iOS 8.4
- received a could not connect error initially, but did not have to reconfigure
- device reboot re-esatblished connectivity
- users who have "ANL" the "domain" field configured for the Exchange connection will have to clear that field
- users whose username field does not contain their username in the supported syntax "[email protected]" will have to edit that field appropriately.
- Please refer to Configuring Apple iOS Devices for Office365 for configuration examples
- iOS 5.1.1
- continually prompted for password to Exchange
- had to delete and recreate the exchange account
- left domain field blank and username in format [email protected]
- See Configuring Apple iOS Devices for Office365
Windows Mobile Devices
- Windows RT 8.1
- no warnings or changes required