{"id":221,"date":"2017-10-26T00:00:00","date_gmt":"2017-10-26T00:00:00","guid":{"rendered":"http:\/\/officedevblogs.wpengine.com\/?p=221"},"modified":"2017-10-26T00:00:00","modified_gmt":"2017-10-26T00:00:00","slug":"migrating-from-outlook-rest-api-v1-0-to-microsoft-graph","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/migrating-from-outlook-rest-api-v1-0-to-microsoft-graph\/","title":{"rendered":"Migrating from Outlook REST API v1.0 to Microsoft Graph"},"content":{"rendered":"
\n

Version 1.0 of the Outlook REST API <\/a>was launched in 2015 to provide API access to mail, calendar, contacts, and other data from Exchange Online, with support for Basic Authentication.\u00a0 Over time, we\u2019ve released major enhancements in Outlook REST API v2.0 and Microsoft Graph, both of which provide richer features, and better performance and reliability than Outlook REST API v1.0. Both Outlook REST API v2.0 and Microsoft Graph <\/a>use OAuth 2.0 for authentication and authorization, which is a more secure and reliable way than Basic Authentication to access data.<\/p>\n

With the planned deprecation of the Outlook REST API v1.0, you can update your app to Microsoft Graph and leverage all the new functionality available there.\u00a0 This article will give you guidance on the process of upgrading from the Outlook v1.0 REST API to the Microsoft Graph <\/a>REST API and well as pointing some of the key differences.<\/p>\n

Major Differences between Outlook v1.0 and Microsoft Graph:<\/p>\n

    \n
  1. Authorization protocol<\/strong> – Microsoft Graph uses the newer and more secure OAuth 2.0 and OpenID Connect authorization protocols. If you are already using OAuth 2.0 in your app, then you can skip this section. If you are using Basic Authentication to connect to v1.0 of the Outlook REST endpoint, upgrade to use OAuth 2.0 and OpenID Connect by getting access tokens from Azure Active Directory<\/a>.<\/li>\n
  2. Supported account types and app types – <\/strong>If you are using Basic Authorization with the Outlook v1.0 REST endpoint, changing to use OAuth 2.0 and OpenID Connect opens up your app to a much larger user base, by allowing you to access users with work or school accounts, as well as users with Microsoft personal accounts. You can also choose to enable user-specific experiences like Single Sign-on (SSO) and support different app types<\/a> such as Single Page Apps (SPA) and background services like daemon apps. Find out more about the different types of permissions<\/a> for which you can get access tokens to suit your purpose.<\/li>\n
  3. API endpoint<\/strong> – The next major difference is that Microsoft Graph endpoint is https:\/\/graph.microsoft.com<\/a>. Change your code to access your REST API calls here. All Outlook v1.0 capabilities are available in Microsoft Graph, and new features are always made available in the Microsoft Graph endpoint. You can quickly try out and compare the APIs on the 2 endpoints: use the Graph Explorer tool<\/a> for the Microsoft Graph APIs , and the Outlook API Explorer<\/a> for the Outlook REST API.<\/li>\n<\/ol>\n

    Detailed Schematic Differences between Microsoft Graph v1.0 and Outlook v1.0<\/h3>\n

    Casing<\/strong><\/p>\n

    Microsoft Graph uses the standard lower camel case as the convention for casing while the Outlook REST API uses PascalCase.<\/p>\n

    MeetingRequest<\/strong><\/p>\n

    Meeting requests messages are returned in the generic Message type in v1 while in Microsoft Graph they are under a separate derived type called \u201cmeetingRequest\u201d.<\/p>\n

    Item<\/strong><\/p>\n

    The Item entity in Outlook API has been renamed to outlookItem.<\/p>\n

    Folder<\/strong><\/p>\n

    The Outlook Folder entity in the schema has been renamed to mailFolder in the Microsoft Graph API.<\/p>\n