
Three obvious areas are migration, connectors, and backup. The two factors make it difficult to give a definitive set of guidelines for what to look.

The introduction of the Microsoft Graph APIs as the preferred access method for data across Microsoft 365 marked the beginning of the end for EWS.
#Export email from entourage to outlook for mac for mac
Since then, EWS has been used by Microsoft in the Entourage and Outlook for Mac clients and by ISVs for many different purposes, including migration of mailbox and PST data to Exchange Online and as the foundation for backup products. In fact, when it appeared in Exchange 2007, EWS was the first successful API for Exchange that Microsoft delivered since MAPI.

Microsoft created EWS as a SOAP-based protocol to allow ISVs access to Exchange Server content.

Both steps are part of the sunset process to ease EWS out of Microsoft 365, with Microsoft noting that “ EWS is a legacy API surface that has served us well, but no longer meets the security and manageability needs of modern app development.” Figuring Out the Impact Microsoft also says that they’ll remove the ability to create new EWS apps starting on September 30, 2022. Microsoft says that the set of 25 APIs selected to go first (Figure 1) are those least used with Exchange Online.įigure 1: Exchange Web Services APIs due for deprecation by March 31, 2022 Microsoft’s October 5 announcement that they will decommission 25 Exchange Web Services (EWS) APIs by March 31, 2022, contains some clear signals that EWS is on a short runway to oblivion. EWS Sunset Will Impact Office 365 Tenants and ISVs
