%3CLINGO-SUB%20id%3D%22lingo-sub-1898162%22%20slang%3D%22en-US%22%3EOutlook%20REST%20API%20beta%20and%20Outlook%20REST%20API%20v2.0%20Deprecation%20Notice%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1898162%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdeveloper.microsoft.com%2Fen-us%2Fgraph%2Fblogs%2Foutlook-rest-api-v2-0-deprecation-notice%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3EThis%20blog%20was%20published%20today%3C%2FA%3E%20on%20the%20Microsoft%20365%20Developer%20Blog%2C%20but%20given%20its%20relevance%20and%20importance%20to%20our%20readers%20we%20wanted%20to%20publish%20it%20here%20too.%3C%2FP%3E%0A%3CP%3EMicrosoft%20Graph%20is%20the%20modern%20API%20for%20the%26nbsp%3BMicrosoft%20365%26nbsp%3Bplatform.%26nbsp%3BWe%20make%20continuous%2C%20significant%20investments%20in%20its%20security%2C%20performance%2C%20and%20features%20to%20ensure%20it%20meets%20the%20needs%20of%20our%20own%20product%20teams%20as%20well%20as%20the%20global%20ecosystem%20of%20developers%20who%20build%20applications%20using%20its%20capabilities.%3C%2FP%3E%0A%3CP%3EWhile%20we%E2%80%99re%20investing%20in%20Microsoft%20Graph%2C%20we%E2%80%99re%20also%20examining%20our%20legacy%20surface%20areas.%20Some%20of%20our%20existing%20legacy%20services%20become%20obsolete%20based%20on%20the%20new%20functionality%20and%20they%20no%20longer%20provide%20the%20best%20way%20to%20access%20Microsoft%20365%20data.%20When%20this%20happens%2C%20we%20start%20the%20two-year%20process%20defined%20in%20our%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdeveloper.microsoft.com%2Fen-us%2Fgraph%2Fdocs%2Fconcepts%2Fversioning_and_support%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eservice%20deprecation%20policy%3C%2FA%3E%26nbsp%3Bto%20shut%20down%20the%20service%20in%20question.%3C%2FP%3E%0A%3CP%3EToday%20we%20are%20announcing%20the%20%3CSTRONG%3Edeprecation%20of%26nbsp%3Bthe%20Outlook%20REST%20API%20beta%3C%2FSTRONG%3E%3CSTRONG%3E%26nbsp%3Band%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fprevious-versions%2Foffice%2Foffice-365-api%2Fapi%2Fversion-2.0%2Fuse-outlook-rest-api%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%26nbsp%3BOutlook%20REST%20API%20v2.0%3C%2FA%3E%20endpoints%2C%20and%20that%20they%20will%20be%20decommissioned%20on%20November%2030%2C%202022%3C%2FSTRONG%3E.%20Once%20past%20this%20date%2C%20these%20services%20will%20be%20retired%2C%20and%20developers%20may%20no%20longer%20access%20them.%20As%20part%20of%20the%20deprecation%2C%20we%20will%20soon%20disable%20creation%20of%20new%20Outlook%20REST%20API%20beta%20or%20Outlook%20REST%20API%20v2.0%20applications.%3C%2FP%3E%0A%3CP%3EGoing%20forward%2C%20we%20will%20not%20be%20making%20any%20further%20investments%20in%20the%20capabilities%20or%20capacity%20of%20the%20Outlook%20REST%20API%20beta%20or%20Outlook%20REST%20API%20v2.0.%20This%20will%20result%20in%20two%20changes%20for%20developers.%20First%2C%20we%20will%20retire%20the%20%3CA%20href%3D%22https%3A%2F%2Foauthplay.azurewebsites.net%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3EOAuth%20Sandbox%3C%2FA%3E%20by%20December%2031%2C%202020.%20Additionally%2C%20we%20have%20removed%20the%20%E2%80%9CExchange%E2%80%9D%20app%20permission%20from%20the%20Azure%20portal.%20We%20have%20updated%20our%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fexchange%2Fclient-developer%2Fexchange-web-services%2Fhow-to-authenticate-an-ews-application-by-using-oauth%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Edocumentation%3C%2FA%3E%20with%20additional%20information%20regarding%20creation%20of%20EWS%20apps.%3C%2FP%3E%0A%3CP%3EIf%20you%20are%20using%20the%20Outlook%20REST%20API%20beta%20or%20Outlook%20REST%20API%20v2.0%20in%20your%20app%2C%20you%20should%20plan%20on%20transitioning%20to%20Microsoft%20Graph.%3C%2FP%3E%0A%3CP%3EPlease%20refer%20to%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foutlook%2Frest%2Fcompare-graph%23moving-from-outlook-endpoint-to-microsoft-graph%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foutlook%2Frest%2Fcompare-graph%23moving-from-outlook-endpoint-to-microsoft-graph%3C%2FA%3E%26nbsp%3Bas%20a%20starting%20point.%3C%2FP%3E%0A%3CP%3EWe%20understand%20that%20for%20some%20applications%20this%20change%2C%20even%20if%20anticipated%2C%20will%20require%20some%20amount%20of%20work%20to%20accommodate%2C%20but%20we%20are%20confident%20it%20will%20ensure%20better%20security%2C%20reliability%2C%20and%20performance%20for%20our%20customers.%20The%20Microsoft%20Support%20Community%20is%20here%20to%20support%20you%20through%20this%20transition.%3C%2FP%3E%0A%3CP%3EThanks%20for%20continuing%20with%20us%20on%20our%20journey%20as%20we%20continue%20to%20improve%20productivity%20for%20everyone%20on%20the%20planet%2C%20and%20please%20let%20us%20know%20if%20you%20have%20any%20additional%20questions%20or%20concerns%20by%20reaching%20out%20to%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fanswers%2Ftopics%2Fms-graph-mail.html%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eour%20Q%26amp%3BA%20Mail%20forum%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%3CFONT%20color%3D%22%23FF6600%22%3EThe%20Microsoft%20365%20Team%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1898162%22%20slang%3D%22en-US%22%3E%3CP%3EToday%20we%20are%20announcing%20the%26nbsp%3B%3CSTRONG%3Edeprecation%20of%26nbsp%3Bthe%20Outlook%20REST%20API%20beta%26nbsp%3Band%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fprevious-versions%2Foffice%2Foffice-365-api%2Fapi%2Fversion-2.0%2Fuse-outlook-rest-api%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3E%26nbsp%3BOutlook%20REST%20API%20v2.0%3C%2FA%3E%26nbsp%3Band%20that%20they%20will%20be%20decommissioned%20on%20November%2030%2C%202022%3C%2FSTRONG%3E.%20Once%20past%20this%20date%2C%20the%20services%20will%20be%20retired%2C%20and%20developers%20may%20no%20longer%20access%20them.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1898162%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAll%20Posts%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAnnouncements%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDeployment%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDevelopment%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOutlook%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E

