M365 Changelog: Resource Specific Consent (RSC) for Chats and Meetings
MC280917 – Resource specific consent (RSC) for chats and meetings will allow participants in group chat and authorized users in meetings to authorize a Teams app (without requiring tenant admin consent) to follow messages exchanged in the meeting, manage members, pin tabs, provision apps, and much more – automatically based on the ongoing conversation in the meeting or any other signal.
The app can do all this anytime during the entire lifecycle of the meeting – before/during and after. All of this, just for that specific meeting. Once the app is uninstalled from the meeting, it loses all access completely.
This message is associated with Microsoft 365 Roadmap ID 85551
When this will happen:
Microsoft expects this to roll out in early September.
How this will affect your organization:
As a tenant admin, you wouldn’t have to approve every single app-only permission request while still ensuring that you have the master control to enable/disable it through AAD, if required.
If you have user consent settings enabled on Azure portal (Azure Active Directory > Enterprise applications > Consent and permissions > User consent settings) authorized users can authorize a Teams app in a group chat or meeting, to access media during a meeting, follow the chat, manage members and pin tabs for that specific meeting/chat.
User Consent Settings
What you need to do to prepare:
- You can control whether you want to allow resource owners to grant RSC permission for apps in chats and meetings directly in Azure portal using user consent setting (Azure Active Directory > Enterprise applications > Consent and permissions > User consent settings). Enabling “Allow user consent for apps” will allow resource owners to grant RSC permissions for apps in chats and meetings. In addition, you can enable or disable user consent using PowerShell, follow the steps outlined in configure user consent using PowerShell.
- You can also view the list of RSC permissions for a Teams app in the Teams Admin Center (Team Apps ->Manage apps-> <App Name> -> Permissions tab).
- You might also want to notify your users about this new capability and update your training and documentation as appropriate. More information can be found here.
More in Teams
M365 Changelog: (Updated) Microsoft Teams device store in Teams admin center
Jun 14, 2022 | Petri Staff
M365 Changelog: (Updated) Pairing naming convention between Teams channels and corresponding SharePoint folders
Jun 14, 2022 | Petri Staff
M365 Changelog: (Updated) Microsoft Teams: Chat density
Jun 7, 2022 | Petri Staff
M365 Changelog: (Updated) Microsoft Teams: Casting from Teams desktop client to Microsoft Teams Rooms
Jun 3, 2022 | Petri Staff
M365 Changelog: (Updated) Multi-language Teams meeting invite control
Jun 2, 2022 | Petri Staff
M365 Changelog: Expanded reactions in Microsoft Teams
May 26, 2022 | Petri Staff
Most popular on petri