編輯

共用方式為

Feature differences between Azure AD Graph and Microsoft Graph

  • 發行項

This article is part of step 1: review API differences of the process to migrate apps.

Many features in Microsoft Graph work similarly to their Azure Active Directory (Azure AD) Graph counterparts. However, a few have changed or improved. In this article, you learn how to adapt your apps to take advantage of these differences.

This article explores how Microsoft Graph handles:

  • Directory schema extensions
  • Differential queries
  • Batching

Directory extensions

If your app uses Azure AD Graph directory extensions, you can continue to use the same basic APIs (with Microsoft Graph request URLs) to:

  • Manage directory extension definitions using the extensionProperty resource and associated methods.
  • Get available extension properties using the getAvailableExtensionProperties action.
  • Read extension values using GET and for users, only with a $select query via the v1.0 endpoint
  • Search on extension values using GET and $filter
  • Update extension values using PATCH
  • Remove extension values using PATCH (set to null)

Microsoft Graph provides an enhanced schema extensions developer experience, which today isn't backwards compatible with Azure AD Graph directory extensions. To learn more, see Choose an extension type for your application.

If your Azure AD Graph app uses directory extensions, take an incremental approach to migrate the app to Microsoft Graph.

First, switch your app to using Microsoft Graph API calls, but let the app continue to use Azure AD Graph directory extensions.

Then, you can switch to using Microsoft Graph schema extensions. In some cases, switching isn't appropriate. Don't switch if:

  • Your app uses directory extensions created through AD Connect
  • Your app sets directory extension values that are used in token claims by other apps
  • Your app sets directory extension values that are used in dynamic membership rules

NOTE: Using Microsoft Graph schema extension properties as claims in a token using optional claims or in a dynamic membership rule is not yet supported.

To switch to the newer Microsoft Graph schema extension model, you need to:

  • Define new schema extension definitions using Microsoft Graph.
  • Update the app to support the new schema extension definitions.
  • Migrate the data from the Azure AD Graph directory extension properties to the Microsoft Graph schema extension properties. Automatic migration of data isn't supported.

Differential queries

Azure AD Graph and Microsoft Graph let you track changes using queries. The high-level approach is similar between the two APIs, but the syntax is different.

Azure AD Graph calls these differential queries while Microsoft Graph calls them delta queries.

The following table highlights key similarities and differences:

Delta request Azure AD Graph Microsoft Graph
Initial data request Uses a query parameter:
GET /groups?deltaLink=		 Uses a function:
GET /groups/delta
Get new changes GET /groups?deltaLink={deltaToken} GET /groups/delta?$deltaToken={deltaToken}
Sync from now Uses a custom HTTP header:
ocp-aad-dq-include-only-delta-token: true		 Uses a query parameter:
GET /groups/delta?$deltaToken=latest
Track changes for directory objects Gets changes for multiple resource (user and group) in the same operation:  
GET /directoryObject?$filter=isof('User') or isof('Group')&deltaLink=		 Uses separate queries with Microsoft Graph, one for each resource.
Get resource and relationship changes All requests return resource and relationship changes, if the resource has relationships. GET /groups/delta?$expand=members
Response indicating new and changed items

  • Represents newly created instances using their standard representation.

  • Updated instances are represented by their id with at least the properties that have been updated. Other properties can be included.

  • Relationships are represented as the directoryLinkChange type.

  • Represents newly created instances using their standard representation.

  • Updated instances are represented by their id with at least the properties that have been updated. Other properties can be included.

  • Relationships are represented as annotations on the standard resource representation. These annotations use the format propertyName@delta, for example members@delta for a group's membership changes.
Response indicating deleted items Indicates a deleted item with an additional property of aad.isDeleted set to true. Indicates a deleted item with the @removed annotation. It might also contain a reason code, which indicates if the item is deleted, but can be restored, or is permanently deleted.

If your app is already storing state data, consider using the "sync from now" functionality to help manage the transition to delta queries.

Batching

Azure AD Graph used a system called multi-part MIME messages to manage batching. Microsoft Graph uses JSON batching to permit up to 20 requests in a single batch operation. The JSON batching mechanism is simpler to use, especially together with JSON parsing libraries. It also allows for sequencing batch operations. However, it isn't backwards compatible with the Azure AD Graph batching approach.

Next step

Review the migration checklist again