Upcoming API Deprecations in Exchange Web Services for Exchange Online

Published Oct 05 2021 10:05 AM 5,577 Views

Over the last few years, we have invested heavily in Microsoft Graph to enable developers to access the rich data available in Microsoft 365. Microsoft Graph, along with OAuth 2.0, provides increased security and seamless integration with other Microsoft cloud services.

In August 2018, we announced that we were no longer going to actively invest in Exchange Web Services (EWS) APIs for Exchange Online. We also gave a strong recommendation to start migrating to Microsoft Graph for Exchange Online data access.

Today, we are announcing that we are going to remove the ability to create new EWS apps starting September 30, 2022. We are also announcing the deprecation of the 25 least used APIs of EWS for Exchange Online (as determined by the call volume into the service). We are deprecating these APIs to begin the process of reducing the surface area of the EWS protocol for maintenance and security purposes. Support for these APIs will no longer exist after deprecation.

The list of deprecated APIs is at the end of this post. We will introduce sunset headers in the response for these APIs that are marked for deprecation. As per our deprecation policy, we will decommission these APIs by March 31, 2022.

This set of deprecations is the first in a series of steps we will take as we sunset EWS for Exchange Online. Over time, we will identify additional APIs for deprecation when and where we see adequate parity with Microsoft Graph APIs.

EWS is a legacy API surface that has served us well, but no longer meets the security and manageability needs of modern app development. We strongly urge our ecosystem partners accessing Exchange Online data to migrate to Microsoft Graph APIs.

APIs scheduled for deprecation:

The_Exchange_Team_0-1633453136023.png

The Exchange Team and Microsoft Graph Team

7 Comments
Frequent Contributor

Way to go! Are there any plans to provide insights if these particular API:s are in use in our tenant(s) so we know if we will be affected of these depreciations?

Occasional Visitor

Hello, the main issue we face today is that graph API does not cover all methods covered by EWS. It will be easier to move to graph API if we did not miss some of it. We are now in a situation where we need to do heavy developments using Graph API and EWS. knowing that we will need to do some more developments when those missing features will be covered by graph API. Hope we can use Graph API fully soon. thanks

Frequent Contributor

@Renaud_B If you could add what particular methods are missing, I think that would help. Not only Microsoft but also us who talk to customers and vendors so we are aware what is missing and not. Since there is actually no "User Voice" anymore and this Tech Community is one place where Microsoft wants us to provide feedback.

Senior Member

I agree with Jonas, Microsoft needs to provide reporting so that we can easily identify the apps that are utilising the impacted EWS APIs (and EWS more generally). I don’t think we can rely on the Azure AD Sign-In logs as they only allow you to filter on Client App, which for EWS is only listed for Basic Authentication connections.

 

Also how do these changes impact the Outlook for Windows and Outlook for Mac clients, since it’s my understanding that both clients still utilise EWS to connect to Exchange Online for some functionality (especially Outlook for Mac - current version, not the new UI version which uses Microsoft Sync Technology).

Senior Member

What does that mean, "Today, we are announcing that we are going to remove the ability to create new EWS apps starting September 30, 2022."?

You mean you can't create Azure AD apps anymore with EWS permissions? You're kidding, right?

Senior Member

Completely agree wit @Jonas Back and @stukey 

 

Microsoft needs to provide reporting so that we can easily identify the apps that are utilizing the impacted EWS APIs (and EWS more generally). I don’t think we can rely on the Azure AD Sign-In logs as they only allow you to filter on Client App, which for EWS is only listed for Basic Authentication connections.

Regular Visitor

This is a major announcement and has the potential to impact every Microsoft customer from the point onward where no new EWS App Registrations are possible.

 

