MS Teams Presence Sync Transitions

Question

MS Teams Presence Sync Transitions

Tenneti Sudheer Kumar 20

I want to follow up with a couple of questions in context to this discussion
https://learn.microsoft.com/en-gb/answers/questions/5933754/ms-teams-presence-sync-transitions

When using setUserPreferredPresence, we have an expiration time. But since user status changes have the highest preference, in a case where no status changes are made after the setUserPreferredPresence call, will the status (for example DND) continue after the expiration or does it reset?

Secondly, I want to know about the situations when we try to change the status using setPresence. In a scenario where we change the status of MS Teams from available to busy, MS teams pushes this event to the subscriptions. In this specific case, is there a way to identify if a particular client has generated this event? In this case, we may not want to conusme this event, but we are interested in consuming change of statuses that happen through any other route apart from our application itself.

Ashlesha Pawar (Tata Consultancy Services Limited) 335 Reputation points Microsoft External Staff

2026-07-02T09:33:15.1466667+00:00

Tenneti Sudheer Kumar, Based on current Microsoft Graph presence behavior, these look like by-design behaviors rather than a product bug.

For setUserPreferredPresence: when expirationDuration is reached, preferred presence stops overriding session state. It won’t stay pinned (for example DND) indefinitely unless refreshed. The final visible state is recalculated from active sessions and timeout/expiration rules.

For presence change notifications: there isn’t a reliable field to identify the exact originating client/app for a specific update event. So filtering “self-generated” updates should be handled in your app logic (for example, short suppression window using user + state + timestamp after your own write).

Your answer

Ashlesha Pawar (Tata Consultancy Services Limited) 335 Reputation points Microsoft External Staff

2026-07-02T09:33:15.1466667+00:00

Tenneti Sudheer Kumar, Based on current Microsoft Graph presence behavior, these look like by-design behaviors rather than a product bug.

For setUserPreferredPresence: when expirationDuration is reached, preferred presence stops overriding session state. It won’t stay pinned (for example DND) indefinitely unless refreshed. The final visible state is recalculated from active sessions and timeout/expiration rules.

For presence change notifications: there isn’t a reliable field to identify the exact originating client/app for a specific update event. So filtering “self-generated” updates should be handled in your app logic (for example, short suppression window using user + state + timestamp after your own write).