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

Microsoft Teams logo

check before: 2022-12-28

Product:

Graph API, Teams

Platform:

Developer, mobile, US Instances, Web, Windows Desktop, World tenant

Status:

In development

Change type:

Admin impact, New feature, Updated message

Links:

100883

Details:

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.

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*

DatePropertyoldnew
2023-01-20MC Last Updated01/11/2023 01:23:292023-01-19T21:32:44Z
2023-01-20MC MessagesUpdated 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-20MC End Time03/03/2023 09:00:002023-04-30T10:00:00Z
2023-01-11MC MessagesUpdated 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-11MC Last Updated01/06/2023 23:12:032023-01-11T01:23:29Z
2023-01-07MC MessagesThe 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-07MC TitleGeneral availability - Receive all chats messages in all scopes(Updated) General availability - Receive all chats messages in all scopes
2023-01-07MC Last Updated12/14/2022 08:48:492023-01-06T23:12:03Z
2023-01-07MC MessageTagNamesNew feature, Admin impactUpdated message, New feature, Admin impact
2023-01-07MC End Time01/13/2023 09:00:002023-03-03T09:00:00Z
2022-12-28MC PlatformsDesktop, Developer, Mobile, Web

*starting April 2022

Last updated 6 days ago

Share to MS Teams

Login to your account

Welcome Back, We Missed You!