Receive all conversation messages with RSC

The resource-specific consent (RSC) permissions model, originally developed for Microsoft Teams Graph APIs, is being extended to bot scenarios. With RSC, conversation owners can consent for a bot to receive all user messages in standard channels and chats without being @mentioned. This can be enabled by specifying the ChannelMessage.Read.Group or ChatMessage.Read.Chat permission strings in your Teams app manifest. Conversation owners can grant consent during the app installation or upgrade process after the app updates are published. For more information about enabling RSC for your app and inside of a tenant, see resource-specific consent.

Enable bots to receive all channel or chat messages


The ability for bots to receive all messages in chats using ChatMessage.Read.Chat is available only in public developer preview for Teams.

The ChannelMessage.Read.Group and ChatMessage.Read.Chat RSC permissions are being extended to bots. With user consent and app installation, these permissions:

  • Allow a specified graph application to get all messages in channels and chats, respectively.
  • Enable a bot defined in the app manifest to receive all conversations messages without being @mentioned in relevant contexts where the permissions apply.


  • Services that need access to all Teams message data must use the Graph APIs that provide access to archived data in channels and chats.
  • Bots must use the ChannelMessage.Read.Group and ChatMessage.Read.Chat RSC permission appropriately to build and enhance engaging experience for users to pass the store approval. The app description must include how the bot uses the data it reads.
  • The ChannelMessage.Read.Group and ChatMessage.Read.Chat RSC permission may not be used by bots to extract large amounts of customer data.

Update app manifest

For your bot to receive all conversation messages, the relevant RSC permission strings must be specified in the authorization.permissions.resourceSpecific property of your Teams app manifest. For more information about manifest schema, see app manifest schema for Teams.

app manifest

The following code provides an example of the app manifest:

  • Your Microsoft Azure Active Directory (AAD) app ID. The app ID can be the same as your bot ID.
  • webApplicationInfo.resource: Any string. The resource field has no operation in RSC, but must be added with a value to avoid error response.
  • authorization.permissions.resourceSpecific: RSC permissions for your app with either or both ChannelMessage.Read.Group and ChatMessage.Read.Chat specified. For more information, see resource-specific permissions.

The following code provides an example of the app manifest version 1.12 or higher:

    "$schema": "",
    "manifestVersion": "1.12",
    "version": "1.0.0",
    "id": "8239c8f3-ed78-4512-933e-babfd28856f1",
    "packageName": "com.contoso.rscechobot",
    "developer": {
        "name": "Contoso",
        "websiteUrl": "",
        "privacyUrl": "",
        "termsOfUseUrl": ""
    "icons": {
        "color": "color.png",
        "outline": "outline.png"
    "name": {
        "short": "RscEchoBot",
        "full": "Echo bot with RSC configured for all conversation messages"
    "description": {
        "short": "Echo bot with RSC configured for all channel and chat messages",
        "full": "Echo bot configured with all channel and chat messsages RSC permission in manifest"
    "accentColor": "#FFFFFF",
    "staticTabs": [
            "entityId": "conversations",
            "scopes": [
            "entityId": "about",
            "scopes": [
    "webApplicationInfo": {
        "id": "07338883-af76-47b3-86e4-2603c50be638",
        "resource": "https://AnyString"
    "authorization": {
        "permissions": {
            "resourceSpecific": [
                    "type": "Application",
                    "name": "ChannelMessage.Read.Group"
                    "type": "Application",
                    "name": "ChatMessage.Read.Chat"
    "bots": [
            "botId": "07338883-af76-47b3-86e4-2603c50be638",
            "scopes": [
            "supportsFiles": false,
            "isNotificationOnly": false
    "permissions": [
    "validDomains": []

Sideload in a conversation

The following steps guide you to sideload and validate bot that receives all channel messages in a Team without being @mentioned:

  1. Select or create a team.

  2. Select ●●● from the left pane. The dropdown menu appears.

  3. Select Manage team from the dropdown menu.

    Screenshot of Managing team option in Teams application.

  4. Select Apps. Multiple apps appear.

  5. Select Upload a custom app from the lower right corner.

    Screenshot of upload a custom app option.

  6. Select Open.

    Screenshot of the open dialog box to select the app package.

  7. Select Add from the app details pop-up, to add the bot to your selected team.

    Screenshot of the Add button to add a bot to a team.

  8. Select a channel and enter a message in the channel for your bot.

    The bot receives the message without being @mentioned.

    Screenshot of a bot receiving message in a channel.

Code snippets

The following code provides an example of the RSC permissions:

// Handle when a message is addressed to the bot.
// When rsc is enabled the method will be called even when bot is addressed without being @mentioned.
protected override async Task OnMessageActivityAsync(ITurnContext<IMessageActivity> turnContext, CancellationToken cancellationToken)
        // Sends an activity to the sender of the incoming activity.
         await turnContext.SendActivityAsync(MessageFactory.Text("Using RSC the bot can receive messages across channels or chats in team without being @mentioned."));

Code sample

Sample name Description .NET Node.js
Channel messages with RSC permissions Microsoft Teams sample app demonstrating on how a bot can receive all channel messages with RSC without being @mentioned. View View

See also