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.
For many years, ...
Updated Jul 09, 2024
Version 10.0
Blog Post
We manage +100K users tenant and we try to embrace automation in our day to day jobs. I have some serious questions to find answers to:
- What are the ways of using modern auth non-interactively? We have some long-running scripts scheduled across several servers. They are scheduled to run automatically without an engineer supervising them.
- What do we do to the hundreds of automation scripts (remote PowerShell) which currently enjoy non-interactive connections to Exchange/AAD/MSOL/SPO etc.?
- What happens to the printers, scanners, MFPs, applications, websites which can't use modern auth by this deadline?
- Without our hands on the said 'tool' to detect users currently using basic authentication, how do we measure the beast we got to wrestle?
- What EAS versions and profiles already work on modern auth? Does native email on Android use basic auth? Does native mail app on iOS when configured with an app password use basic? What do we do for older devices not set to receive firmware upgrades? If they don't support modern auth, how do they access to email? We don't want to use IMAP/POP with or without modern auth.
- How do we give exceptions to service accounts? We’d like some service accounts to continue using basic authentication. We'd like to rewrite the scripts our own pace. With so many changes happening in M365.
Lastly, the deadline, October 2020 does not seem to be realistic for tenants of our size. We need more time if we have to change how M365 administration is done.