Microsoft Entra and Teams are introducing new resource-specific consent settings for teams and chats to enhance secure app adoption. These settings will affect Chat RSC and Team RSC for apps in Microsoft Teams. Existing Group owner consent settings and API and the existing Chat RSC API will be retired with this update. The new settings will be managed using Microsoft Graph PowerShell commandlets and will start taking effect on March 7, 2024, and will completely roll out to all tenants by April 14, 2024. Teams-level admins can independently manage these settings. Instructions for modifying the new teams-specific consent settings can be found in the Configure consent settings section of Grant RSC permissions to an app - Teams | Microsoft Learn.
Entra ID is moving Teams app consent to new resource-specific controls while retiring legacy RSC interfaces
The period’s only supplied item is a Microsoft 365 Message Center notice describing a service rollout and retirement, not a documentation clarification. Entra ID and Microsoft Teams are introducing teams- and chat-specific resource-specific consent settings for apps using Chat RSC and Team RSC. The notice does not identify the change as preview or generally available.
- New consent controls apply to Teams and chat resources
Entra ID · Microsoft identity platformResource-specific consent settings are being introduced for apps in Microsoft Teams, covering Chat RSC and Team RSC. Microsoft describes the change as intended to enhance secure app adoption, but supplies no further security requirements or configuration details.
- Legacy consent settings and APIs are retiringEntra ID · Microsoft identity platform
The existing Group owner consent settings and API, together with the existing Chat RSC API, will be retired as part of this update. This creates a compatibility and administration impact for tenants or automation that still depend on those interfaces.
- Administration shifts to Microsoft Graph PowerShell during a staged rollout
Entra ID · SecurityThe new teams-specific consent settings are managed using Microsoft Graph PowerShell cmdlets. Teams-level admins can manage them independently; the notice says the rollout started taking effect on March 7 and will be complete across tenants by April 14, 2024.
The change began taking effect on March 7, 2024, with rollout to all tenants scheduled to complete by April 14, 2024. Administrators whose processes or tooling depend on the existing Group owner consent settings or API, or the existing Chat RSC API, need to account for their retirement. The new settings are managed through Microsoft Graph PowerShell cmdlets, and Teams-level administrators can manage them independently.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
Updates this week