Forum Discussion

Lakshmi_145's avatar
Lakshmi_145
Iron Contributor
Jul 13, 2024
Solved

RSC permission for sending message is not working

We have enabled bots to receive all channel or chat messages. Enabled 'ChannelMessage.Read.Group' permission in manifest file as below and it is working without mentioning the bot name

 

 

"$schema": "https://developer.microsoft.com/en-us/json schemas/teams/v1.11/MicrosoftTeams.schema.json",

"manifestVersion": "1.11",

"webApplicationInfo": {

		"id": <bot app id>,

		"resource": "https://AnyString",

		"applicationPermissions": [

			"ChannelMessage.Read.Group"

		]

	}

 

 

 

But for few tenants suddenly the app got not working without mentioning bot name. It was working fine, and we have deleted existing app and re uploaded the same app again still we are not able to use the app without @bot name.

This is not a happening consistently for all tenants. But for few tenants we are seeing this issue. Sometimes, it will resolve automatically after few days or re uploading the same manifest file again.

What can be the causes of this issue. Does it depend on the policies in tenants organization level. Do teams admin need to do something to get the 'ChannelMessage.Read.Group' permission applied to bot app. Also, it is taking more than 1 day to reflect the newly added app in the teams

Chat
developer
microsoft teams
  • Dinesh-MSFT's avatar
    Dinesh-MSFT
    Jul 24, 2024

    Hi Lakshmi_145, Sorry for the delay in the response. It sounds like you're dealing with an intermittent issue where the ChannelMessage.Read.Group permission is not consistently working across different tenants. Here are some potential causes and steps to address the issue:

    The issue might be related to specific policies at the tenant organization level. Ensure that the necessary permissions are granted and that there are no conflicting policies that might be affecting the bot's functionality. Teams admins might need to provide consent for the ChannelMessage.Read.Group permission. This can be done through the Azure AD portal by navigating to App registrations > Your app > API permissions and ensuring that the required permissions are granted. Double-check the manifest file to ensure that it is correctly configured. Any errors or omissions in the manifest file could cause issues with the bot's permissions. Sometimes, changes to app permissions can take time to propagate. If the issue persists, it might be worth waiting a bit longer or re-uploading the manifest file again. For more details, please refer to the official Microsoft documentation for more details on configuring and troubleshooting RSC permissions: Get All Conversation Messages with RSC - Teams | Microsoft Learn.

4 Replies

    • Lakshmi_145's avatar
      Lakshmi_145
      Iron Contributor
      Jul 17, 2024

      Dinesh-MSFT 

       

      Hi, is there any update on this. We have uploaded the app last Friday and still we are not able to use the permission channel. Read group. Still, we are using the @Botname for sending the messages.

       

       

      • Dinesh-MSFT's avatar
        Dinesh-MSFT
        Iron Contributor
        Jul 24, 2024

        Hi Lakshmi_145, Sorry for the delay in the response. It sounds like you're dealing with an intermittent issue where the ChannelMessage.Read.Group permission is not consistently working across different tenants. Here are some potential causes and steps to address the issue:

        The issue might be related to specific policies at the tenant organization level. Ensure that the necessary permissions are granted and that there are no conflicting policies that might be affecting the bot's functionality. Teams admins might need to provide consent for the ChannelMessage.Read.Group permission. This can be done through the Azure AD portal by navigating to App registrations > Your app > API permissions and ensuring that the required permissions are granted. Double-check the manifest file to ensure that it is correctly configured. Any errors or omissions in the manifest file could cause issues with the bot's permissions. Sometimes, changes to app permissions can take time to propagate. If the issue persists, it might be worth waiting a bit longer or re-uploading the manifest file again. For more details, please refer to the official Microsoft documentation for more details on configuring and troubleshooting RSC permissions: Get All Conversation Messages with RSC - Teams | Microsoft Learn.

Resources