{"id":440,"date":"2019-02-20T00:00:00","date_gmt":"2019-02-20T07:00:00","guid":{"rendered":"http:\/\/officedevblogs.wpengine.com\/?p=440"},"modified":"2022-03-22T12:34:03","modified_gmt":"2022-03-22T19:34:03","slug":"microsoft-graph-or-azure-ad-graph","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/microsoft-graph-or-azure-ad-graph\/","title":{"rendered":"Microsoft Graph or the Azure AD Graph"},"content":{"rendered":"
\n

UPDATE March 1, 2022:<\/strong><\/p>\n

Please note that we have postponed the retirement date for Azure AD Graph. The Azure AD Graph retirement date will be postponed through at least the end of 2022. For the most up to date information about end of support for Azure AD Graph, please read the blog post: Azure AD: Change Management Simplified – Microsoft Tech Community<\/a>.<\/p>\n

—————————————-<\/p>\n

Howdy folks,<\/p>\n

We\u2019ve seen a few posts recently on Stack Overflow from developers asking whether they should be using\u00a0Microsoft Graph\u00a0<\/a>(developer.microsoft.com\/graph) vs\u00a0Azure AD Graph<\/a>\u00a0(graph.windows.net).\u00a0 So we thought we\u2019d provide some guidance, as well as a bit of a roadmap to clarify things, for new and existing developers who require directory-based features.\u00a0In general, we recommend the use of Microsoft Graph over Azure AD Graph, as Microsoft Graph is where we are investing for Microsoft cloud services.<\/strong><\/p>\n

Roadmap for AAD Graph and Microsoft Graph<\/strong><\/p>\n

First of all, we’ll lay out the roadmap for Microsoft Graph (as it is related to Azure AD Graph functionality).\u00a0 In each of the sections below we’ll also highlight the opportunities and implications for developers.<\/p>\n

 <\/p>\n

Two endpoints, different functionality<\/strong><\/p>\n

Currently (as of February 2019) Microsoft Graph supports most of the directory features that Azure AD Graph supports, but not all.\u00a0 In some cases, Microsoft Graph supports functionality that is not in Azure AD Graph (such as ability to make $select projection queries).<\/p>\n

Even with those gaps, we strongly<\/strong> recommend that developers start using Microsoft Graph over Azure AD Graph, unless those specific gaps prevent you from using Microsoft Graph right now.\u00a0 For a list of the high level gaps, as of February 2019, please see the end of this blog post for more details.<\/p>\n

Microsoft Graph closing the gap with Azure AD Graph<\/strong><\/p>\n

The Microsoft Graph team is working hard to close the gap between Microsoft Graph and Azure AD Graph functionality, making it easier for developers to choose Microsoft Graph.\u00a0 We will also start to introduce newer directory features on Microsoft Graph (and in some cases\u00a0only<\/strong>\u00a0on Microsoft Graph).\u00a0 You\u2019ll start to see the gap closure and new features over the coming months.\u00a0 Please monitor both\u00a0http:\/\/developer.microsoft.com\/graph\/blogs<\/a>\u00a0and the Microsoft Graph\u00a0changelog<\/a>\u00a0to see this happen real-time so to speak!<\/p>\n

 <\/p>\n

Microsoft Graph supports all functionality exposed by Azure AD Graph<\/strong><\/p>\n

At some point in the near future (we hope within 6 months) Microsoft Graph will support all<\/strong> functionality that Azure AD Graph offers (and more).\u00a0 At this point developers building new apps (or integrating an existing app with Microsoft cloud services) will be directed to use Microsoft Graph in favor of Azure AD Graph.<\/p>\n

Update 2\/20\/2019: Starting February 23rd<\/sup> 2019, we will prevent newly registered apps from calling three older Azure AD Graph versions 0.5, 0.8 and 0.9. All scenarios in these versions are fully supported in Microsoft Graph. For existing apps calling the AAD Graph 0.5-0.9 versions you have until July 1, 2019 to migrate your app to Microsoft Graph API as these versions will be deprecated. \u00a0<\/em><\/p>\n

NOTE:\u00a0\u00a0<\/em><\/strong>As we start removing support for non-GA versions of Azure AD Graph (versions 0.5-0.9) we will deprecate additional GA versions in the future. We urge developers to migrate to Microsoft Graph. Regardless, the Azure AD Graph GA endpoint will remain fully available for all applications including production applications.\u00a0 We will continue to closely monitor this API, fix service issues and strive to continue to provide 99.99% service availability.<\/em><\/p>\n

 <\/p>\n

For developers with existing apps that call Azure AD Graph, we will provide guidance for those who want to switch their apps over to Microsoft Graph (from Azure AD Graph).\u00a0 Additionally, we\u2019ll do it in such a way that existing users for your applications won\u2019t need to re-consent to your application to access directory data through Microsoft Graph.<\/p>\n

 <\/p>\n

Client libraries<\/strong><\/p>\n

While we continue to support the Azure AD Graph client library, this is only available for .Net applications and it is maintenance mode.\u00a0 On the other hand, Microsoft Graph client libraries are available on multiple platforms and languages<\/a>, that enables you to have more choice in how you can use directory data in apps for your customers.<\/p>\n

 <\/p>\n

We’d like to hear from you<\/strong><\/p>\n

We hope this post clarifies the future of both Microsoft Graph and Azure AD Graph, and how you should think about developing against these APIs.\u00a0 In general, we recommend the use of Microsoft Graph over Azure AD Graph, as Microsoft Graph is where we are investing for Microsoft cloud services. As always, we\u2019d like to hear what you think of our roadmap plan.<\/p>\n

 <\/p>\n

Gaps between Microsoft Graph and Azure AD Graph<\/strong><\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n

AAD Graph Capability<\/strong><\/p>\n<\/td>\n

Status in Microsoft Graph (February 20, 2019)<\/strong><\/td>\n<\/tr>\n
1. Differential query (aka delta sync) for users, groups and organizational contacts<\/td>\nGA availability<\/strong>\u00a0with\u00a0Delta Query<\/a>.<\/p>\n

Delta query on organizational contacts is not available but is planned (see below).<\/p>\n

Sync from now and some other new capabilities like scoping filters (track changes on one or more users or groups) are supported in Delta Query.<\/td>\n<\/tr>\n

2. Organizational contact resource type<\/td>\nPreview recently updated<\/a> with a restructured resource, as we ready for release to GA, very soon.<\/td>\n<\/tr>\n
3.\u00a0\u00a0\u00a0\u00a0 Management of applications including:<\/p>\n

a. \u00a0 Application and service principal entity types<\/p>\n

b. \u00a0 Managing assignment of applications to users and groups<\/p>\n

c. \u00a0 Assigning OAuth permissions to apps<\/td>\n

Application<\/a> and service principal<\/a> are available in preview.<\/p>\n

Extensive breaking changes are planned over the coming few months for application APIs, in preview, before this rolls out to Microsoft Graph v1.0.<\/td>\n<\/tr>\n

4.\u00a0\u00a0\u00a0\u00a0 Partner admin on behalf of capability (for resellers and syndicators who are part of the\u00a0Cloud Solution Provider program<\/a>)<\/td>\nGA availability<\/strong>.\u00a0 See\u00a0CSP support in Microsoft Graph<\/a>.<\/td>\n<\/tr>\n
5.\u00a0\u00a0\u00a0\u00a0 Domain resource type (mainly relevant for Cloud Solution Providers)<\/td>\nGA availability<\/strong>. See\u00a0Domain<\/a>.<\/p>\n

This now includes the ability to forcefully delete a domain.<\/p>\n<\/td>\n<\/tr>\n

6.\u00a0\u00a0\u00a0\u00a0 Contracts resource type (only relevant for Cloud Solution Providers)<\/td>\nGA availability<\/strong>. See\u00a0Contract<\/a>.<\/td>\n<\/tr>\n
7.\u00a0\u00a0\u00a0\u00a0 Registering directory schema extension definitions<\/td>\nGA availability.<\/strong>\u00a0Extending resources with application data is available with\u00a0Extensions<\/a>\u00a0and schema extensions.<\/p>\n

NOTE: Not available for extending application or service principal resource types.<\/td>\n<\/tr>\n

8.\u00a0\u00a0\u00a0\u00a0 Batching<\/td>\nAvailable in\u00a0preview.\u00a0<\/strong>See\u00a0JSON batching<\/a><\/td>\n<\/tr>\n
9.\u00a0\u00a0\u00a0\u00a0 Missing properties on the User resources (sipProxyAddress, otherMails, licenseDetails)<\/td>\nGA availability<\/strong>: See\u00a0User<\/a>.<\/p>\n

This was recently updated<\/a> to add otherMails, faxNumber, employeeId and other properties. With the exception of managing users in a B2C tenant (see below), the User resource in Microsoft Graph is now at parity with Azure AD Graph, and contains additional properties and capabilities (like restoring deleted users) over and above Azure AD Graph.<\/td>\n<\/tr>\n

10.\u00a0 GetObjectsByObjectIds method<\/td>\nGA availability<\/strong>. See\u00a0getByIds method<\/a>.<\/td>\n<\/tr>\n
11.\u00a0 IsMemberOf method<\/td>\nNot planned.\u00a0 Use checkMemberGroups method instead.<\/td>\n<\/tr>\n
12.\u00a0 Manage users in a B2C tenant (set local accounts, sign in names)<\/td>\n\n

Coming soon to preview, in a few months.<\/p>\n

 <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n\n
\n

13.\u00a0 Policy<\/p>\n<\/td>\n

\n

Policy resource is available in preview.\u00a0 However some significant breaking changes are planned, before this is GA.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Thanks,<\/p>\n

Dan Kershaw on behalf of the Microsoft Graph and Azure AD Graph teams<\/p>\n<\/div>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Provides guidance and a roadmap for using Microsoft Graph vs. Azure AD Graph.<\/p>\n","protected":false},"author":69077,"featured_media":441,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[3,5],"tags":[22],"class_list":["post-440","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft-graph","category-microsoft-identity-platform","tag-azure-ad"],"acf":[],"blog_post_summary":"

Provides guidance and a roadmap for using Microsoft Graph vs. Azure AD Graph.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/440","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\/69077"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/comments?post=440"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/440\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media\/441"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media?parent=440"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/categories?post=440"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/tags?post=440"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}