Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Buscar en Ayuda

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

Este tema ha sido archivado. Haz una nueva pregunta si necesitas ayuda.

Thunderbird 102.7.1 on OSX Monterey cannot connect to Outlook. However, 91.13.1 has no issues

  • 2 respuestas
  • 0 tienen este problema
  • 20 visitas
  • Última respuesta de sgnadkarni

sgnadkarni
sgnadkarni

I have two laptops both on Monterey. On my primary laptop I had no issues connecting to our outlook server. However, after I upgraded to 102.7.1, it suddenly stopped working. My logins fail after providing my password. From my other laptop has an older version of Tbird (91.13.1) also running Monterey I am able to connect to Outlook server after providing the password.

Wondering if others have encountered a similar issue.

I have two laptops both on Monterey. On my primary laptop I had no issues connecting to our outlook server. However, after I upgraded to 102.7.1, it suddenly stopped working. My logins fail after providing my password. From my other laptop has an older version of Tbird (91.13.1) also running Monterey I am able to connect to Outlook server after providing the password. Wondering if others have encountered a similar issue.

Solución elegida

The Oauth authentication on 102.7 for Microsoft mail servers is completely different from V91. It is apparently more secure and causing loads of issues. Are you using oauth?

Leer esta respuesta en su contexto 👍 1

Todas las respuestas (2)

Matt
Matt
  • Top 25 Contributor

Solución elegida

The Oauth authentication on 102.7 for Microsoft mail servers is completely different from V91. It is apparently more secure and causing loads of issues. Are you using oauth?

sgnadkarni
sgnadkarni Autor de la pregunta

Thanks for the clue. On upgrade to 102.7.1 the authentication method switched from oauth2 and normal. Setting it back to Oauth2 fixed it.

Modificadas por sgnadkarni el