Open Bug 1847846 (tb-ms-exchange) Opened 1 years ago Updated 3 days ago

[meta] Implement Microsoft Exchange

Categories

(Thunderbird :: Account Manager, task, P1)

Tracking

(Not tracked)

People

(Reporter: aleca, Unassigned)

References

(Depends on 38 open bugs, )

Details

(Keywords: meta)

Meta bug to track the implementation effort to fully support Microsoft Exchange, including authentication, email, calendar, and contacts.

Depends on: tb-ms-oauth2
See Also: → 134763
See Also: → 1846203
Keywords: meta
Depends on: 1859645
Depends on: 1859653
Depends on: 1859654
Depends on: 1859656
Depends on: 1859859
Depends on: 1860333
Depends on: 1860334
Depends on: 1860335
Depends on: 1868655
Depends on: 1876553

I'm posting this here because I'm not sure where else to mention this and don't see anything specific to "EWS Support" in an issue.

I've seen several articles recently about Thunderbird working to implement Exchange support using EWS.

EWS is deprecated for Exchange Online and will be blocked starting October 1, 2026.
84% of exchange mailboxes are in the cloud vs on-premises based on the latest Statista information

Is implementing EWS support the correct way to enable Exchange Online mailboxes today?
Are you looking at Graph API instead?

At present, EWS is our best way to enable support for both Exchange Online and on-premise installations.

Graph API has been considered and may be considered again in future, but it currently provides narrower support than EWS and lacks some functionality for desktop applications. Even with the announcement that EWS support will be removed for Exchange Online, it's still valuable in the short term for enabling access for a wide userbase and in the long term for supporting users using on-premise installations.

Depends on: 1882570
No longer depends on: 1859654
Depends on: 1892082
Depends on: 1892085
Depends on: 1895317
Depends on: 1895801
Depends on: 1896171
Depends on: 1897303
Depends on: 1899653
Depends on: 1899649
No longer blocks: 1905689
Depends on: 1905689
Depends on: 1906188
Depends on: 1906757
Depends on: 1907993
Depends on: 1907714
Depends on: 1908652
Depends on: 1910980
Depends on: 1910983
Blocks: 1911467
Depends on: 1913167
Depends on: 1908866
Depends on: 1914794
Depends on: 1914442
Depends on: 1915208
Depends on: 1915211
Depends on: 1915214
Depends on: 1915339
Depends on: 1916449
Depends on: 1916452
Depends on: 1916658
Depends on: 1917090
Depends on: 1917110
Depends on: 1917597
Depends on: 1919027
Depends on: 1920130
Depends on: 1920131
Depends on: 1920133
Depends on: 1921968
Depends on: 1921600
Depends on: 1907115
Depends on: 1922821
No longer depends on: 1914442
Depends on: 1924804
Depends on: 1924853
No longer depends on: 1924853
Depends on: 1927877
Depends on: 1929091
Depends on: 1929610
Depends on: 1930127
Depends on: 1930206
Depends on: 1931310
Depends on: 1931599
Depends on: 1931624
Depends on: 1932839
Depends on: 1933535
Depends on: 1901487
Depends on: 1934979
Depends on: 1935013
Depends on: 1935982
No longer blocks: 1936081
Depends on: 1936081
Depends on: 1936082
Depends on: 1936274
Depends on: 1936296
Depends on: 1936555
No longer blocks: 1911467
Depends on: 1911467
Depends on: 1937927
Depends on: 1941880
You need to log in before you can comment on or make changes to this bug.