SOLVED

Setting presence using api

Copper Contributor

Hi :) I'm developing a react app for Teams and I would like to ask how to set user presence in Teams. My main goal is to make 2-way state synchronization between users in my system and users in Teams. In the GraphAPI I had found only the way to get user presence, but not to change it. I have also tried tinkering a bit with this PUT route (https://presence.teams.microsoft.com/v1/me/forceavailability) but without big success. Is there a way to achieve it?

 

Regards 

Bartłomiej

5 Replies

No, there is no way to achieve the desired behavior, You can get user presence but not modify it using graph API. This is by design. 

@Manish-MSFTthank you for your response :) Are there any other ways to manage the presence of Teams users, but without using graph api, like some kind of backend library, sdk?

And the second question. When you said that this is not achievable by design, you meant right now or are there any plans for the future to add this feature? Thank you for your time :)

best response confirmed by Blizth (Copper Contributor)
Solution

Hi @Blizth,

No, there is no way to achieve the desired behavior, You can get user presence but can't modify it by using graph API, sdk or with any other back end library. This won't be implemented in the near future. It's by design.

 

@Jagadeesh-MSFT 

Thank you for your answer. 

@Jagadeesh-MSFTThat's bad design then. And the user-voice request that explicitly asked for put-permission has been closed as solved after 1600+ votes. From the top of my head I can think of 20+ scenarios where this would be super useful. Only allowing the app and other Microsoft products to set your availability status is bad design. The user requests prove this, as usual Microsoft doesn't listen.

1 best response

Accepted Solutions
best response confirmed by Blizth (Copper Contributor)
Solution

Hi @Blizth,

No, there is no way to achieve the desired behavior, You can get user presence but can't modify it by using graph API, sdk or with any other back end library. This won't be implemented in the near future. It's by design.

 

View solution in original post