MC375736 – (Updated) Basic Authentication Deprecation in Exchange Online – May 2022 Update

Microsoft Exchange Logo

*For this entry exists the more relevant or more recent entry (MC424246)

check before: 2022-10-01

Product:

Exchange, Microsoft 365 admin center, Outlook

Platform:

Android, Developer, iOS, Mac, mobile, Online, Web, World tenant

Status:

Change type:

Admin impact, Retirement, Updated message, User impact

Links:

(MC424246)
(MC424244)
(MC424219)
(MC424189)
(MC403391)
(MC402113)
(MC402111)
(MC393179)
(MC393177)
(MC389751)
(MC388690)
MC286990

Details:

Updated May 10, 2022: We have updated this post to show as intended. Thank you for your patience.
In about 150 days from today, we’re going to start to turn off Basic Auth for specific protocols in Exchange Online for those customers still using it.
[Timeline and Scope]
As we communicated last year in blog posts and MC286990, we will start to turn off Basic Authentication in our worldwide multi-tenant service on October 1, 2022. To clarify, we will start on October 1; this is not the date we turn it off for everyone. We will randomly select tenants, send 7-day warning Message Center posts (and post Service Health Dashboard notices), then we will turn off Basic Auth in the tenant. We expect to complete this by the end of this year. You should therefore be ready by October 1.
We’re turning off Basic Auth for the following protocols: MAPI, RPC, Offline Address Book (OAB), Exchange Web Services (EWS), POP, IMAP, Exchange ActiveSync (EAS) and Remote PowerShell.
We are not turning off SMTP AUTH. We have turned off SMTP AUTH for millions of tenants not using it, but if SMTP AUTH is enabled in your tenant, it’s because we see usage and so we won’t touch it. We do recommend you disable it at the tenant level and re-enable it only for those user accounts that still need it.
[Exceptions and Per-Tenant Timing]
There is no way to request an exception after October. Tenant selection is random, and we cannot put your tenant to the back of the queue to give you more time or change your settings on any specific date. If you want Basic Auth to be disabled at a time of your choosing (either now, or as soon as you are ready), use Authentication Policies.

Change Category:
XXXXXXX ...

Scope:
XXXXXXX ...

Release Phase:

Created:
2022-05-05

updated:
2022-08-27

the free basic plan is required to see all details. Sign up here


A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.


changes*

