More granular Graph API permissions
Currently the functions that I would like to leverage in teams for integration scenarios are secured using Graph API permissions that require administrator approval due to their power.
e.g. Delegated Group.ReadWrite.All is required in order for a new conversation thread to be started.
Is this being addressed as part of the overall developer api update?
Lisa R commented
The Graph API, in its current iteration, is essentially unusable at an enterprise level. Access is granted to read/write to *ALL* Teams spaces which is a LOT of power to give an application. Either have the Graph API include specific Teams IDs which it can access or have each Team include configuration to allow specific registered app IDs to access their data. In the later case, an admin would still approve the app access in the tenant but the Team owner would need to add the app ID to the Team before any data could be read.