users/delta with $select still returns users when non-selected properties change, and sometimes returns the same user multiple times

Sarbjit Singh 0 Reputation points
2026-11-19T23:18:41.5433333+00:00

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

  1. Should $select limit change tracking to the selected properties for users/delta, as the docs say? Is what I’m seeing a known issue?
  2. If changes to non-selected properties (contact info, address, authentication methods) are expected to trigger a result?
  3. Is manager reliably tracked when it’s in $select, or should I detect manager changes another way?
  4. 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

Microsoft Security | Microsoft Entra | Microsoft Entra ID
0 comments No comments

1 answer

Sort by: Newest
  1. Paul Thomas 165 Reputation points
    2026-11-20T09:11:18.45+00:00

    Good test setup. I'd split this into what the docs actually promise and what I'd build around, because the docs are a bit softer than the note on the users page suggests.

    1 and 2. Should $select limit tracking to the selected properties?

    That's the documented intent. The delta overview says $select means the client "prefers to only track changes on the properties or relationships specified", and that if a non-selected property changes the resource doesn't appear in the next delta response. So users coming back after a phone, address or authentication method change, with your selected values unchanged, doesn't match the docs. I can't tell you from the outside whether that's a known issue. It's worth reporting with the request IDs from those deltaLink calls through Graph support or the feedback link on the doc page.

    I wouldn't design around that note, though. The same overview says updated objects come back with "at least" the updated properties, and it lists replays as expected behaviour. So treat every user in a delta response as "this may have changed": compare the selected values with what you have stored and skip the update if nothing differs. That makes the extra users harmless, whatever the cause.

    1. Is manager tracked?

    Yes. Manager is one of the two navigation properties $select supports for change tracking (members is the other, for groups). Changes come back as a manager@delta annotation on the user, so read it from there. $expand=manager isn't supported on users/delta, so don't try to get the full manager object that way. Look up the manager by the ID in the annotation if you need more than the ID.

    1. The same user more than once in a round

    That's documented as expected. The overview says a single entity can appear multiple times in the response if it changed more than once "and under certain conditions", and tells you not to assume any order and to handle duplicates in your merge logic. In practice I'd process the pages in the order received and let the later occurrence win, and make the upsert idempotent so applying the same user twice does no harm.

    Also worth knowing: users that were just created or updated can show up late because of replication delays, so don't treat a missing change as final straight away.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.