2
edits
Thunderbird:Exchange: Difference between revisions
on-premises, not on-premise
m (c/Graph API/Microsoft API/ (in most places)) |
(on-premises, not on-premise) |
||
| Line 105: | Line 105: | ||
Microsoft EWS is a legacy SOAP-based API for accessing Exchange data, while Microsoft Graph API is a modern, RESTful API for accessing a wide range of Office365 services, including Exchange data. | Microsoft EWS is a legacy SOAP-based API for accessing Exchange data, while Microsoft Graph API is a modern, RESTful API for accessing a wide range of Office365 services, including Exchange data. | ||
The EWS API is being partly retired by Microsoft in favor of Graph API. However, there is still a whole year before the EWS API gets retired, '''and''' this only impacts domains hosted on Microsoft's Office365 cloud. '''On- | The EWS API is being partly retired by Microsoft in favor of Graph API. However, there is still a whole year before the EWS API gets retired, '''and''' this only impacts domains hosted on Microsoft's Office365 cloud. '''On-premises instances of EWS are not subject to this retirement deadline.''' | ||
= Microsoft hosted vs. Self hosted Exchange servers = | = Microsoft hosted vs. Self hosted Exchange servers = | ||
| Line 139: | Line 139: | ||
== Self hosted scenario - less common == | == Self hosted scenario - less common == | ||
'''TLDR - self hosted (aka on- | '''TLDR - self hosted (aka on-premises) works with password/basic auth, but NTLM and OAuth are not yet supported.''' | ||
You can tell from this [https://searchfox.org/comm-central/source/mailnews/base/src/OAuth2Providers.sys.mjs OAuth2Providers.sys.mjs] file that there are no domains correlating to self hosted mail servers, meaning Thunderbird won’t know anything about an Exchange server hosted within non-cloud infrastructure so won’t be able to complete an OAuth handshake with this server. | You can tell from this [https://searchfox.org/comm-central/source/mailnews/base/src/OAuth2Providers.sys.mjs OAuth2Providers.sys.mjs] file that there are no domains correlating to self hosted mail servers, meaning Thunderbird won’t know anything about an Exchange server hosted within non-cloud infrastructure so won’t be able to complete an OAuth handshake with this server. | ||
To ease this painful situation of a self hosted server being usable in Thunderbird, Thunderbird can consume these handshake details via an add-on. So now it’s possible for '''a mail server administrator to create a customized (to their server) add-on that provides the OAuth handshake details of their server which their users can install, or that can be rolled out to users via enterprise policy.''' | To ease this painful situation of a self hosted server being usable in Thunderbird, Thunderbird can consume these handshake details via an add-on. So now it’s possible for '''a mail server administrator to create a customized (to their server) add-on that provides the OAuth handshake details of their server which their users can install, or that can be rolled out to users via enterprise policy.''' | ||