Events
Mar 17, 9 PM - Mar 21, 10 AM
Join the meetup series to build scalable AI solutions based on real-world use cases with fellow developers and experts.
Register nowThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Namespace: microsoft.graph
Important
APIs under the /beta
version in Microsoft Graph are subject to change. Use of these APIs in production applications is not supported. To determine whether an API is available in v1.0, use the Version selector.
Get newly created, updated, or deleted users without having to perform a full read of the entire user collection. For more information, see Use delta query to track changes in Microsoft Graph data for details.
Note
Changes to the licenseAssignmentStates property are currently not tracked.
This API is available in the following national cloud deployments.
Global service | US Government L4 | US Government L5 (DOD) | China operated by 21Vianet |
---|---|---|---|
✅ | ✅ | ✅ | ✅ |
Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions only if your app requires it. For details about delegated and application permissions, see Permission types. To learn more about these permissions, see the permissions reference.
Permission type | Least privileged permissions | Higher privileged permissions |
---|---|---|
Delegated (work or school account) | User.Read.All | Directory.Read.All, Directory.ReadWrite.All, User.ReadWrite.All |
Delegated (personal Microsoft account) | Not supported. | Not supported. |
Application | User.Read.All | Directory.Read.All, Directory.ReadWrite.All, User.ReadWrite.All |
To begin tracking changes, you make a request including the delta function on the users resource.
GET /users/delta
Tracking changes in users incurs a round of one or more delta function calls. If you use any query parameter (other than $deltatoken
and $skiptoken
), you must specify it in the initial delta request. Microsoft Graph automatically encodes any specified parameters into the token portion of the @odata.nextLink
or @odata.deltaLink
URL provided in the response.
You only need to specify any desired query parameters once upfront.
In subsequent requests, copy and apply the @odata.nextLink
or @odata.deltaLink
URL from the previous response, as that URL already includes the encoded, desired parameters.
Query parameter | Type | Description |
---|---|---|
$deltatoken | string | A state token returned in the @odata.deltaLink URL of the previous delta function call for the same user collection, indicating the completion of that round of change tracking. Save and apply the entire @odata.deltaLink URL including this token in the first request of the next round of change tracking for that collection. |
$skiptoken | string | A state token returned in the @odata.nextLink URL of the previous delta function call, indicating there are further changes to be tracked in the same user collection. |
This method supports optional OData Query Parameters to help customize the response.
$select
query parameter as in any GET request to specify only the properties your need for best performance. The id property is always returned.$filter
:
$filter
expression is for tracking changes on a specific object: $filter=id+eq+{value}
. You can filter multiple objects. For example, https://graph.microsoft.com/beta/users/delta/?$filter= id eq '477e9fc6-5de7-4406-bb2a-7e5c83c9ffff' or id eq '004d6a07-fe70-4b92-add5-e6e37b8affff'
. There's a limit of 50 filtered objects.Name | Description |
---|---|
Authorization | Bearer {token}. Required. Learn more about authentication and authorization. |
Content-Type | application/json |
Prefer | return=minimal Specifying this header with a request that uses a @odata.deltaLink would return only the object properties that have changed since the last round. Optional. |
Don't supply a request body for this method.
If successful, this method returns 200 OK
response code and user collection object in the response body. The response also includes a @odata.nextLink
URL or a @odata.deltaLink
URL.
If a @odata.nextLink
URL is returned:
@odata.nextLink
URL until a @odata.deltaLink
URL is included in the response.If a @odata.deltaLink
URL is returned:
@odata.deltaLink
URL to learn about changes to the resource in the next round.Prefer:return=minimal
header, to include in the response values for only the properties that have changed since the time the @odata.deltaLink
was issued.By default, requests using a @odata.deltaLink
or @odata.nextLink
return the same properties as selected in the initial delta query in the following ways:
Note: With this behavior, by looking at the response it is not possible to tell whether a property is changing or not. Also, the delta responses tend to be large because they contain all property values - as shown in Example 2.
Adding an optional request header - prefer:return=minimal
- results in the following behavior:
Note: The header can be added to a
@odata.deltaLink
request at any point in time in the delta cycle. The header only affects the set of properties included in the response and it does not affect how the delta query is executed. See Example 3.
The following example shows a request. There's no $select
parameter, so a default set of properties is tracked and returned.
GET https://graph.microsoft.com/beta/users/delta
Here's an example of the response when using @odata.deltaLink
obtained from the query initialization.
Note: The response object shown here might be shortened for readability.
HTTP/1.1 200 OK
Content-type: application/json
{
"@odata.context":"https://graph.microsoft.com/beta/$metadata#users",
"@odata.nextLink":"https://graph.microsoft.com/beta/users/delta?$skiptoken=pqwSUjGYvb3jQpbwVAwEL7yuI3dU1LecfkkfLPtnIjsXoYQp_dpA3cNJWc",
"value": [
{
"businessPhones": [
"+1 425 555 0109"
],
"displayName": "Adele Vance",
"givenName": "Adele",
"jobTitle": "Retail Manager",
"mail": "AdeleV@contoso.com",
"mobilePhone": "+1 425 555 0109",
"officeLocation": "18/2111",
"preferredLanguage": "en-US",
"surname": "Vance",
"userPrincipalName": "AdeleV@contoso.com",
"id": "87d349ed-44d7-43e1-9a83-5f2406dee5bd"
}
]
}
The next example shows the initial request selecting three properties for change tracking, with default response behavior.
GET https://graph.microsoft.com/beta/users/delta?$select=displayName,jobTitle,mobilePhone
Here's an example of the response when using @odata.deltaLink
obtained from the query initialization. All three properties are included in the response and it isn't known which ones have changed since the @odata.deltaLink
was obtained.
HTTP/1.1 200 OK
Content-type: application/json
{
"@odata.context":"https://graph.microsoft.com/beta/$metadata#users",
"@odata.nextLink":"https://graph.microsoft.com/beta/users/delta?$skiptoken=pqwSUjGYvb3jQpbwVAwEL7yuI3dU1LecfkkfLPtnIjsXoYQp_dpA3cNJWc",
"value": [
{
"displayName": "Adele Vance",
"jobTitle": "Retail Manager",
"mobilePhone": "+1 425 555 0109"
}
]
}
The next example shows the initial request selecting three properties for change tracking, with alternative minimal response behavior.
GET https://graph.microsoft.com/beta/users/delta?$select=displayName,jobTitle,mobilePhone
Prefer: return=minimal
Here's an example of the response when using @odata.deltaLink
obtained from the query initialization. The mobilePhone
property isn't included, which means it hasn't changed since the last delta query; displayName
and jobTitle
are included which means their values have changed.
HTTP/1.1 200 OK
Content-type: application/json
{
"@odata.context":"https://graph.microsoft.com/beta/$metadata#users",
"@odata.nextLink":"https://graph.microsoft.com/beta/users/delta?$skiptoken=pqwSUjGYvb3jQpbwVAwEL7yuI3dU1LecfkkfLPtnIjsXoYQp_dpA3cNJWc",
"value": [
{
"displayName": "Vance Adele",
"jobTitle": "Product Marketing Manager"
}
]
}
Events
Mar 17, 9 PM - Mar 21, 10 AM
Join the meetup series to build scalable AI solutions based on real-world use cases with fellow developers and experts.
Register now