check before: 2022-12-28
Product:
Graph API, Microsoft Graph, Teams
Platform:
Developer, mobile, US Instances, Web, Windows Desktop, World tenant
Status:
Launched
Change type:
Admin impact, New feature, Updated message
Links:
Details:
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.
Change Category:
XXXXXXX ...
Scope:
XXXXXXX ...
Release Phase:
General Availability
Created:
2022-12-14
updated:
2022-12-14
the free basic plan is required to see all details. Sign up here
A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.
changes*
| Date | Property | old | new |
| 2023-02-01 | MC Messages | Updated January 19, 2023: We have updated the timeline and content below. Thank you for your patience.
The resource-specific consent (RSC) permissions model for receiving all message, 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:] Will begin rolling out early March (previously early January) and expect to complete by late March (previously late January). [How this effects your organization:] When developing Teams apps, this feature will enable a bot defined in the app manifest to receive all conversations messages without being @mentioned in relevant contexts where the permissions apply. Note: Admins are requested to review all apps using ChatMessage.Read.Chat permissions and take appropriate actions if required. | 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. |
| 2023-02-01 | MC How Affect | 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. | |
| 2023-02-01 | MC Last Updated | 01/19/2023 21:32:44 | 2023-01-31T21:32:24Z |
| 2023-02-01 | MC prepare | For more details, review: Receive all conversation messages with RSC
This is for your information only and no action is needed. https://www.microsoft.com/microsoft-365/roadmap?rtc=1%26filters=&searchterms=100883 | 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 https://learn.microsoft.com/graph/api/chatmessage-get?view=graph-rest-beta&tabs=http https://learn.microsoft.com/microsoftteams/platform/bots/how-to/conversations/channel-messages-with-rsc?tabs=channel%2Cdotnet#filtering-at-mention-messages https://learn.microsoft.com/microsoftteams/platform/bots/how-to/conversations/channel-messages-with-rsc?tabs=chat%2Cdotnet https://www.microsoft.com/microsoft-365/roadmap?rtc=1%26filters=&searchterms=100883 |
| 2023-01-20 | MC Last Updated | 01/11/2023 01:23:29 | 2023-01-19T21:32:44Z |
| 2023-01-20 | MC Messages | Updated January 10, 2023: We have updated the timeline and content below. Thank you for your patience.
The resource-specific consent (RSC) permissions model for receiving all message, 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:] Will begin rolling out early January and expect to complete by late January. [How this effects your organization:] When developing Teams apps, this feature will enable a bot defined in the app manifest to receive all conversations messages without being @mentioned in relevant contexts where the permissions apply. Note: Admins are requested to review all apps using ChatMessage.Read.Chat permissions and take appropriate actions if required. | Updated January 19, 2023: We have updated the timeline and content below. Thank you for your patience.
The resource-specific consent (RSC) permissions model for receiving all message, 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:] Will begin rolling out early March (previously early January) and expect to complete by late March (previously late January). [How this effects your organization:] When developing Teams apps, this feature will enable a bot defined in the app manifest to receive all conversations messages without being @mentioned in relevant contexts where the permissions apply. Note: Admins are requested to review all apps using ChatMessage.Read.Chat permissions and take appropriate actions if required. |
| 2023-01-20 | MC End Time | 03/03/2023 09:00:00 | 2023-04-30T10:00:00Z |
| 2023-01-11 | MC Messages | Updated January 6, 2023: We have updated the timeline below. Thank you for your patience.
The resource-specific consent (RSC) permissions model for receiving all message, 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:] Will begin rolling out early January and expect to complete by late January. [How this effects your organization:] When developing Teams apps, this feature will enable a bot defined in the app manifest to receive all conversations messages without being @mentioned in relevant contexts where the permissions apply. | Updated January 10, 2023: We have updated the timeline and content below. Thank you for your patience.
The resource-specific consent (RSC) permissions model for receiving all message, 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:] Will begin rolling out early January and expect to complete by late January. [How this effects your organization:] When developing Teams apps, this feature will enable a bot defined in the app manifest to receive all conversations messages without being @mentioned in relevant contexts where the permissions apply. Note: Admins are requested to review all apps using ChatMessage.Read.Chat permissions and take appropriate actions if required. |
| 2023-01-11 | MC Last Updated | 01/06/2023 23:12:03 | 2023-01-11T01:23:29Z |
| 2023-01-07 | MC Messages | The resource-specific consent (RSC) permissions model for receiving all message, 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:] Available now [How this effects your organization:] When developing Teams apps, this feature will enable a bot defined in the app manifest to receive all conversations messages without being @mentioned in relevant contexts where the permissions apply. | Updated January 6, 2023: We have updated the timeline below. Thank you for your patience.
The resource-specific consent (RSC) permissions model for receiving all message, 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:] Will begin rolling out early January and expect to complete by late January. [How this effects your organization:] When developing Teams apps, this feature will enable a bot defined in the app manifest to receive all conversations messages without being @mentioned in relevant contexts where the permissions apply. |
| 2023-01-07 | MC Title | General availability - Receive all chats messages in all scopes | (Updated) General availability - Receive all chats messages in all scopes |
| 2023-01-07 | MC Last Updated | 12/14/2022 08:48:49 | 2023-01-06T23:12:03Z |
| 2023-01-07 | MC MessageTagNames | New feature, Admin impact | Updated message, New feature, Admin impact |
| 2023-01-07 | MC End Time | 01/13/2023 09:00:00 | 2023-03-03T09:00:00Z |
| 2022-12-28 | MC Platforms | Desktop, Developer, Mobile, Web |
*starting April 2022
Last updated 10 months ago
