(Updated) General availability – Receive all chats messages in all scopes

  • Home |
  • (Updated) General availability – Receive all chats messages in all scopes
Microsoft Teams Curtain Reveal Tech Bulletin Header

Microsoft Teams, Microsoft 365 Experts

From Microsoft Corporation
Technical Bulletin MC485096 · Published Dec 14, 2022 · Last updated Jan 31, 2023

Message Summary

Updated January 31, 2023: We have updated the timeline and content below. Thank you for your patience.

The resource-specific consent (RSC) permissions model for receiving all messages, originally developed for Microsoft Teams Graph APIs, is being extended to bot scenarios. This feature was available for the channel scope and now is being extended to chat scope. With RSC, conversation owners can consent for a bot to receive all user messages in standard channels and chats without being @mentioned.

This change is related to Microsoft 365 Roadmap ID: 100883

When this will happen:

We will begin rolling out in early March (previously early January) and expect to complete by late March (previously late January). This is intended to give developers more time to check that their apps handle the new behavior correctly, and make changes if needed.

How this affects your organization:

Apps that use the ChatMessage.Read.Chat permission and have a bot capability will notice a difference in behavior when installed to a chat. Previously, the ChatMessage.Read.Chat scope only granted access to the Graph API to Get messages in a chat. After this change, the corresponding bot will receive all messages in the chat where it is installed, even when it is not at-mentioned. If the bot does not handle this correctly, your users may see unexpected replies from it.

What you can do to prepare:

Admins are requested to review existing custom or line of business apps which currently are using ChatMessage.Read.Chat permission and have a bot capability and test the application using the Developer Preview version of Teams, as described here. To maintain the existing end-user behavior, the developer must modify the code following this example. If you do not take any action, your bot will receive all messages after new installations, which could result in unexpected replies.

For more details, review: Receive all conversation messages with RSC

Additional information

Recent Comments

No comments to show.

Recent Posts

Microsoft 365 Curtain Reveal Tech Bulletin Header
New Outlook for Windows: Auto-reading emails with Microsoft Windows Narrator
October 14, 2024
Microsoft 365 Curtain Reveal Tech Bulletin Header
(Updated) Microsoft Purview: Minor encrypted message portal design updates, URL to remain the same
October 14, 2024
Microsoft Exchange Curtain Reveal Tech Bulletin Header
(Updated) Microsoft Defender for Office 365: Tenant Allow/Block List will support IPv6 allow and block entries
October 14, 2024