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.
It’s been a few ...
Updated Sep 01, 2022
Version 7.0
Blog Post
We currently use Remote PowerShell to Exchange online from an application using Basic Auth.
The new PowerShell ExchangeOnlineManagement does not work for us because it forces a change to Local PowerShell with in Imported Remote Session.
- It is very slow to import the session when connecting.
- Programatically it is different and would require a rework of the code.
- The new EX REST commands do not provide the same information in the same format - so are not useful anyway.
So we would like to keep just using Remote PowerShell with passing the OAuth token.
We have this working using "https://outlook.office365.com/PowerShell-LiveID?BasicAuthToOAuthConversion=true" as outlined in the articles below.
https://developermessaging.azurewebsites.net/2018/09/07/acquiring-oauth2-access-tokens-for-automating-exchange-management-shell-cmdlets/
https://www.michev.info/Blog/Post/1771/hacking-your-way-around-modern-authentication-and-the-powershell-modules-for-office-365
The question is will this still work after Basic Auth is turned off?
If not is there a supported way to do this?
Thanks