Update: The full timeline for retirement of Basic Authentication in Exchange Online is now published in Basic Authentication Deprecation in Exchange Online – September 2022 Update.
Last year we ann...
Updated Sep 01, 2022
Version 7.0
Blog Post
Hi,
We are using an application that integrates with Outlook clients and connects via Basic Authentication on Exchange Online. We migrated our on-premise Exchange environment to Exchange Online (Office 365) in November last year. User mailboxes were moved from on prem to EXO and the application that integrates with Outlook has be reconfigured to meet these requirements.
We're planning an upgrade of the app that integrates with Outlook and Exchange Online to a new version. The new version has support for OAuth 2.0 which can be (with some difficulty it seems) configured with Exchange Online.
What is the impact of us NOT implementing OAuth 2.0 as part of the upgrade? What will happen to our PRODUCTION system if we do not implement this? We assume the application impersonation to impersonate user email inboxes will fail when Basic Authen is decomissioned but as per the Microsoft notes this is not clear.
What will this mean for end users? Will they not be able to open Outlook and send/receive emails?
We are also using two factor authentication to allow users to access Outlook. Users cannot access Outlook without completing the two factor authentication process.
Thanks