Currently only delegated user permissions are supported, and this is very sub-optimal for bots and service applications that need to monitor Teams presence of users.
89 Comments
Bump - I've also being troubleshooting why READ isn't working and found this thread!
Similar use case - we have a custom staff directory on our intranet that we would love to surface the Teams presence onto. We are a large enterprise company and delegated token is not ideal since we have contractors and third parties out width our tenancy that browse our staff intranet directory.Up voting too - Please can this be done ASAP.
Please can this be fixed so we are to integrate Users presence with external systems.
Thank you.Upvoting as well.
Almost 1 year now, still no update. PLEASE try to listen users' voice.
We have a service to read and sync user's presence between Teams and another communication software, without get presence permission, we have to ask our customer to provide an bot user with password for us to do under delegate permission, quite annoying.
Since it is named Presence.ReadWrite.All, please make "Read" works, otherwise remove "Read" to avoid misleading.
In an age where remote working is definitely the norm; being able to neatly integrate presence information with external platforms would be invaluable. Whether that's for notification routing or for consistency between systems.
We have an internal portal which pulls several systems together and provide staff with useful information and dashboards, and it would be good to bring in presence information, so as our staff move between Teams, Outlook and our bespoke platform it all feels part of one cohesive ecosystem.
Upvoting, and agreed Presence.ReadWrite.All does suggest full read access to the presence libraries was intended. Need this to determine everyone's presence status from an app level for a dashboard app.
I struggle to find a reason why data as public as user presence should be available in a limited scope, but not in in an application wide environment. As DaveHmp pointed out, the name Presence.ReadWrite.All strongly suggests that read access was intended.
In a callcenter setting, this feature is all but essential.
I will pray that this option will be allowed as soon as possible, because most of our company works remotely ...
I just read this thread so far and laughed as hard as could be, hurting my ribs. Why? Because I'm going through these exact same hoops everyone else is here and it is maddening. Yes, I'm in a position where delegated permissions would work, by why? You want me to subscriptions for each user and re-up it every hour in my app? Really? Or.......... once.
Let us make that decision. Is presence info REAAAAALLY that important?We'd really like this feature. The name of the Application permission Presence.ReadWrite.All suggests that the intention is to make reading available? Otherwise why is it not just called Presence.Write.All?
Is there any update from Microsoft on this?
Upvoting as well. We have two main use-cases; a helpdesk-only app that integrates into a number of different platforms, and an internal directory where viewing of Lync / SfB presence information has been integrated for at least the last 8 years.
It's things like this that give our teams deployment a bad rep with internal users; a reduction in feature-set and capability.
