[TEST] What are supported RSC Permissions?

Prasad-MSFT 10,541 Reputation points Microsoft External Staff Moderator
2026-08-14T05:51:15.7633333+00:00

Could you please confirm what RSC (Resource-Specific Consent) permissions are currently supported, and whether there are any limitations or prerequisites we should be aware of when configuring them?

Microsoft Teams | Development
Microsoft Teams | Development

Building, integrating, or customizing apps and workflows within Microsoft Teams using developer tools and APIs

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sayali-MSFT 6,396 Reputation points Microsoft External Staff Moderator
    2026-08-14T06:07:13.9133333+00:00

    Hello @Prasad-MSFT ,

    RSC (Resource-Specific Consent) in Microsoft Teams allows permissions to be granted at the specific team, chat, meeting, or user level instead of requiring tenant-wide Microsoft Graph permissions. It supports both Application and Delegated permission models for Teams, chats/meetings, and users.

    When configuring RSC, ensure the Teams app is registered in Microsoft Entra ID, uses a dedicated Entra app registration (1:1 mapping with the Teams app), and declares the required RSC permissions in the app manifest. Delegated RSC permissions require app manifest version 1.12 or later.

    A few limitations to be aware of: RSC permissions apply only to the specific resource where consent was granted and do not provide tenant-wide access. Additionally, Teams app permission policies and organizational admin settings may restrict app installation or permission grants, even when the manifest is configured correctly.

    For reference:

    1. https://learn.microsoft.com/en-us/microsoftteams/platform/graph-api/rsc/resource-specific-consent#supported-rsc-permissions
    2. https://learn.microsoft.com/en-us/microsoftteams/platform/graph-api/rsc/grant-resource-specific-consent

    Was this answer helpful?

    3 people found this answer helpful.

  2. AI answer

    2026-08-14T05:51:40.51+00:00

    RSC permissions are supported for these resource types in Microsoft Teams:

    • Teams and the channels within those teams
    • Chats and meetings associated with those chats
    • Users

    They are available in two access modes:

    • Application context RSC permissions: app accesses data without a signed-in user. Only resource owners can grant these permissions.
    • Delegated context RSC permissions: app accesses data on behalf of a signed-in user. Only authorized users who can install the app in that scope can grant delegated RSC permissions for that scope.

    Examples of currently supported RSC permissions include:

    • Team scope
      • Channel.Create.Group
      • Channel.Delete.Group
      • ChannelMeeting.ReadBasic.Group
      • ChannelMeetingParticipant.Read.Group
      • ChannelMeetingRecording.Read.Group
      • ChannelMeetingTranscript.Read.Group
      • ChannelMeetingNotification.Send.Group
      • ChannelMessage.Read.Group
      • ChannelMessage.Send.Group
      • ChannelSettings.Read.Group
    • Chat or meeting scope
      • Calls.AccessMedia.Chat
      • Calls.JoinGroupCalls.Chat
      • ChatSettings.Read.Chat
      • ChatSettings.ReadWrite.Chat
      • ChatMessage.Read.Chat
      • ChatMessageReadReceipt.Read.Chat
      • ChatMember.Read.Chat
      • Chat.Manage.Chat
      • TeamsTab.Read.Chat
      • InAppPurchase.Allow.Chat
      • LiveShareSession.ReadWrite.Chat
      • MeetingStage.Write.Chat
      • MeetingParticipantReaction.Read.Chat
      • OnlineMeetingIncomingAudio.Detect.Chat
      • OnlineMeetingActiveSpeaker.Read.Chat
      • OnlineMeetingAudioVideo.Stream.Chat
      • OnlineMeetingParticipant.Read.Chat
      • OnlineMeetingParticipant.ToggleIncomingAudio.Chat
    • Basic low-risk RSC permissions that are always consented to upon installation
      • TeamsActivity.Send.Group
      • TeamsActivity.Send.Chat
      • TeamsActivity.Send.User

    Key limitations and prerequisites:

    1. Support varies by permission and access mode Some permissions are supported only as application permissions, some only as delegated permissions, and some support both. For example, ChannelMessage.Read.Group is supported as application only in the listed team table, while OnlineMeetingParticipant.Read.Chat supports both delegated and application.
    2. Some features tied to listed permissions might not be generally available The documentation notes that some associated features are not yet GA.
    3. Personal-scope chat limitation For chat in personal scope, RSC permissions are limited to ChatMessageReadReceipt.Read.Chat.
    4. Chat permissions can extend to associated meetings or calls If a chat has an associated meeting or call, the relevant RSC permissions apply to those resources as well.
    5. RSC permissions are defined in the Teams app manifest, not in Microsoft Entra ID Consent is granted when the app is added to the relevant team or chat.
    6. Manifest prerequisite for testing/configuration For app manifest version 1.12 and later, add:
      • webApplicationInfo with:
        • id: Microsoft Entra app ID
        • resource: required and must have a value, though it has no operation in RSC
      • authorization: lists the permissions the app needs
      For app manifest version 1.11 and earlier, add:
      • webApplicationInfo with id and resource
      • applicationPermissions: array of RSC permission strings
    7. If the app supports both team and chat installation scopes Both team and chat permissions can be specified in the same manifest under authorization.
    8. RSC availability note RSC permissions are available only to Teams apps installed on the Teams client and not part of the Microsoft Entra admin center.
    9. Viewing requested RSC permissions In Teams admin center, go to Teams apps > Manage apps, open the app, then review the Permissions tab under Resource-specific consent (RSC) permissions.
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

    3 people found this answer helpful.
  3. Ashlesha Pawar (Tata Consultancy Services Limited) 385 Reputation points Microsoft External Staff
    2026-08-14T06:11:59.7966667+00:00

    There are two modes:

    • Application – the app can access data without a signed-in user.
    • Delegated – the app can access data only in the context of a signed-in user.

    Was this answer helpful?

    2 people found this answer helpful.
  4. Harikrishnan Rajandiran 15 Reputation points Microsoft External Staff
    2026-08-14T07:06:37.11+00:00

    RSC (Resource-Specific Consent) supports scoped permissions for Teams, chats/meetings, and users. It supports both Application and Delegated permission models, depending on the resource and permission. Examples include reading/writing chat messages and settings, reading team/channel information, creating/deleting channels, accessing meeting participants, and sending Teams activity notifications.
    Key prerequisites/limitations:

    • RSC permissions must be declared in the Teams app manifest; they aren't configured as normal Microsoft Entra API permissions.
    • For current manifest versions, manifest v1.12 or later is recommended, with webApplicationInfo and the authorization.permissions.resourceSpecific section configured.
    • The app must be installed in the specific team/chat/user scope where the permission is required. RSC doesn't provide tenant-wide access.
    • Who can provide consent depends on the permission type and resource. For example, application RSC consent can be given by the relevant team/chat resource owner, while delegated RSC is granted by an authorized user installing the app.
    • Tenant administrators can restrict RSC consent. The tenant settings can be ManagedByMicrosoft, EnabledForAllApps, or DisabledForAllApps.
    • Some RSC permissions/features may not yet be generally available (GA), so the specific API/permission should be checked before implementation.
    • RSC permissions are scoped to the resource and are not attributed to an individual user for application permissions; therefore, the app can potentially perform actions beyond what the consenting user personally could do. This should be reviewed carefully before making API calls.

    So, RSC is suitable when we need access to a specific Team, Chat, Meeting, or User rather than requesting tenant-wide Graph permissions. The exact supported permission should be validated against Microsoft's current RSC permission list before adding it to the manifest.

    Was this answer helpful?

    1 person found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.