"mailEnabled": false, "provisioningErrors": [], "proxyAddresses": [], "securityEnabled": true }, … ] } Because Azure AD Graph API is built using standard REST semantics, NO special protocols or libraries are necessary to access your directory tenant information. HTTP is enough. Furthermore, Azure AD Graph API supports differential query requests. A differential query request returns all changes made to specified entities during the time between two consecutive requests. For example, if you make a differential query request an hour after the previous differential query request, only the changes made during that hour will be returned. This functionality is especially useful when synchronizing directory tenant data with an application’s data store. A differential query request URL is created by appending deltaLink in the query string to the tenant-specific endpoint: https://graph.windows.net/<tenant domain name>/<entity>?api-version=<version>&deltaLink= Such as: The deltaLink parameter with no assigned value indicates that this is an initial differential query request. Differential query paged responses contain all changes that occurred on the tenant until last page of changes is returned: { "odata.metadata": "", "aad.nextLink": "... [Truncated]", "value": [ { "odata.type": "Microsoft.WindowsAzure.ActiveDirectory.User", "objectType": "User", "objectId": "dca803ab-bf26-4753-bf20-e1c56a9c34e2", "accountEnabled": true, "displayName": "John Smith", "givenName": "John", "mailNickname": "johnsmith", "passwordPolicies": "None", "surname": "Smith", "usageLocation": "US", "userPrincipalName": "" } ] } The aad.nextLink property indicates that there are more changes on the tenant and that the application should perform subsequent differential query request right away and pass aad.nextLink property value from the response as deltaLink parameter value: [Truncated]
"mailEnabled": false, "provisioningErrors": [], "proxyAddresses": [], "securityEnabled": true }, … ] } Because Azure AD Graph API is built using standard REST semantics, NO special protocols or libraries are necessary to access your directory tenant information. HTTP is enough. Furthermore, Azure AD Graph API supports differential query requests. A differential query request returns all changes made to specified entities during the time between two consecutive requests. For example, if you make a differential query request an hour after the previous differential query request, only the changes made during that hour will be returned. This functionality is especially useful when synchronizing directory tenant data with an application’s data store. A differential query request URL is created by appending deltaLink in the query string to the tenant-specific endpoint: https://graph.windows.net/<tenant domain name>/<entity>?api-version=<version>&deltaLink= Such as: The deltaLink parameter with no assigned value indicates that this is an initial differential query request. Differential query paged responses contain all changes that occurred on the tenant until last page of changes is returned: { "odata.metadata": "", "aad.nextLink": "... [Truncated]", "value": [ { "odata.type": "Microsoft.WindowsAzure.ActiveDirectory.User", "objectType": "User", "objectId": "dca803ab-bf26-4753-bf20-e1c56a9c34e2", "accountEnabled": true, "displayName": "John Smith", "givenName": "John", "mailNickname": "johnsmith", "passwordPolicies": "None", "surname": "Smith", "usageLocation": "US", "userPrincipalName": "" } ] } The aad.nextLink property indicates that there are more changes on the tenant and that the application should perform subsequent differential query request right away and pass aad.nextLink property value from the response as deltaLink parameter value: [Truncated]