Today, we're pleased to announce the general availability of several new features to the Microsoft Teams API in Microsoft Graph, including interactive messaging APIs to read and send Microsoft Teams messages.
We are pleased to announce the general availability of resource-specific consent and the APIs to read channel messages. Enabling you to build apps that can read messages and manipulate channels, without needing to beg an admin for access to the entire tenant.
Back in February we announced the public preview of change notifications for Teams messages and we are excited to share we have now moved the change notification for Teams to general availability. This was one of the most common requests made in UserVoice, and we heard it from developers who wanted to listen to Teams messages in near-real time...
At the end of July, we will make breaking changes to the beta endpoint that include different permissions for app installations for a user and removing redundant data from code snippets inside chatMessages. APIs on the v1.0 endpoint will not be affected.
One of the most common requests we receive in UserVoice is change notifications for messages. Developers want to build apps that can listen to Teams messages in near-real time, without polling, to enable scenarios such as bots that listen to messages on which they aren't @mentioned, or assist with enterprise information archiving and data loss prevention. We are pleased to announce that developers can now subscribe to change notifications for Microsoft Teams messages. This feature is available in beta on the Microsoft Graph API.