It appears how TB handles IMAP connections for outlook email accounts no longer works - OAuth2 connection flow broken, and this is likely due to stricter changes made on … (jàng ci lu gën a bari)
It appears how TB handles IMAP connections for outlook email accounts no longer works - OAuth2 connection flow broken, and this is likely due to stricter changes made on Microsoft's backend that is impacting connections going forward.
I have multiple email accounts configured and recently, I have been bombarded by login pop up - likely related to the OAuth2 authentic process.
Whilst I was able to circumvent the authentication process - i.e. not completing the flow process entirely as it expected, newly created outlook accounts appear to reveal two things:
1] There has been a recent change to the authentication process - i.e. the telling sign.
2] There is a now deeper issue when trying to connect outlook email accounts. It seems the reason why circumvention was possible with existing accounts was because they have already passed the OAuth2 process correctly - correct tokens exist. Since this won't be the case for new outlook accounts - no OAuth IMAP access token created, above error is given.
It seems the likely cause is because Thunderbird holds or requests a token that does not contain the correct IMAP audience/scope combination, and Exchange rejects it during SASL XOAUTH2 bind.
For your information, I am using the latest versions and able to configure Apple Mail client - which uses Exchange protocol (not IMAP), without issues.