Upcoming API Deprecations in Exchange Web Services for Exchange Online

Published Oct 05 2021 10:05 AM 35.7K Views

Update 11/3/2021: We have edited this post for clarity based on customer feedback.

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 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 March 31, 2022.

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.

In the coming months we will send Message Center posts to tenants we can see are using these low volume, and now deprecated APIs.

Over time, we will identify additional APIs for deprecation when and where we see adequate parity with Microsoft Graph APIs. We are also working hard on addressing feature gaps and building parity between EWS and Microsoft Graph APIs. We strongly urge our ecosystem partners accessing Exchange Online data to migrate to Microsoft Graph APIs.

We will also remove the ability to register new apps in Azure with EWS permissions starting September 30, 2022. Apps registered before this date, any API not mentioned in this, or subsequent announcements, will not be impacted.

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

36 Comments
%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%3CLINGO-SUB%20id%3D%22lingo-sub-2816446%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-2816446%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1176742%22%20target%3D%22_blank%22%3E%40Renaud_B%3C%2FA%3E%26nbsp%3BIf%20you%20could%20add%20what%20particular%20methods%20are%20missing%2C%20I%20think%20that%20would%20help.%20Not%20only%20Microsoft%20but%20also%20us%20who%20talk%20to%20customers%20and%20vendors%20so%20we%20are%20aware%20what%20is%20missing%20and%20not.%20Since%20there%20is%20actually%20no%20%22User%20Voice%22%20anymore%20and%20this%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Foffice%2Fuservoice-pages-430e1a78-e016-472a-a10f-dc2a3df3450a%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3ETech%20Community%20is%20one%20place%20where%20Microsoft%20wants%20us%20to%20provide%20feedback%3C%2FA%3E.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2855967%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-2855967%22%20slang%3D%22en-US%22%3E%3CP%3EI%20think%20it%20would%20be%20good%20for%20Microsoft%20to%20provide%20some%20more%20clarification%20on%20the%20following%20statement%20%22%3CSPAN%3EToday%2C%20we%20are%20announcing%20that%20we%20are%20going%20to%20remove%20the%20ability%20to%20create%20new%20EWS%20apps%20starting%20September%2030%2C%202022.%3C%2FSPAN%3E%22.%20Does%20it%20mean%20we%20can%20no%20longer%20add%20the%20%22EWS.AccessAsUser.All%22%20permission%20to%20new%20Azure%20Active%20Directory%20apps%3F%20If%20so%2C%20does%20it%20apply%20to%20both%20UI%20and%20API%20operations%3F%20How%20does%20Microsoft%20propose%20developers%20deal%20with%20needing%20to%20support%20both%20Exchange%20Online%20and%20Exchange%20On-premises%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2871684%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-2871684%22%20slang%3D%22en-US%22%3E%3CP%3EFor%20those%20looking%20for%20a%20text-based%20list%20of%20these%20APIs%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECopyFolder%3CBR%20%2F%3ECreateUMPrompt%3CBR%20%2F%3EDeleteBookingService%3CBR%20%2F%3EDeleteBookingStaff%3CBR%20%2F%3EDeleteUMPrompts%3CBR%20%2F%3EFindAvailableMeetingTimes%3CBR%20%2F%3EFindMessageTrackingReport%3CBR%20%2F%3EGetDiscoverySearchConfiguration%3CBR%20%2F%3EGetPeopleInsights%3CBR%20%2F%3EGetUMCallDataRecords%3CBR%20%2F%3EGetUMCallSummary%3CBR%20%2F%3EGetUMPin%3CBR%20%2F%3EGetUMPromptNames%3CBR%20%2F%3ENewBookingMailbox%3CBR%20%2F%3EPerformReminderAction%3CBR%20%2F%3EPlayOnPhone%3CBR%20%2F%3ERemoveDelegate%3CBR%20%2F%3ERemoveImGroup%3CBR%20%2F%3EResetUMMailbox%3CBR%20%2F%3ESetBookingCalendarPublishing%3CBR%20%2F%3ESetUserPhoto%3CBR%20%2F%3EStartXrmSession%3CBR%20%2F%3EUpdateBookingCustomer%3CBR%20%2F%3EUpdateDelegate%3CBR%20%2F%3EUpgradeDistributionGroup%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2902173%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-2902173%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3E%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%2C%26nbsp%3B%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F435615%22%20target%3D%22_blank%22%3E%40Tom_R_%3C%2FA%3E%26nbsp%3B%2C%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%3B%20-%20We%20will%20send%20Message%20Center%26nbsp%3Bposts%20to%20impacted%20tenants%20with%20a%20list%20of%20applications%20using%20any%20of%20these%2025%20EWS%20APIs%20mentioned%20in%20the%20blog%20post.%20As%20for%20the%20question%20on%20Outlook%20usage%20%E2%80%93%20currently%20we%20have%20announced%20only%20a%20small%20subset%20of%20EWS%20APIs%20for%20upcoming%20deprecation%2C%20not%20EWS%20all%20up.%20Outlook%20very%20much%20still%20uses%20EWS%2C%20but%20none%20of%20the%20APIs%20included%20in%20this%20announcement.%20Outlook%20(win%20and%20mac)%20moving%20off%20EWS%20is%20beyond%20the%20scope%20of%20this%20announcement.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F953061%22%20target%3D%22_blank%22%3E%40MichelZCF%3C%2FA%3E%26nbsp%3B%2C%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1188388%22%20target%3D%22_blank%22%3E%40WGroenestein%3C%2FA%3E%26nbsp%3B-%20As%20mentioned%20in%20the%20blog%2C%20creation%20of%20new%20apps%20using%20EWS%20is%20planned%20to%20be%20blocked%20from%20September%2030th%2C%202022.%20So%2C%20yes%2C%20new%20Azure%20AD%20apps%20can%E2%80%99t%20be%20created%20using%20EWS%20permission%20scopes.%20Existing%20apps%20using%20EWS%20apps%20permissions%20will%20however%20continue%20to%20function%20beyond%20this%20date%20%26amp%3B%20not%20be%20impacted.%20This%20is%20only%20relevant%20for%20Exchange%20Online.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EApps%20running%20on%20Exchange%20On-Prem%20won%E2%80%99t%20be%20affected%20by%20any%20of%20this%20announcement%20and%20will%20not%20need%20to%20change.%26nbsp%3B%3C%2FSPAN%3ENew%20solutions%20should%20actively%20look%20into%20on-boarding%20to%20Microsoft%20Graph%20directly%20for%20Exchange%20Online.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2919543%22%20slang%3D%22de-DE%22%3ESubject%3A%20Upcoming%20API%20Deprecations%20in%20Exchange%20Web%20Services%20for%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2919543%22%20slang%3D%22de-DE%22%3E%3CP%3EFrom%20my%20Point%20of%20View%20the%20impact%20of%20this%20is%20huge.%20In%20my%20little%20world%20almost%20every%203rd%20Party%20ExO%20solution%20I%20can%20think%20of%20uses%20these%20EWS%20permissions.%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20it%20comes%20to%20the%20EWS%20API%20itself%20(which%20will%20still%20be%20there%20but%20you%20cant%20register%20the%20app)%20and%20the%20ability%20to%20just%20replace%20it%20with%20graph%20API%20is%20just%20not%20true.%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20believed%20in%20graphAPI%20as%20a%20replacement%20for%20EWS%20in%202018%20and%20ended%20up%20with%20a%20lot%20of%20issues%20which%20-%20to%20my%20knowledge%20-%20are%20still%20not%20sorted.%20EWS%20is%20complete.%20graphAPI%20is%20not%20when%20it%20comes%20to%20a%20full%20featured%20Exchange%20API.%3C%2FP%3E%3CP%3ESo%2C%20when%20you%20depend%20on%20streaming%20subscriptions%20and%20full%20featured%20object%20handling%20(create%2C%20update%2C%20delete%20notes%2C%20contacts%2C%20appointments%2C%20stickynotes%20and%20folders%2C%20etc)%3C%2FP%3E%3CP%3Eyou%20end%20up%20with%20a%20mixture%20of%20graphAPI%20and%20Outlook%20REST%20API%20and%20still%20miss%20features.%26nbsp%3B%20This%20can%20all%20be%20true%20because%20of%20my%20limited%20knowledge%2C%20so%20if%20anyone%20at%20MS%20is%20reading%20this%3A%3C%2FP%3E%3CP%3Ea%20real%20migration%20guide%20which%20EWS%20feature%20can%20be%20(fully)%20replaced%20with%20which%20graphAPI%20feature%20and%20how%20to%20do%20it%20with%20samples%20and%20stuff%20would%20be%20incredibly%20great.%3C%2FP%3E%3CP%3EAlso%20a%20clear%20statement%20what's%20just%20not%20available%20atm.%20Or%20take%20the%20easy%20way%20and%20just%20drop%20the%20idea%20of%20deprecating%20the%20EWS%20APP%20registration.%3C%2FP%3E%3C%2FLINGO-BODY%3E%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%3E%3CSTRONG%3EUpdate%2011%2F3%2F2021%3A%3C%2FSTRONG%3E%20We%20have%20edited%20this%20post%20for%20clarity%20based%20on%20customer%20feedback.%3C%2FP%3E%0A%3CP%3EOver%20the%20last%20few%20years%2C%20we%20have%20invested%20heavily%20in%20Microsoft%20Graph%20to%20enable%20developers%20to%20access%20the%20rich%20data%20available%20in%26nbsp%3BMicrosoft%20365.%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%26nbsp%3B%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%26nbsp%3Bthat%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%3EToday%20we%20are%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%2C%20and%20only%20these%20APIs%2C%20by%20March%2031%2C%202022.%3C%2FP%3E%0A%3CP%3EIn%20the%20coming%20months%20we%20will%20send%20Message%20Center%20posts%20to%20tenants%20we%20can%20see%20are%20using%20these%20low%20volume%2C%20and%20now%20deprecated%20APIs.%3C%2FP%3E%0A%3CP%3EOver%20time%2C%20we%20will%20identify%20additional%20APIs%20for%20deprecation%20when%20and%20where%20we%20see%20adequate%20parity%20with%20Microsoft%20Graph%20APIs.%20We%20are%20also%20working%20hard%20on%20addressing%20feature%20gaps%20and%20building%20parity%20between%20EWS%20and%20Microsoft%20Graph%20APIs.%20We%20strongly%20urge%20our%20ecosystem%20partners%20accessing%20Exchange%20Online%20data%20to%20migrate%20to%20Microsoft%20Graph%20APIs.%3C%2FP%3E%0A%3CP%3EWe%20will%20also%20remove%20the%20ability%20to%20register%20new%20apps%20in%20Azure%20with%20EWS%20permissions%20starting%20September%2030%2C%202022.%20Apps%20registered%20before%20this%20date%2C%20any%20API%20not%20mentioned%20in%20this%2C%20or%20subsequent%20announcements%2C%20will%20%3CEM%3Enot%3C%2FEM%3E%20be%20impacted.%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-2871769%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-2871769%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F324116%22%20target%3D%22_blank%22%3E%40The_Exchange_Team%3C%2FA%3E%26nbsp%3BCare%20to%20comment%20on%20the%20request%20for%20providing%20more%20insights%20in%20which%20APIs%20used%20by%20what%3F%20Or%20do%20we%20have%20to%20guess%3F%20%3Asmiling_face_with_smiling_eyes%3A%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2929649%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-2929649%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20very%20techno-ignorant%3B%20I%20have%20a%20solo%20counseling%20practice%20and%20I%20just%20want%20my%20MS365%20Business%20to%20function.%20I%20have%20had%20trouble%20linking%20the%20correct%20email%20account%20with%20the%20Zoom%20Add-In%20for%20Outlook.%20Randomly%2C%20emails%20do%20not%20go%20out%20to%20attendees.%20I%20just%20want%20to%20focus%20on%20my%20clients...Please%20Get%20All%20This%20Launched%20and%20FIXED%20so%20ALL%20your%20consumers%20can%20access%20and%20use%20All%20the%20features%20for%20which%20we%20are%20paying.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2930368%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-2930368%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F731489%22%20target%3D%22_blank%22%3E%40Abheek_Das%3C%2FA%3E%2C%20thank%20you%20for%20providing%20extra%20info%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2931120%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-2931120%22%20slang%3D%22en-US%22%3E%3CP%3ESuper.%20I%20only%20use%20Set-UserPhoto%20via%20Powershell%2040%20times%20a%20day%20via%20a%20profile%20photo%20update%20process.%20%3A(%3C%2Fimg%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2932150%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-2932150%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20a%20small%20business%20customer%2C%20we%20chose%20Exchange%20Online%20to%20meet%20our%20mail%20client%20needs%20rather%20than%20using%20on-prem%20Exchange.%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3BOur%20entire%20business%20depends%20and%20runs%20on%20e-mail.%26nbsp%3B%20I%20would%20hope%20that%20Microsoft%20would%20evaluate%20these%20changes%20and%20publish%20information%20as%20to%20exactly%20how%20this%20is%20going%20to%20affect%20our%20mail%20clients.%20Minor%20changes%20have%20had%20drastic%20impacts%20on%20our%20mail%20clients%20in%20the%20past.%26nbsp%3B%20In%20many%20cases%2C%20the%20small%20business%20customer%20is%20only%20using%20the%20mail%20and%20we%20would%20not%20know%20how%20might%20impact%20our%20mails%20system%2C%20without%20paying%20our%20IT%20contractors%20overtime%20to%20figure%20it%20out.%26nbsp%3B%20Please%20provide%20documentation%20that%20is%20customer-centered%20and%20please%20do%20not%20make%20any%20changes%20that%20prevent%20our%20clients%20from%20connecting%20to%20Exchange%20and%20performing%20the%20expected%20tasks%20(Using%20Mail%2C%20Calendar%2C%20Contacts%2C%20Shared%20Folders%2C%20Delegation%2C%20etc.)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2934033%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-2934033%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20officially%20requesting%20the%20ability%20to%20check%20tenants%20for%20all%20calls%20that%20include%20EWS%20and%20Microsoft%20Graph%2C%20than%20you%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2936547%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-2936547%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149115%22%20target%3D%22_blank%22%3E%40Greg%20Taylor%20-%20EXCHANGE%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%E2%80%98s%20not%20about%20net%20new%20apps%2C%20we%20gave%20a%20mature%20app%20that%20our%20custoners%20want%20to%20use.%20They%20need%20their%20own%20app%20regs%20ro%20be%20able%20to%20use%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2936741%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-2936741%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149115%22%20target%3D%22_blank%22%3E%40Greg%20Taylor%20-%20EXCHANGE%3C%2FA%3E%26nbsp%3Bwe%20use%20the%20Graph%20API%20Ecosystem%20to%20integrate%20our%20software's%20scheduling%20module%20with%20published%20calendars%20created%20for%20our%20customers.%20I%20am%20almost%20certain%20that%20we%20are%20strictly%20using%20Graph%20API%20but%20would%20like%20to%20verify%20it.%20Thanks.%26nbsp%3B%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2939014%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-2939014%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F324116%22%20target%3D%22_blank%22%3E%40The_Exchange_Team%3C%2FA%3E%26nbsp%3BSet-UserPhoto%20was%20a%20one%20line%20command%20that%20simplified%20the%20overly%20complex%20photo%20sync%20process.%20I've%20spent%20hours%20trying%20to%20get%20the%20GraphAPI%20to%20work%20for%20this%20in%20Powershell%20and%20keep%20getting%20401%20errors.%26nbsp%3B%5B30%2C1%3A%20Invoke-RestMethod%5D%20The%20remote%20server%20returned%20an%20error%3A%20(401)%20Unauthorized.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20permissions%20are%20needed%20for%20the%20App%20Registration%20and%20the%20Powershell%20connection%20scope%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EConnect-MgGraph%20-Scopes%20%22User.ReadWrite.All%22%3C%2FP%3E%3CP%3E%24AzAppSecret%20%3D%20'%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23'%3CBR%20%2F%3E%24AzAppId%20%3D%20'%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23'%3CBR%20%2F%3E%24AzTenantId%20%3D%20'%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23'%3C%2FP%3E%3CP%3E%23%20Request%20token%3CBR%20%2F%3E%24tokenRequestBody%20%3D%20%40%7B%3C%2FP%3E%3CP%3EGrant_Type%20%3D%20%22client_credentials%22%3CBR%20%2F%3EScope%20%3D%20%22%3CA%20href%3D%22https%3A%2F%2Fgraph.microsoft.com%2F.default%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgraph.microsoft.com%2F.default%3C%2FA%3E%22%3CBR%20%2F%3EClient_Id%20%3D%20%24AzAppID%3CBR%20%2F%3EClient_Secret%20%3D%20%24AzAppSecret%3CBR%20%2F%3E%7D%3C%2FP%3E%3CP%3E%24tokenRequestUri%20%3D%20%5BString%5D%3A%3AFormat('%3CA%20href%3D%22https%3A%2F%2Flogin.microsoftonline.com%2F%7B0%7D%2Foauth2%2Fv2.0%2Ftoken%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Flogin.microsoftonline.com%2F%7B0%7D%2Foauth2%2Fv2.0%2Ftoken%3C%2FA%3E'%2C%20%24AzTenantId)%3CBR%20%2F%3E%24tokenResponse%20%3D%20Invoke-RestMethod%20-Uri%20%24tokenRequestUri%20-Method%20'POST'%20-Body%20%24tokenRequestBody%20-ErrorAction%20Stop%3CBR%20%2F%3E%24accessToken%20%3D%20%24tokenResponse.access_token%3CBR%20%2F%3E%24AzUserUPN%20%3D%20'username%40example.com'%3CBR%20%2F%3E%24AzUserImage%20%3D%20'S%3A%5Csamplepic.jpg'%3C%2FP%3E%3CP%3E%24uri%20%3D%20%5BString%5D%3A%3AFormat('%3CA%20href%3D%22https%3A%2F%2Fgraph.microsoft.com%2Fv1.0%2Fusers%2F%7B0%7D%2Fphoto%2F%24value%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgraph.microsoft.com%2Fv1.0%2Fusers%2F%7B0%7D%2Fphoto%2F%24value%3C%2FA%3E'%2C%20%24AzUserUPN)%3CBR%20%2F%3E%24Headers%20%3D%20%40%7B%3CBR%20%2F%3E'Authorization'%20%3D%20%5BString%5D%3A%3AFormat('Bearer%20%7B0%7D'%2C%20%24accessToken)%3CBR%20%2F%3E'Content-Type'%20%3D%20'image%2Fjpeg'%3CBR%20%2F%3E%7D%3C%2FP%3E%3CP%3EInvoke-RestMethod%20-Method%20Put%20-Uri%20%24uri%20-InFile%20%24AzUserImage%20-Headers%20%24Headers%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2940167%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-2940167%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F659709%22%20target%3D%22_blank%22%3E%40MGSpaceCaptain%3C%2FA%3E%26nbsp%3B%2C%20in%20your%20code%2C%20I%20don't%20see%20what%20'Connect-MSGraph%20-Scopes%20%22User.ReadWrite.All%22'%20is%20doing%2C%20it's%20just%20there%20at%20the%20start%2C%20but%20then%20everything%20else%20is%20an%20app%20getting%20it's%20own%20confidential%20client%20access%20token%20using%20a%20client%20secret.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrom%20here%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fgraph%2Fapi%2Fprofilephoto-update%3Fview%3Dgraph-rest-1.0%26amp%3Btabs%3Dhttp%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EUpdate%20profilephoto%20-%20Microsoft%20Graph%20v1.0%20%7C%20Microsoft%20Docs%3C%2FA%3E%26nbsp%3B-%20it%20says%20that%20if%20an%20app%20will%20need%20to%20update%20any%20user's%20photo%2C%20it%20needs%20to%20have%20%22User.ReadWrite.All%22%20application%20permission.%26nbsp%3B%20So%2C%20I%20think%20that's%20where%20you're%20getting%20the%20idea%20to%20do%20the%20Connect-MSGraph%20step.%26nbsp%3B%20Instead%2C%20go%20to%20your%20app%20registration%20in%20the%20Azure%20AD%20portal%20and%20grant%20it%20the%20User.ReadWrite.All%20application%20permission%20and%20grant%20it%20the%20consent%20there%20too.%26nbsp%3B%20Then%20just%20omit%20the%20Connect-MSGraph%20step%20from%20your%20code%2C%20as%20the%20scope%20will%20already%20be%20automatically%20granted%20(via%20the%20granted%2Fconsented%20API%20application%20permission).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEdit%3A%20PS.%26nbsp%3B%20You%20could%20give%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FJeremyTBradshaw%2FMSGraphPSEssentials%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3EMSGraphPSEssentials%3C%2FA%3E%20a%20try%20for%20your%20task%20at%20hand.%26nbsp%3B%20It%20would%20be%20an%20easy%20way%20for%20you%20to%20switch%20from%20client%20secret%20to%20certificates%2C%20while%20also%20making%20it%20easy%20to%20get%20your%20app's%20access%20token%20and%20then%20submit%20your%20request(s)%20to%20update%20the%20photo(s).%26nbsp%3B%20If%20you%20have%20trouble%2C%20I%20can%20help%20through%20a%20GitHub%20discussion%20(at%20no%20guaranteed%20pace%20of%20course).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2941633%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-2941633%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20use%20EWS%20in%20a%20daemon%20to%20sync%20all%20our%20user%E2%80%99s%20appointments%20and%20tasks%20to%20exchange.%20%26nbsp%3BUsing%20EWS%20this%20works%20easily%20using%20impersonation.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGraph%20only%20allows%20delegated%20authorization%20to%20access%2Fmodify%20tasks.%20At%20several%20government%20clients%20we%20are%20not%20allowed%20to%20store%20user%20credentials%20or%20request%20permission%20from%20users.%20Graph%20docs%20say%20the%20only%20way%20to%20possibly%20do%20this%20is%20to%20use%20ROCP%20auth.%20Then%20it%20says%20%E2%80%9Cdon%E2%80%99t%20use%20ROCP%20auth.%E2%80%9D%20%26nbsp%3BUnless%20access%20to%20tasks%20is%20allowed%20on%20application%20authorization%20we%20can%20not%20properly%20synchronize%20tasks.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EThere%20are%20other%20similar%20areas.%20%26nbsp%3BUntil%20Graph%20has%20true%20parity%20in%20these%20areas%20it%20seems%20wrong%20to%20prevent%20new%20app%20registrations.%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2941776%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-2941776%22%20slang%3D%22en-US%22%3E%3CP%3E1.%26nbsp%3BIs%20there%20any%20roadmap%20for%20Graph%20API%20to%20gain%20feature%20parity%20with%20EWS%3F%3CBR%20%2F%3E2.%26nbsp%3B%3CSPAN%3EFrom%20the%20statement%3A%3C%2FSPAN%3E%3C%2FP%3E%3CBLOCKQUOTE%3E%3CP%3E%3CSPAN%3EToday%2C%20we%20are%20announcing%20that%20we%20are%20going%20to%20remove%20the%20ability%20to%20create%20new%20EWS%20apps%20starting%20September%2030%2C%202022.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3EDoes%20it%20mean%20we%20can%20no%20longer%20add%20%22full_access_as_app%22%20permission%20to%20new%20AD%20apps%20through%20the%20following%20API%20%3F%3C%2FP%3E%3CBLOCKQUOTE%3E%3CP%3E%3CSPAN%3E%3CSPAN%20class%3D%22%22%3EPOST%20%2FservicePrincipals%2F%7Bid%7D%2FappRoleAssignedTo%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2942079%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-2942079%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheck%20out%20this%20open%20letter%20to%20Microsoft%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.linkedin.com%2Fpulse%2Fsubject-do-recent-exchange-teams-announcements-signal-peter-kozak%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.linkedin.com%2Fpulse%2Fsubject-do-recent-exchange-teams-announcements-signal-peter-kozak%2F%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2956793%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-2956793%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20working%20on%20EWS%20%26gt%3B%20Graph%20roadmap%2Fcomparisons%2C%20all%20of%20that.%20We'll%20have%20more%20on%20that%20in%20the%20future.%20We're%20also%20working%20on%20answering%20the%20more%20specific%20questions%20asked%20above%2C%20so%20look%20out%20for%20those%20soon.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2964865%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-2964865%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EI%20have%20a%20particular%20question%20rather%20clarification%20as%20our%20code%20heavily%20relies%20on%20the%20EWS%20Managed%20API%20still.%20The%20following%20will%20greatly%20help%20us%20in%20our%20impact%20analysis%2C%20appreciate%20your%20patience%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E1.%20Do%20these%2025%20method%20calls%20also%20affect%20the%20EWS%20%3CSTRONG%3EManaged%3C%2FSTRONG%3E%20API%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E2.%20Some%20of%20the%20API%20calls%20will%20be%20deprecated%20on%203%2F31.%20Any%20idea%20on%20if%20that%20deprecation%20is%20merely%20%E2%80%9Cno%20longer%20supported%E2%80%9D%20or%20%E2%80%9Cthe%20API%20calls%20will%20fail%E2%80%9D%3F%20%22We%20will%20introduce%20sunset%20headers%20in%20the%20response%20for%20these%20APIs%20that%20are%20marked%20for%20deprecation.%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ETo%20paraphrase%20the%20above%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EMeaning%20to%20say%20that%20after%203%2F31%2C%20calls%20to%20the%20listed%20methods%20in%20the%20EWS%20API%20will%20not%20fail%2C%20but%20return%20a%20response%20with%20the%20additional%20%22deprecated%22%20header.%20If%20we%20are%20using%20the%20EWS%20managed%20API%2C%20this%20will%20work%20with%20the%20old%20object%20model%20and%20the%20introduction%20of%20the%20header%20will%20not%20alter%20the%20old%20object%20model%20of%20the%20EWS%20Managed%20API.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E2.%20The%20least%20used%2025%20EWS%20Api%20methods%20are%20being%20deprecated%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ESo%2C%20to%20paraphrase%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ENo%20other%20EWS%20Api%20%2F%20EWS%20Managed%20Api%20method%20calls%20apart%20from%20the%2025%20listed%20above%20will%20fail%20or%20behave%20differently.%20All%20other%20EWS%20Api%20%2F%20EWS%20Managed%20Api%20methods%20do%20not%20internally%20call%20the%20above%2025%20methods.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EMany%20Thanks%20in%20advance!!%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ERegards%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EProbir%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2974204%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-2974204%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20one%20more%20follow%20up%20question%20-%20Is%20there%20a%20way%20to%20test%20that%20we%20are%20ready%20for%20this%20change%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3EProbir%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2980574%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-2980574%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149115%22%20target%3D%22_blank%22%3E%40Greg%20Taylor%20-%20EXCHANGE%3C%2FA%3E%2C%20I%20am%20trying%20to%20get%20my%20head%20straight%20regarding%20the%20timing%20of%20the%20%22%3CSPAN%3E%3CEM%3Edeprecation%20of%20the%2025%20least%20used%20APIs%20of%20EWS%20for%20Exchange%20Online...by%20March%2031%2C%202022%3C%2FEM%3E%22%20and%20the%20removal%20of%20%22%3CEM%3Ethe%20ability%20to%20register%20new%20apps%20in%20Azure%20with%20EWS%20permissions%20starting%20September%2030%2C%202022.%20Apps%20registered%20before%20this%20date%2C%20any%20API%20not%20mentioned%20in%20this%2C%20or%20subsequent%20announcements%2C%20will%26nbsp%3B%3CSTRONG%3Enot%26nbsp%3B%3C%2FSTRONG%3Ebe%20impacted.%3C%2FEM%3E%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EMy%20interpretation%20of%20the%202%20different%20statements%20above%20is%20that%20the%2025%20APIs%20will%20no%20longer%20be%20usable%20after%2031st%20March%20but%20it%20will%20be%20possible%20to%20register%20new%20AAD%20apps%20using%20those%20APIs%20up%20until%2030th%20September.%26nbsp%3B%20I%20feel%20like%20I%20am%20mis-understanding%20something%20here%20because%20what%20is%20the%20point%20of%20being%20able%20to%20register%20a%20new%20AAD%20app%20that%20uses%20on%20of%20the%2025%20listed%20APIs%2C%20let's%20say%20on%201st%20April%2C%20when%20the%20EWS%20APIs%20were%20no%20longer%20usable%20from%2031st%20March%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAre%20you%20able%20to%20clarify%20the%20relationship%20between%20the%202%20different%20events%20and%20the%20timing%20of%20those%202%20events%20please%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThanks%20in%20advance%2C%20Ian.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2980576%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-2980576%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F578287%22%20target%3D%22_blank%22%3E%40Ian_M10%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMarch%2031%3A%20You%20can't%20use%20those%2025%20API's%2C%20but%20still%20every%20other%20EWS%20API%20(there%20are%20lots%20more)%3C%2FP%3E%3CP%3ESept%2030%3A%20You%20can%20use%20all%20EWS%20API's%20except%20the%2025%20for%20Apps%20that%20have%20been%20registered%20before%20this%20date.%26nbsp%3B%20If%20you%20don't%20have%20an%20app%20registered%20by%20then%20-%20you%20will%20not%20be%20able%20to%20use%20EWS%20at%20all.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat's%20my%20current%20understanding%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2985363%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-2985363%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149115%22%20target%3D%22_blank%22%3E%40Greg%20Taylor%20-%20EXCHANGE%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20struggling%20with%20the%20conversion%20from%20Set-UserPhoto%20to%20the%20Graph%20equivalent.%26nbsp%3B%20Our%20agency%20currently%20employs%20a%20PowerShell%20script%20to%20upload%20new%20employee%20photos.%26nbsp%3B%20The%20photos%20are%20generated%20in%20our%20security%20badge%20system%20and%20exported%20to%20be%20used%20in%20Microsoft%20365.%26nbsp%3B%20Switching%20to%20a%20Graph%20version%20of%20the%20process%20necessitates%20the%20creation%20of%20an%20app%2C%20writing%20additional%20code%20and%20%5Bpossibly%5D%20editing%20the%20photos%20to%20fit%20one%20of%20the%209%20designated%20sizes.%26nbsp%3B%20There%20a%20concern%20that%20this%20will%20cause%20a%20significant%20increase%20in%20administration%20of%20what%20was%20originally%20a%20simple%20process.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20identifying%20which%20APIs%20to%20'retire'%2C%20it%20seems%20Microsoft%20used%20a%20metric%20that%20is%20not%20reflective%20of%20the%20viability%20of%20the%20API.%26nbsp%3B%20It%20is%20fairly%20obvious%20that%20the%20Set-UserPhoto%20API%20would%20not%20be%20used%20very%20frequently%20but%20that%20negates%20the%20utility%20of%20the%20command.%26nbsp%3B%20I%20feel%20it%20would%20be%20prudent%20to%20not%20deprecate%20the%20Set-UserPhoto%20cmdlet%20until%20an%20alternative%20procedure%20could%20be%20provided.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ET%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2995516%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-2995516%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F187072%22%20target%3D%22_blank%22%3E%40Terrell%20Gilliland%3C%2FA%3E%26nbsp%3B-%20thanks%20for%20explaining%20that.%20I'll%20circle%20back%20with%20the%20team%20and%20provide%20that%20feedback.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Co-Authors
Version history
Last update:
‎Nov 23 2021 09:05 AM
Updated by: