Firstly, Exchange *protocol* is not the same as Exchange *server* or Exchange *account*.
Firstly, Exchange *protocol*(EWS) is not the same as Exchange *server* or Exchange *account*.
The Microsoft Exchange Web Services (EWS) protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
The Microsoft Exchange Web Services ™(EWS) protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
Microsoft stopped updating the EWS libraries [in 2016](https://github.com/OfficeDev/ews-java-api).
Microsoft stopped updating the EWS libraries [in 2016](https://github.com/OfficeDev/ews-java-api).
So, it makes little sense to add this protocol anymore.
So, it makes little sense to add this protocol anymore.
@ -797,7 +797,7 @@ You can use a Microsoft Exchange account if it is accessible via IMAP, which is
See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
Note that the desciption of FairEmail starts with the remark
Note that the desciption of FairEmail starts with the remark
that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
that non-standard protocols, like Microsoft Exchange Web Services ™and Microsoft ActiveSync™ are not supported.
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040)
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040)
for the Microsoft documentation about configuring an email client.
for the Microsoft documentation about configuring an email client.
@ -806,7 +806,7 @@ There is also a section about common connection errors and solutions.
Some older Exchange server versions have a bug causing empty message and corrupt attachments.
Some older Exchange server versions have a bug causing empty message and corrupt attachments.
Please see [this FAQ](#user-content-faq110) for a workaround.
Please see [this FAQ](#user-content-faq110) for a workaround.
Please see [this FAQ](#user-content-faq133) about ActiveSync support.
Please see [this FAQ](#user-content-faq133) about ActiveSync ™support.
Please see [this FAQ](#user-content-faq111) about OAuth support.
Please see [this FAQ](#user-content-faq111) about OAuth support.
@ -3939,15 +3939,16 @@ Android might rate limit the notification sound, which can cause some new messag
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported.
The Microsoft Exchange ActiveSync ™ protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and Microsoft doesn't give out licenses anymore.
For this reason you won't find many, if any, other email clients supporting ActiveSync.
Therefore, it isn't possible to support ActiveSync ™ anymore.
For this same reason, you won't find many, if any, other email clients supporting ActiveSync ™.
Note that the desciption of FairEmail starts with the remark
Note that the desciption of FairEmail starts with the remark
that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
that non-standard protocols, like Microsoft Exchange Web Services ™and Microsoft ActiveSync™ are not supported.