Blog Post

Exchange Team Blog
2 MIN READ

Basic Authentication and Exchange Online – April 2020 Update

The_Exchange_Team's avatar
The_Exchange_Team
Platinum Contributor
Apr 03, 2020

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 announced changes to make Exchange Online more secure, and earlier this year we provided some updates on progress.

In response to the COVID-19 crisis and knowing that priorities have changed for many of our customers we have decided to postpone disabling Basic Authentication in Exchange Online for those tenants still actively using it until the second half of 2021. We will provide a more precise date when we have a better understanding of the impact of the situation.

We will continue to disable Basic Authentication for newly created tenants by default and begin to disable Basic Authentication in tenants that have no recorded usage starting October 2020. And of course you can start blocking legacy authentication today, you don’t need us to do anything if you want to get started (and you should).

We will also continue to complete the roll-out of OAuth support for POP, IMAP, SMTP AUTH and Remote PowerShell and continue to improve our reporting capabilities. We will publish more details on these as we make progress.

Update: For more news on OAUTH support for IMAP and SMTP go here and for POP, go here.

We still intend to move our customers away from Basic Authentication as we still very strongly believe improving security in Exchange Online benefits all of us, and so we’ll announce more accurate timelines for disabling Basic Authentication for tenants with usage at a later date.

 

The Exchange Team

Updated Sep 01, 2022
Version 7.0

67 Comments

  • Pascal_Odermatt's avatar
    Pascal_Odermatt
    Copper Contributor

    What about the Surface Hub?

    Microsoft docs mentioning to create a device account with active-sync authentication.

    The_Exchange_Team  would be nice to see an alternative for this use case.

     

    Source: https://docs.microsoft.com/en-us/surface-hub/create-a-device-account-using-office-365

  • StefanFried's avatar
    StefanFried
    Iron Contributor

    An API alternative  to access the reporting web service (eg. To pull messagetrace information) would be also pretty important. (The current api supports only basic auth).

     

    Powershell is no solution for us.

     

    Thank you

  • @ ND_Armand
    Office 365 service connectivity support end dates - As of October 13, 2020, connectivity support to Office 365 services (e.g. Exchange
    Online, SharePoint Online, OneDrive) will require Office 365 ProPlus or nonsubscription versions of Office in mainstream support. 
    See this: View related timelines on the Office system requirements matrix

    Not only will Outlook 2010 be EOS, but so will Outlook 2013.

  • victorguo's avatar
    victorguo
    Brass Contributor

    Any updates on the PowerShell certificate based authentication (CBA)?

  • Dave_Watson's avatar
    Dave_Watson
    Copper Contributor
    Can you provide a timeframe for when you will publish an updated API for PowerShell? I am looking for unattended authentication from PowerShell to query mailboxes and devices in an O365 tenant.
    Can you provide us with your interim progress, so we know what to anticipate once it is officially published?
     
    This update is nice for customers with simple needs, but the deadline hasn't changed for those of us that need to support both new and existing customers.