This blog was published today on the Microsoft 365 Developer Blog, but given its relevance and importance to our readers we wanted to publish it here too.

Microsoft Graph is the modern API for the Microsoft 365 platform. We make continuous, significant investments in its security, performance, and features to ensure it meets the needs of our own product teams as well as the global ecosystem of developers who build applications using its capabilities.

While we’re investing in Microsoft Graph, we’re also examining our legacy surface areas. Some of our existing legacy services become obsolete based on the new functionality and they no longer provide the best way to access Microsoft 365 data. When this happens, we start the two-year process defined in our service deprecation policy to shut down the service in question.

Today we are announcing the deprecation of the Outlook REST API beta and  Outlook REST API v2.0 endpoints, and that they will be decommissioned on November 30, 2022. Once past this date, these services will be retired, and developers may no longer access them. As part of the deprecation, we will soon disable creation of new Outlook REST API beta or Outlook REST API v2.0 applications.

Going forward, we will not be making any further investments in the capabilities or capacity of the Outlook REST API beta or Outlook REST API v2.0. This will result in two changes for developers. First, we will retire the OAuth Sandbox by December 31, 2020. Additionally, we have removed the “Exchange” app permission from the Azure portal. We have updated our documentation with additional information regarding creation of EWS apps.

If you are using the Outlook REST API beta or Outlook REST API v2.0 in your app, you should plan on transitioning to Microsoft Graph.

Please refer to: https://docs.microsoft.com/en-us/outlook/rest/compare-graph#moving-from-outlook-endpoint-to-microsof... as a starting point.

We understand that for some applications this change, even if anticipated, will require some amount of work to accommodate, but we are confident it will ensure better security, reliability, and performance for our customers. The Microsoft Support Community is here to support you through this transition.

Thanks for continuing with us on our journey as we continue to improve productivity for everyone on the planet, and please let us know if you have any additional questions or concerns by reaching out to our Q&A Mail forum.

The Microsoft 365 Team