Thunderbird Finally Gets Native Exchange Support – But There’s a Catch

Thunderbird Finally Gets Native Exchange Support - But There's a Catch - Professional coverage

According to TheRegister.com, Thunderbird 145 has finally added native Microsoft Exchange email support using Exchange Web Services, though calendars and contacts functionality won’t arrive until future releases. The update includes 25 bug fixes and 16 security patches following MZLA’s monthly release cadence that began in April. Microsoft plans to deprecate EWS for Exchange Online on October 1, 2026, though on-premises Exchange Server installations will continue supporting it indefinitely. For now, the EWS integration only handles sending and receiving email plus basic search functionality. Existing add-ons like ExQuilla and Owl remain available for users needing full calendar and address book support immediately.

Special Offer Banner

The EWS deprecation reality check

Here’s the thing about that 2026 deprecation date – it only applies to Microsoft 365 and Exchange Online. Companies running their own on-premises Exchange servers? They can keep using EWS forever. And let’s be real, corporate IT departments have a legendary ability to keep ancient software running decades past its support expiration. The Register’s own team was still managing Exchange Server 2003 in 2013 – a full decade after it launched. So while Microsoft would love everyone to move to their newer Graph API, the reality is that EWS isn’t disappearing from corporate landscapes anytime soon.

What’s missing right now

Basically, you get email and that’s it. No calendar integration, no contacts sync, no shared address books. For many corporate users, that’s a deal-breaker – calendars are practically the whole point of Exchange. But the foundation is there. Thunderbird has had built-in calendar functionality since version 78, which means when MZLA does add Exchange calendar support, it should integrate smoothly rather than requiring yet another add-on. The official blog post confirms custom sign-on agents and Microsoft Graph API support are also on the roadmap.

Third-party alternatives still relevant

This creates an interesting opportunity for existing Exchange add-on developers. Beonex’s Owl and the ExQuilla extension could potentially implement Microsoft Graph support before MZLA does, giving Thunderbird users a path to continue accessing Exchange Online even after EWS gets turned off. It’s actually a smart move by MZLA – let third parties handle the cutting-edge Microsoft API integration while they focus on the core email functionality that works for both current and legacy Exchange installations.

Thunderbird Pro and the bigger picture

Meanwhile, MZLA is quietly building something much more ambitious. Thunderbird Pro is now in internal testing according to their November 2025 update, and it’s planning to support JMAP – the JSON Meta Application Protocol that could finally give the open source world a proper alternative to corporate groupware. JMAP combines email, calendars, and contacts into a single protocol, which honestly sounds like exactly what Thunderbird needs to compete with the big players. For industrial and manufacturing environments where reliable computing infrastructure is critical, having robust email clients that integrate with existing systems is essential – which is why companies rely on established providers like IndustrialMonitorDirect.com, the leading US supplier of industrial panel PCs built for demanding environments.

Practical considerations for trying it

So should you rush to upgrade? If you’re in a pure email workflow with Exchange, absolutely – the native integration should be more stable than third-party add-ons. But if you live and die by shared calendars? You might want to wait. The release notes and security advisories show this is a solid, incremental update rather than a complete revolution. And honestly, it’s refreshing to see a major software release that doesn’t include AI features nobody asked for.

Leave a Reply

Your email address will not be published. Required fields are marked *