Would you please post a screenshot of the screen asking for <your login>? That may help. Thank you.

Thanks David.

Attachment 1 is the settings. Those showing in that attachment were apparently provided by the auto lookup on the server, when I clicked Re-test. But they're the same as the ones I'd keyed in, that were provided to by the organisation.

Attachment 2 is the rejection message when I clicked Done.

Regards ... Roger[[Att2 Rejection Knowledge Base Article|Att1 Settings]]

I see the attachment / linkage format broke. (I'm a newbie here, sorry).

Attachment 1 is here: http://rogerclarke.com/SOS/Att1-Settings-2024-04-21at07.54.19.png

Try it by changing the outgoing server to smtp.office365.com, 587, STARTTLS, and for both incoming and outgoing use OAuth2 authentication.

I made those changes. That got as far as login.microsoftonline.com. It demanded I loosen up on cookies. I allowed first session-cookies, then 'Allow' permanent on all of: - microsoftonline.com, office365.com, microsoft.com, acs.org.au.

It continues to decline, as per: https://rogerclarke.com/SOS/Att3-Challenge-2024-04-21at13.30.17.png

When I closed that window, it rejected as before: https://rogerclarke.com/SOS/Att4-Rejection-2024-04-21at13.31.48.png

It may be the password. I attempted to set up your account and just entered name, email address -NO password and pressed enter key. A microsoft window popped up to verify password. That indicates (to me) that the configuration may not be the issue.

I made those changes. That got as far as login.microsoftonline.com. It demanded I loosen up on cookies. I allowed first session-cookies, then 'Allow' permanent on all of: - microsoftonline.com, office365.com, microsoft.com, acs.org.au. It continues to decline, as per: https://rogerclarke.com/SOS/Att3-Challenge-2024-04-21at13.30.17.png When I closed that window, it rejected as before: https://rogerclarke.com/SOS/Att4-Rejection-2024-04-21at13.31.48.png

Did you allow cookies in your browser or in TB? Cookies must be accepted in TB Settings/Privacy & Security, at least for the MS site, to allow OAuth authentication to store an oauth:// token in Saved Passwords. Remove the entries for the account from Saved Passwords, restart TB, enter the account password in the OAuth window when prompted.

Ah, I hadn't restarted TB because I assumed that, once saved, the allow-cookies settings were active. As you described, the OAuth window duly asked for my password.

Great work thanks David/sfhowes!!

I'll close this thread when I can. (I don't think I can click on <Solved the problem> until after I've posted this final message).

P.S. for completeness. It then failed with: > Sending of password for user Roger.Clarke@acs.org.au did not succeed. Mail server outlook.office365.com responded: Authentication failure: unknown user name or bad password.

But that's the test of the organisation's MS settings that I was trying to perform, so now I can take the next step in my dealings with them.

When the OAuth window appears, enter the account password, not an app password. If two-step verification is set on the account, which usually requires using an app password, disable it, as it's not necessary with OAuth2 authentication.