Email Services/Office 365 Client Documentation
Jump to navigation
Jump to search
This Wiki page contains basic instructions for connecting your Mail client and mobile device to Office 365 after you have been migrated from the ANL on premises Exchange Server.
What to Expect
- If a potential pilot user has delegates, all delegates MUST also be moved to Office 365 in order to retain that level of mailbox access.
- Pilot users will see an *incomplete* directory listing (GAL) - any users with their mailbox associated with a child domain account will NOT be visible to pilot users (a pilot user in Office 365 will not be able to “look up” a user with a mailbox associated with a child domain account; however, this does not prevent the pilot user from sending or receiving email to/from that user)
- Free/Busy calendar time for users with their mailbox associated with a child domain account will NOT be visible to pilot users - this does not prevent scheduling meetings, but it will be difficult
without knowing availability
- During the migration process, you should not expect any interruption in mail access or service. After your migration has completed, you may need to reconfigure your mail client or mobile device. The following documents will outline that process for the Laboratory's most frequently used mail clients and mobile devices.
- Office 365 users will not have access to Public folders. We are investigating the fix below as an option
If you experience issues, refer to the following configuration documents or call the Service desk at 2-9999 option 2 for assistance
Getting to Know Office 365
Office 365 Getting Started Guide
Desktop Client Changes and Configuration Documents
Outlook 2010 or 2013 for Windows
- NOTE: It is highly recommended that you upgrade to Outlook 2016 for Windows before moving to Office 365
- 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 Windows
Outlook 2011 for Mac
- NOTE: It is highly recommended that you upgrade to Outlook 2016 for Mac before moving to Office 365
- 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
Outlook 2016 for Mac
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 8,9 and 10
- 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