Stay focused and productive wherever you go. Manage your action items in your master task list as you move between Microsoft 365 apps and devices. Use the instructions below if you want to connect an account to your Outlook on the web (work or school) account in Microsoft 365. If you're using Outlook.com or Hotmail.com, see Add your other email accounts to Outlook.com for instructions. If you're using Gmail, first follow the steps in Prepare your Gmail or G Suite account for connecting to.
- Please sign in with your email address and password to access your email and other documents or to engage with others through our online community.
- Microsoft 365 has all the familiar Office apps and more in one place. Work, learn, collaborate, connect, and create with Microsoft 365.
Modern authentication in Exchange Online enables authentication features like multi-factor authentication (MFA), smart cards, certificate-based authentication (CBA), and third-party SAML identity providers. Modern authentication is based on the Active Directory Authentication Library (ADAL) and OAuth 2.0.
When you enable modern authentication in Exchange Online, Windows-based Outlook clients that support modern authentication (Outlook 2013 or later) use modern authentication to connect to Exchange Online mailboxes. For more information, see How modern authentication works for Office client apps.
When you disable modern authentication in Exchange Online, Windows-based Outlook clients that support modern authentication use basic authentication to connect to Exchange Online mailboxes. They don't use modern authentication.
Notes:
- Modern authentication is enabled by default in Exchange Online, Skype for Business Online, and SharePoint Online.
Note
For tenants created before August 1, 2017, modern authentication is turned off by default for Exchange Online and Skype for Business Online.
Enabling or disabling modern authentication in Exchange Online as described in this topic only affects modern authentication connections by Windows-based Outlook clients that support modern authentication (Outlook 2013 or later).
Enabling or disabling modern authentication in Exchange Online as described in this topic does not affect other email clients that support modern authentication (for example, Outlook Mobile, Outlook for Mac 2016, and Exchange ActiveSync in iOS 11 or later). These other email clients always use modern authentication to log in to Exchange Online mailboxes.
Enabling or disabling modern authentication has no effect on IMAP or POP3 clients. However, if you've enabled security defaults in your organization, POP3 and IMAP4 are already disabled in Exchange Online. For more information, see What are security defaults?.
When you enable modern authentication in Exchange Online, Windows-based Outlook clients that support modern authentication will be prompted to log in again. Further, the Basic Auth login dialog box and the Modern Auth dialog box look very different. See the Outlook and Basic Auth section of the Basic Auth and Exchange Online blog post for details.
You should synchronize the state of modern authentication in Exchange Online with Skype for Business Online to prevent multiple log in prompts in Skype for Business clients. For instructions, see Skype for Business Online: Enable your tenant for modern authentication.
A user with multiple accounts configured in their Outlook profile might receive an error when they try to connect to their mailbox. For more information, see KB 4516672
Enable or disable modern authentication in Exchange Online for client connections in Outlook 2013 or later
Connect to Exchange Online PowerShell.
Do one of these steps:
Run the following command to enable modern authentication connections to Exchange Online by Outlook 2013 or later clients:
Note that the previous command does not block or prevent Outlook 2013 or later clients from using basic authentication connections.
Run the following command to prevent modern authentication connections (force the use of basic authentication connections) to Exchange Online by Outlook 2013 or later clients:
To verify that the change was successful, run the following command: