{"id":5593,"date":"2020-11-17T09:00:32","date_gmt":"2020-11-17T17:00:32","guid":{"rendered":"https:\/\/officedevblogs.wpengine.com\/?p=5593"},"modified":"2023-01-26T08:27:11","modified_gmt":"2023-01-26T16:27:11","slug":"outlook-rest-api-v2-0-deprecation-notice","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/outlook-rest-api-v2-0-deprecation-notice\/","title":{"rendered":"Outlook REST API v2.0 production and beta endpoint deprecation"},"content":{"rendered":"

Update January 27, 2023:<\/span><\/span> Based on customer signals and feedback from multiple partners working through this change, we are pushing the deprecation deadline to a further date not yet defined.<\/span> P<\/span>lease note that our team is actively working to define a new date which will be announced on this same blog\/media. We <\/span>advise our users to<\/span> continue with their migration efforts since the target for the new deprecation date will still be in 2023. We will <\/span>provide<\/span> a 6 months\u2019 notice period before enforcing the block on the endpoint.<\/span><\/span>\u00a0<\/span><\/p>\n

Microsoft Graph is the modern API for\u00a0<\/span>the Microsoft 365 platform.\u00a0\u00a0<\/span>We mak<\/span>e<\/span>\u00a0continuous<\/span>,<\/span>\u00a0sign<\/span>i<\/span>ficant<\/span>\u00a0investments in its\u00a0<\/span>security, performance<\/span>,<\/span>\u00a0and feature<\/span>s to\u00a0<\/span>ensure it\u00a0<\/span>meet<\/span>s<\/span>\u00a0the needs of\u00a0<\/span>our own product teams as well as the\u00a0<\/span>global\u00a0<\/span>ecosystem of developers who\u00a0<\/span>build applications using its capabilities.<\/span>\u00a0<\/span><\/p>\n

While<\/span>\u00a0we\u2019re investing in Microsoft Graph<\/span>,<\/span>\u00a0we\u2019re\u00a0<\/span>also\u00a0<\/span>examining our legacy surface areas<\/span>.<\/span>\u00a0<\/span>Some o<\/span>f o<\/span>ur\u00a0<\/span>existing legacy\u00a0<\/span>services<\/span>\u00a0become obsolete based on the new functionality<\/span>\u00a0and they no longer provide the best way to access M365\u00a0<\/span>data<\/span>. When\u00a0<\/span>this happens,\u00a0<\/span>we\u00a0<\/span>start the\u00a0<\/span>two-year\u00a0<\/span>process\u00a0<\/span>defined in our\u00a0<\/span>service deprecation policy<\/span><\/a>\u00a0to\u00a0<\/span>shut down<\/span>\u00a0the\u00a0<\/span>service<\/span>\u00a0in question.\u00a0<\/span>\u00a0<\/span><\/p>\n

Today we are announcing\u00a0<\/span>the\u00a0<\/span>deprecation of<\/span><\/b>\u00a0<\/span><\/b>both the production and\u00a0<\/span><\/b>beta<\/span><\/b><\/a>\u00a0<\/span><\/b>Outlook REST API<\/span><\/b>\u00a0<\/span><\/b>v2<\/span><\/b>.0<\/span><\/b>\u00a0<\/span><\/b>endpoints,\u00a0<\/span><\/b>and<\/span><\/b>\u00a0that\u00a0<\/span><\/b>they<\/span><\/b>\u00a0will\u00a0<\/span><\/b>be decommissioned<\/span><\/b>\u00a0<\/span><\/b>on November 30, 2022<\/span><\/b>.<\/span>\u00a0<\/span>Once past this date,\u00a0<\/span>the\u00a0<\/span>service<\/span>\u00a0will be\u00a0<\/span>retired,<\/span>\u00a0and\u00a0<\/span>d<\/span>evelopers\u00a0<\/span>may no longer<\/span>\u00a0access\u00a0<\/span>it<\/span>.<\/span>\u00a0<\/span>As part of the deprecation, w<\/span>e will<\/span>\u00a0soon<\/span>\u00a0disabl<\/span>e<\/span>\u00a0creation of new Outlook REST AP<\/span>I<\/span>\u00a0v2.0 applications<\/span>.<\/span>\u00a0<\/span><\/p>\n

Going forward, w<\/span>e will\u00a0<\/span>not<\/span>\u00a0be<\/span>\u00a0mak<\/span>ing<\/span>\u00a0any\u00a0<\/span>further\u00a0<\/span>investments in the capabilities or capacity of the\u00a0<\/span>Outlook\u00a0<\/span>REST API\u00a0<\/span>v2.0<\/span>.<\/span>\u00a0<\/span>This will result in two changes for developers.\u00a0 First<\/span>, we will\u00a0<\/span>retire<\/span>\u00a0the\u00a0<\/span>OAuth Sandbox<\/span><\/a>\u00a0by December 31, 2020.<\/span>\u00a0<\/span>Additionally, we have removed the \u201cExchange\u201d app permission\u00a0<\/span>from the Azure portal.\u00a0 We will post an article in the coming days with additional information on a workaround<\/span>\u00a0for creating apps\u00a0<\/span>accessing<\/span>\u00a0EWS<\/span>.<\/span>\u00a0<\/span><\/p>\n

If you\u00a0<\/span>are<\/span>\u00a0using the Outlook REST API<\/span>\u00a0v2.0<\/span>\u00a0in your app<\/span>,\u00a0<\/span>you should plan on\u00a0<\/span>transition<\/span>ing<\/span>\u00a0to Microsoft Graph<\/span>.\u00a0<\/span>\u00a0<\/span><\/p>\n

Please refer to:\u00a0<\/span>https:\/\/docs.microsoft.com\/en-us\/outlook\/rest\/compare-graph#moving-from-outlook-endpoint-to-microsoft-graph<\/span><\/a>\u00a0as a starting point.\u00a0<\/span>\u00a0<\/span><\/p>\n

We understand that for some applications this change, even if anticipated, will require some amount of work to accommodate<\/span>,\u00a0<\/span>but we are confident it will ensure\u00a0<\/span>better\u00a0<\/span>secur<\/span>ity<\/span>, reliab<\/span>ility<\/span>, and performan<\/span>ce\u00a0<\/span>for our customers.<\/span>\u00a0The Microsoft Support Community is here to support you through this transition.\u00a0<\/span>\u00a0<\/span><\/p>\n

Thanks for\u00a0<\/span>continuing<\/span>\u00a0with 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\u00a0<\/span>our Q&A Mail forum<\/span><\/a>.\u00a0\u00a0<\/span>\u00a0<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

Today, we are announcing the deprecation of Outlook REST API v2.0. The API will be decommissioned on a date still to be determined.<\/p>\n","protected":false},"author":69076,"featured_media":25159,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[3],"tags":[12],"class_list":["post-5593","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft-graph","tag-outlook"],"acf":[],"blog_post_summary":"

Today, we are announcing the deprecation of Outlook REST API v2.0. The API will be decommissioned on a date still to be determined.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/5593","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/users\/69076"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/comments?post=5593"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/5593\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media\/25159"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media?parent=5593"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/categories?post=5593"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/tags?post=5593"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}