John Rijnbout

My feedback

  1. 16 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    John Rijnbout supported this idea  · 
  2. 75 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    John Rijnbout supported this idea  · 
  3. 11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    John Rijnbout supported this idea  · 
  4. 94 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    John Rijnbout supported this idea  · 
  5. 242 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    John Rijnbout supported this idea  · 
    An error occurred while saving the comment
    John Rijnbout commented  · 

    We are the developers of an Attendant Console application suite and one of our features is augmenting contact directory information with presence information from a variety of sources and present that to the logged on attendants. Currently we are prototyping a presence connector for MSTeams. Presence is being collected and aggregated by a server based service process and as such the client credentials grant flow seemed to be the obvious choice to authenticate the service on MSGraph. However this requires the presence.read and presence.read.all permissions to be available as app permissions, which they are not. Currently we have a working work-around by logging on an user by username/password so we can rely on the delegated permissions, but that's not an ideal situation in terms of security - rather I would like to see the needed permissions implemented as app permissions as well.

    TYI, Kind regards.

Feedback and Knowledge Base