OAuth 2.0 (IMAP) required: Basic Authentication Retirement for legacy protocols in Exchange Online

  • 6 February 2020
  • 0 replies

  • New SysMate
  • 1 reply

We use IMAP integration with Microsoft Exchange Online.
It seems it will be neccessary to use OAuth 2.0 since October 13th 2020 for IMAP.
In which versions of Sysaid is the OAuth 2.0 authentication available for IMAP?
The following is a notification e-mail from Misrosoft informing about the upcoming change.
Thank you.


Basic Authentication Retirement for legacy protocols in Exchange Online
Major update: Announcement started
Applied To: All customers
Beginning October 13, 2020, we will retire Basic Authentication for EWS, EAS, IMAP, POP and RPS to access Exchange Online. Note: this change does not impact SMTP AUTH.
There are several actions that you and/or your users can take to avoid service disruptions on client applications, and we describe them below. If no action is taken, client applications using Basic Authentication for EWS will be retired on October 13, 2020.
Any application using OAuth 2.0 to connect to these protocols, will continue to work without change or interruption.
[What do I need to do to prepare for this change?]
You have several options on how to prepare for the retirement of Basic Authentication.
• You can start updating the client applications your users are using to versions that support OAuth 2.0 today. For mobile device access, there are several email apps available that support Modern Authentication, but we recommend switching to the Outlook app for iOS and Android as we believe it provides the best overall experience for your M365 connected users. For desktop/laptop access, we encourage the use of the latest versions of Outlook for Windows and Outlook for Mac. All Outlook versions including, or newer than, Outlook 2013 fully support OAuth 2.0.
• If you have written your own code using these protocols, you will need to update your code to use OAuth 2.0 instead of Basic Authentication, you can reach out to us on stack overflow with the tag exchange-basicauth if you need some help.
• If you or your users are using a 3rd party application, which uses these protocols, you will either need to
o reach out to the 3rd party app developer who supplied this application to update it to support OAuth 2.0 authentication
o assist your users to switch to an application that’s built using OAuth 2.0.
We are in the process of building reports that will help you identify any impacted users and client applications in your organization. We will make these reports available to you in the next few months and communicate their availability via a follow-up Message center post.

0 replies

Be the first to reply!