Forum Discussion
RSC permission for sending message is not working
- 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 toApp 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.
Hi Lakshmi_145 - Thanks for raising the query.
We will look into it and let you know the updates.
- Lakshmi_145Jul 17, 2024Iron Contributor
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-MSFTJul 24, 2024Iron Contributor
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 toApp 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.- Lakshmi_145Jul 24, 2024Iron Contributor
It has worked after re uploading.
But to note, we have provided the admin consent for the specific app registration in Entra and there was no error in team admin center while uploading the manifest file and we were able to see in the list of apps