@padraig All caveats aside, there are some major gotchas by uptaking 140esr if you are currently an Exchange user on 128. The most significant of these is that *TbSync is no longer available for 140!*

TbSync has far superior coverage for Calendar and Contact support compared to OWL, and experimental native EWS is currently mail only. If you need contacts (esp multiple subfolders!) and calendars (esp shared calendars) then DO NOT upgrade from 128 for the foreseeable future.

@btaroli
Thanks for that. For context, I work for a web hosting provider who resells 'Microsoft 365 Business' products. (Cloud, Not on-prem)

We don't have any customers (to my knowledge) that are currently using Microsoft 365 in Thunderbird (unless they are using Owl)

We're just looking at the possibility of using TB in the future as an alternative client for Outlook.

My understanding is that only On-prem works in 140esr? Or does online work on 140esr also?

🧵 1/5 @padraig @thunderbird Took a little searching but I am working again! Yay. The complexity is that which setup to use with Exchange can be legacy (POP3, IMAP+SMTP, EAS, EWS/OWA) or current Graph API. Thunderbird 140 supports all of the legacy API but not yet Graph API.

#thunderbird #tb140 #TbSync #EAS4TbSync #exchange #ews #owa #eas #imap #pop3 #smtp #GraphAPI #WhyIsMicrosoftSoHard