Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Thunderbird OAuth2 Enter credentials popup is blank for outlook.office365.com

more options

I have a company email account on Office 365. I have to use it and I want to use Thunderbird for it. The account has sso that uses okta.

Thunderbird correctly identifies that the account is available on outlook.office365.com and pops up a window to complete the oauth flow. The oauth window does not display anything. If I copy the url from the window to my browser then I can complete the oauth flow easily. It fails when it ends with a "localhost" url which thunderbird presumably intercepts.

I cannot paste the final URL into thunderbird. I am thus unable to complete the oauth flow.

I have a company email account on Office 365. I have to use it and I want to use Thunderbird for it. The account has sso that uses okta. Thunderbird correctly identifies that the account is available on outlook.office365.com and pops up a window to complete the oauth flow. The oauth window does not display anything. If I copy the url from the window to my browser then I can complete the oauth flow easily. It fails when it ends with a "localhost" url which thunderbird presumably intercepts. I cannot paste the final URL into thunderbird. I am thus unable to complete the oauth flow.
Pridėtos ekrano nuotraukos

All Replies (2)

more options

This comment may be irrelevant, but if account is using Exchange, you may need an addon, such as OWL or Exquilla. I mention this only because some office365 accounts use this and some don't.

Helpful?

more options

Hi,

Thanks for the feedback. It's disappointing that I have to use a paid addon to get email from microsoft.

The blank screen went away after restarting thunderbird and now when collecting mail a notification comes up. It says "User is authenticated but not connected" and no messages are downloaded. I've searched for this message and the stack exchange message suggests an incorrect password:

https://unix.stackexchange.com/questions/164823/user-is-authenticated-but-not-connected-after-changing-my-exchange-password

However the oauth flow completed successfully using the correct password. I've also disabled ip v6 for network dns but that has not fixed the issue.

Helpful?

Užduoti klausimą

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.