Right now, the Exchange Web Services API is the only way to get full-fidelity (preserving all properties) email information into and out of Office 365 (see MS-OXWSBTRF). Without this capability, 3rd Party applications addressing backup, eDiscovery, and migration (including Tenant-to-Tenant) will simply not be possible anymore! Also, even if the Graph API is extended to support the missing methods, will MSFT switch to the same "paid" model to use the Graph API as with Teams?  

 

Imagine the implications of an acquisition or divestiture scenario, where one needs to consolidate tenants and/or on- or offboard legacy data. Cost and Time implications might get enormous, and a lot of restructuring projects will never reach an ROI if suddenly the project costs and timelines multiply.

%3CLINGO-SUB%20id%3D%22lingo-sub-2813925%22%20slang%3D%22en-US%22%3EUpcoming%20API%20Deprecations%20in%20Exchange%20Web%20Services%20for%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2813925%22%20slang%3D%22en-US%22%3E%3CP%20class%3D%22%22%3EOver%20the%20last%20few%20years%2C%20we%20have%20invested%20heavily%20in%20Microsoft%20Graph%20to%20enable%20developers%20to%20access%20the%20rich%20data%20available%20in%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%20class%3D%22brand%22%3EMicrosoft%20365%3C%2FSPAN%3E.%20Microsoft%20Graph%2C%20along%20with%20OAuth%202.0%2C%20provides%20increased%20security%20and%20seamless%20integration%20with%20other%20Microsoft%20cloud%20services.%3C%2FP%3E%0A%3CP%3EIn%20August%202018%2C%20we%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fupcoming-changes-to-exchange-web-services-ews-api-for-office-365%2Fba-p%2F608055%22%20target%3D%22_blank%22%3Eannounced%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Ethat%20we%20were%20no%20longer%20going%20to%20actively%20invest%20in%20Exchange%20Web%20Services%20(EWS)%20APIs%20for%20Exchange%20Online.%20We%20also%20gave%20a%20strong%20recommendation%20to%20start%20migrating%20to%20Microsoft%20Graph%20for%20Exchange%20Online%20data%20access.%3C%2FP%3E%0A%3CP%20class%3D%22%22%3EToday%2C%20we%20are%20announcing%20that%20we%20are%20going%20to%20remove%20the%20ability%20to%20create%20new%20EWS%20apps%20starting%20September%2030%2C%202022.%26nbsp%3BWe%20are%20also%20announcing%20the%20deprecation%20of%20the%2025%20least%20used%20APIs%20of%20EWS%20for%20Exchange%20Online%20(as%20determined%20by%20the%20call%20volume%20into%20the%20service).%20We%20are%20deprecating%20these%20APIs%20to%20begin%20the%20process%20of%20reducing%20the%20surface%20area%20of%20the%20EWS%20protocol%20for%20maintenance%20and%20security%20purposes.%20Support%20for%20these%20APIs%20will%20no%20longer%20exist%20after%20deprecation.%3C%2FP%3E%0A%3CP%3EThe%20list%20of%20deprecated%20APIs%20is%20at%20the%20end%20of%20this%20post.%20We%20will%20introduce%20sunset%20headers%20in%20the%20response%20for%20these%20APIs%20that%20are%20marked%20for%20deprecation.%20As%20per%20our%20deprecation%20policy%2C%20we%20will%20decommission%20these%20APIs%20by%20March%2031%2C%202022.%3C%2FP%3E%0A%3CP%3EThis%20set%20of%20deprecations%20is%20the%20first%20in%20a%20series%20of%20steps%20we%20will%20take%20as%20we%20sunset%20EWS%20for%20Exchange%20Online.%20Over%20time%2C%20we%20will%20identify%20additional%20APIs%20for%20deprecation%20when%20and%20where%20we%20see%20adequate%20parity%20with%20Microsoft%20Graph%20APIs.%3C%2FP%3E%0A%3CP%3EEWS%20is%20a%20legacy%20API%20surface%20that%20has%20served%20us%20well%2C%20but%20no%20longer%20meets%20the%20security%20and%20manageability%20needs%20of%20modern%20app%20development.%20We%20strongly%20urge%20our%20ecosystem%20partners%20accessing%20Exchange%20Online%20data%20to%20migrate%20to%20Microsoft%20Graph%20APIs.%3C%2FP%3E%0A%3CP%3EAPIs%20scheduled%20for%20deprecation%3A%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22The_Exchange_Team_0-1633453136023.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F315349iDF0FC04AD24F5B3F%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22The_Exchange_Team_0-1633453136023.png%22%20alt%3D%22The_Exchange_Team_0-1633453136023.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20color%3D%22%23FF6600%22%3EThe%20Exchange%20Team%20and%20Microsoft%20Graph%20Team%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-2813925%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EToday%2C%20we%20are%20announcing%20that%20we%20are%20going%20to%20remove%20the%20ability%20to%20create%20new%20Exchange%20Web%20Services%20apps%20starting%20September%2030%2C%202022.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2813925%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAnnouncements%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDevelopment%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2814236%22%20slang%3D%22en-US%22%3ERe%3A%20Upcoming%20API%20Deprecations%20in%20Exchange%20Web%20Services%20for%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2814236%22%20slang%3D%22en-US%22%3E%3CP%3EWay%20to%20go!%20Are%20there%20any%20plans%20to%20provide%20insights%20if%20these%20particular%20API%3As%20are%20in%20use%20in%20our%20tenant(s)%20so%20we%20know%20if%20we%20will%20be%20affected%20of%20these%20depreciations%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2816350%22%20slang%3D%22en-US%22%3ERe%3A%20Upcoming%20API%20Deprecations%20in%20Exchange%20Web%20Services%20for%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2816350%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%20the%20main%20issue%20we%20face%20today%20is%20that%20graph%20API%20does%20not%20cover%20all%20methods%20covered%20by%20EWS.%20It%20will%20be%20easier%20to%20move%20to%20graph%20API%20if%20we%20did%20not%20miss%20some%20of%20it.%20We%20are%20now%20in%20a%20situation%20where%20we%20need%20to%20do%20heavy%20developments%20using%20Graph%20API%20and%20EWS.%20knowing%20that%20we%20will%20need%20to%20do%20some%20more%20developments%20when%20those%20missing%20features%20will%20be%20covered%20by%20graph%20API.%20Hope%20we%20can%20use%20Graph%20API%20fully%20soon.%20thanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2816618%22%20slang%3D%22en-US%22%3ERe%3A%20Upcoming%20API%20Deprecations%20in%20Exchange%20Web%20Services%20for%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2816618%22%20slang%3D%22en-US%22%3E%3CP%3EI%20agree%20with%20Jonas%2C%20Microsoft%20needs%20to%20provide%20reporting%20so%20that%20we%20can%20easily%20identify%20the%20apps%20that%20are%20utilising%20the%20impacted%20EWS%20APIs%20(and%20EWS%20more%20generally).%20I%20don%E2%80%99t%20think%20we%20can%20rely%20on%20the%20Azure%20AD%20Sign-In%20logs%20as%20they%20only%20allow%20you%20to%20filter%20on%20Client%20App%2C%20which%20for%20EWS%20is%20only%20listed%20for%20Basic%20Authentication%20connections.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20how%20do%20these%20changes%20impact%20the%20Outlook%20for%20Windows%20and%20Outlook%20for%20Mac%20clients%2C%20since%20it%E2%80%99s%20my%20understanding%20that%20both%20clients%20still%20utilise%20EWS%20to%20connect%20to%20Exchange%20Online%20for%20some%20functionality%20(especially%20Outlook%20for%20Mac%20-%20current%20version%2C%20not%20the%20new%20UI%20version%20which%20uses%20Microsoft%20Sync%20Technology).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2827435%22%20slang%3D%22en-US%22%3ERe%3A%20Upcoming%20API%20Deprecations%20in%20Exchange%20Web%20Services%20for%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2827435%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20does%20that%20mean%2C%20%22Today%2C%20we%20are%20announcing%20that%20we%20are%20going%20to%20remove%20the%20ability%20to%20create%20new%20EWS%20apps%20starting%20September%2030%2C%202022.%22%3F%3C%2FP%3E%3CP%3EYou%20mean%20you%20can't%20create%20Azure%20AD%20apps%20anymore%20with%20EWS%20permissions%3F%20You're%20kidding%2C%20right%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2833797%22%20slang%3D%22en-US%22%3ERe%3A%20Upcoming%20API%20Deprecations%20in%20Exchange%20Web%20Services%20for%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2833797%22%20slang%3D%22en-US%22%3E%3CP%3ECompletely%20agree%20wit%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F19218%22%20target%3D%22_blank%22%3E%40Jonas%20Back%3C%2FA%3E%26nbsp%3Band%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F272511%22%20target%3D%22_blank%22%3E%40stukey%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EMicrosoft%20needs%20to%20provide%20reporting%20so%20that%20we%20can%20easily%20identify%20the%20apps%20that%20are%20utilizing%26nbsp%3Bthe%20impacted%20EWS%20APIs%20(%3CSTRONG%3Eand%20EWS%20more%20generally%3C%2FSTRONG%3E).%20%3CSTRONG%3EI%20don%E2%80%99t%20think%20we%20can%20rely%20on%20the%20Azure%20AD%20Sign-In%20logs%20as%20they%20only%20allow%20you%20to%20filter%20on%20Client%20App%3C%2FSTRONG%3E%2C%20which%20for%20EWS%20is%20only%20listed%20for%20Basic%20Authentication%20connections.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2843877%22%20slang%3D%22en-US%22%3ERe%3A%20Upcoming%20API%20Deprecations%20in%20Exchange%20Web%20Services%20for%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2843877%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EThis%20is%20a%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3Emajor%20announcement%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3Band%20has%20the%20potential%20to%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3Eimpact%20every%26nbsp%3BMicrosoft%20customer%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3Bfrom%20the%20point%20onward%20where%20no%20new%20EWS%20App%20Registrations%20are%20possible.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ERight%20now%2C%20the%20Exchange%20Web%20Services%20API%20is%20the%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3Eonly%20way%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3Bto%20get%20full-fidelity%20(preserving%20all%20properties)%20email%20information%20into%20and%20out%20of%20Office%20365%26nbsp%3B(see%20MS-OXWSBTRF)%3C%2FSPAN%3E%3CSTRONG%3E.%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FSTRONG%3E%3CSPAN%3EWithout%20this%20capability%2C%203rd%20Party%20applications%20addressing%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3Ebackup%2C%20eDiscovery%2C%20and%20migration%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FSTRONG%3E%3CSPAN%3E(including%20Tenant-to-Tenant)%3C%2FSPAN%3E%3CSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FSTRONG%3E%3CSPAN%3Ewill%20simply%20not%20be%20possible%20anymore!%20Also%2C%20even%20if%20the%20Graph%20API%20is%20extended%20to%20support%20the%20missing%20methods%2C%20will%20MSFT%20switch%20to%20the%20same%20%22paid%22%20model%20to%20use%20the%20Graph%20API%20as%20with%20Teams%3F%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EImagine%20the%20implications%20of%20an%20acquisition%20or%20divestiture%20scenario%2C%20where%20one%20needs%20to%20consolidate%20tenants%20and%2For%20on-%20or%20offboard%20legacy%20data.%20Cost%20and%20Time%20implications%20might%20get%20enormous%2C%20and%20a%20lot%20of%20restructuring%20projects%20will%20never%20reach%20an%20ROI%20if%20suddenly%20the%20project%20costs%20and%20timelines%20multiply.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Co-Authors
Version history
Last update:
‎Oct 05 2021 10:05 AM
Updated by: