A cloud-based identity and access management service for securing user authentication and resource access
users/delta with $select still returns users when non-selected properties change, and sometimes returns the same user multiple times
Hi all,
I’m syncing users with the Graph users/delta function and I’m seeing behavior that doesn’t match the documentation. I’d like to check whether it’s expected or a bug.
What the docs say
In Get incremental changes for users, the note under the initial request says only properties included in $select are tracked for changes. Without $select, all properties are tracked. I’m also using the delta query overview as background.
What I did
My initial request was:
GET https://graph.microsoft.com/v1.0/users/delta?$select=id,department,manager,employeeId,jobTitle
I followed all the @odata.nextLink pages and saved the final @odata.deltaLink. Then I changed things on a test user, one at a time, and called the saved deltaLink after each change.
What I see The test user came back in the delta response after each of these changes, even though none of those properties are in my $select:
- Changing the phone number
- Changing the address
- Adding a new authentication method
The values of my selected properties were unchanged each time.
A second problem Within a single delta round, I sometimes get the same user more than once across different @odata.nextLink pages, even when nothing else was changed in between.
My questions
- Should
$selectlimit change tracking to the selected properties forusers/delta, as the docs say? Is what I’m seeing a known issue? - If changes to non-selected properties (contact info, address, authentication methods) are expected to trigger a result?
- Is
managerreliably tracked when it’s in$select, or should I detect manager changes another way? - Is it expected for the same user to appear multiple times in one delta round? If so, is the last occurrence the one to trust?
Thanks in advance