DatePropertyoldnew
2022-08-27MC prepareAny client (user app, script, integration, etc.) using Basic Auth for one of the affected protocols will be unable to connect. The app will receive an HTTP 401 error: bad username or password.
Any app using Modern Auth for these same protocols will be unaffected.
To read more on what can be done to switch apps from Basic to Modern auth please view our main documentation page and our latest blog.
https://docs.microsoft.com/exchange/clients-and-mobile-in-exchange-online/authenticated-client-smtp-submission
https://docs.microsoft.com/exchange/clients-and-mobile-in-exchange-online/disable-basic-authentication-in-exchange-online
https://techcommunity.microsoft.com/t5/exchange-team-blog/basic-authentication-and-exchange-online-september-2021-update/ba-p/2772210
Any client (user app, script, integration, etc.) using Basic Auth for one of the affected protocols will be unable to connect. The app will receive an HTTP 401 error: bad username or password.
Any app using Modern Auth for these same protocols will be unaffected.
To read more on what can be done to switch apps from Basic to Modern auth please view our main documentation page and our latest blog.
ps://docs.microsoft.com/exchange/clients-and-mobile-in-exchange-online/authenticated-client-smtp-submi
ps://docs.microsoft.com/exchange/clients-and-mobile-in-exchange-online/disable-basic-authentication-in-exchange-onl
ps://techcommunity.microsoft.com/t5/exchange-team-blog/basic-authentication-and-exchange-online-september-2021-update/ba-p/27722
2022-05-11MC MessagesIn about 150 days from today, we’re going to start to turn off Basic Auth for specific protocols in Exchange Online for those customers still using it.
[Timeline and Scope]
As we communicated last year in blog posts and MC286990, we will start to turn off Basic Authentication in our worldwide multi-tenant service on October 1, 2022. To clarify, we will start on October 1; this is not the date we turn it off for everyone. We will randomly select tenants, send 7-day warning Message Center posts (and post Service Health Dashboard notices), then we will turn off Basic Auth in the tenant. We expect to complete this by the end of this year. You should therefore be ready by October 1.
We’re turning off Basic Auth for the following protocols: MAPI, RPC, Offline Address Book (OAB), Exchange Web Services (EWS), POP, IMAP, Exchange ActiveSync (EAS) and Remote PowerShell.
We are not turning off SMTP AUTH. We have turned off SMTP AUTH for millions of tenants not using it, but if SMTP AUTH is enabled in your tenant, it’s because we see usage and so we won’t touch it. We do recommend you disable it at the tenant level and re-enable it only for those user accounts that still need it.
[Exceptions and Per-Tenant Timing]
There is no way to request an exception after October. Tenant selection is random, and we cannot put your tenant to the back of the queue to give you more time or change your settings on any specific date. If you want Basic Auth to be disabled at a time of your choosing (either now, or as soon as you are ready), use Authentication Policies.
Updated May 10, 2022: We have updated this post to show as intended. Thank you for your patience.
In about 150 days from today, we’re going to start to turn off Basic Auth for specific protocols in Exchange Online for those customers still using it.
[Timeline and Scope]
As we communicated last year in blog posts and MC286990, we will start to turn off Basic Authentication in our worldwide multi-tenant service on October 1, 2022. To clarify, we will start on October 1; this is not the date we turn it off for everyone. We will randomly select tenants, send 7-day warning Message Center posts (and post Service Health Dashboard notices), then we will turn off Basic Auth in the tenant. We expect to complete this by the end of this year. You should therefore be ready by October 1.
We’re turning off Basic Auth for the following protocols: MAPI, RPC, Offline Address Book (OAB), Exchange Web Services (EWS), POP, IMAP, Exchange ActiveSync (EAS) and Remote PowerShell.
We are not turning off SMTP AUTH. We have turned off SMTP AUTH for millions of tenants not using it, but if SMTP AUTH is enabled in your tenant, it’s because we see usage and so we won’t touch it. We do recommend you disable it at the tenant level and re-enable it only for those user accounts that still need it.
[Exceptions and Per-Tenant Timing]
There is no way to request an exception after October. Tenant selection is random, and we cannot put your tenant to the back of the queue to give you more time or change your settings on any specific date. If you want Basic Auth to be disabled at a time of your choosing (either now, or as soon as you are ready), use Authentication Policies.
2022-05-11MC TitleBasic Authentication Deprecation in Exchange Online – May 2022 Update(Updated) Basic Authentication Deprecation in Exchange Online – May 2022 Update
2022-05-11MC Action Required By03/31/2023 09:00:002022-10-01T09:00:00Z
2022-05-11MC Last Updated05/07/2022 01:21:412022-05-10T17:44:44Z
2022-05-11MC MessageTagNamesUser impact, Admin impact, RetirementUpdated message, User impact, Admin impact, Retirement
2022-05-07MC MessagesIn about 150 days from today, we’re going to start to turn off Basic Auth for specific protocols in Exchange Online for those customers still using it.
[Timeline and Scope]
As we communicated last year in blog posts and MC286990, we will start to turn off Basic Authentication in our worldwide multi-tenant service on October 1, 2022. To clarify, we will start on October 1; this is not the date we turn it off for everyone. We will randomly select tenants, send 7-day warning Message Center posts (and post Service Health Dashboard notices), then we will turn off Basic Auth in the tenant. We expect to complete this by the end of this year. You should therefore be ready by October 1.
We’re turning off Basic Auth for the following protocols: MAPI, RPC, Offline Address Book (OAB), Exchange Web Services (EWS), POP, IMAP, and Remote PowerShell.
We are not turning off SMTP AUTH. We have turned off SMTP AUTH for millions of tenants not using it, but if SMTP AUTH is enabled in your tenant, it’s because we see usage and so we won’t touch it. We do recommend you disable it at the tenant level and re-enable it only for those user accounts that still need it.
[Exceptions and Per-Tenant Timing]
There is no way to request an exception after October. Tenant selection is random, and we cannot put your tenant to the back of the queue to give you more time or change your settings on any specific date. If you want Basic Auth to be disabled at a time of your choosing (either now, or as soon as you are ready), use Authentication Policies.
In about 150 days from today, we’re going to start to turn off Basic Auth for specific protocols in Exchange Online for those customers still using it.
[Timeline and Scope]
As we communicated last year in blog posts and MC286990, we will start to turn off Basic Authentication in our worldwide multi-tenant service on October 1, 2022. To clarify, we will start on October 1; this is not the date we turn it off for everyone. We will randomly select tenants, send 7-day warning Message Center posts (and post Service Health Dashboard notices), then we will turn off Basic Auth in the tenant. We expect to complete this by the end of this year. You should therefore be ready by October 1.
We’re turning off Basic Auth for the following protocols: MAPI, RPC, Offline Address Book (OAB), Exchange Web Services (EWS), POP, IMAP, Exchange ActiveSync (EAS) and Remote PowerShell.
We are not turning off SMTP AUTH. We have turned off SMTP AUTH for millions of tenants not using it, but if SMTP AUTH is enabled in your tenant, it’s because we see usage and so we won’t touch it. We do recommend you disable it at the tenant level and re-enable it only for those user accounts that still need it.
[Exceptions and Per-Tenant Timing]
There is no way to request an exception after October. Tenant selection is random, and we cannot put your tenant to the back of the queue to give you more time or change your settings on any specific date. If you want Basic Auth to be disabled at a time of your choosing (either now, or as soon as you are ready), use Authentication Policies.
2022-05-07MC Last Updated05/05/2022 01:21:572022-05-07T01:21:41Z

*starting April 2022

Last updated 4 weeks ago

Login to your account

Welcome Back, We Missed You!