MS Teams Bot Not Receiving Read Receipts (Permissions and Settings OK)

Naim 0 Reputation points

I'm developing an MS Teams bot that should receive read receipts (Personal Conversation not team, group or channel ), but I'm not getting any events. Here's what I've checked and confirmed:

  • Read receipt settings are enabled (tenant-wide and for the user)
  • ChatMessageReadReceipt.Read.Chat permission is correctly included in my manifest and visible in the published app.
  • I've verified my code has an event handler for application/
  • I'm testing in a 1:1 chat with an up-to-date Teams client.

Any ideas on what else I should look into, or are there known limitations or bugs I should be aware of?

I can provide code snippets, error logs, and more details if needed.

Microsoft Teams Development
Microsoft Teams Development
Microsoft Teams: A Microsoft customizable chat-based workspace.Development: The process of researching, productizing, and refining new or existing technologies.
2,840 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Q&A Assist
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Based on the information provided in the context, it seems that you have correctly configured your bot to receive read receipts. However, there are a few limitations to be aware of.

    Firstly, read receipts are only supported in user to bot chat scenarios. They do not support team, channel, and group chat scopes. Additionally, if a tenant admin or user disables the Read receipts setting, the bot will not receive the read receipt event.

    Assuming that these limitations do not apply to your situation, there may be other issues to investigate. One possibility is that there is an issue with the event handler for application/ You may want to double-check that this is correctly implemented in your code.

    Another possibility is that there may be a bug or issue with the Teams client itself. You may want to try testing your bot with a different client or device to see if the issue persists.

    If you continue to experience issues, you may want to consult the Microsoft Teams documentation or seek support from the Microsoft Teams community.


    0 comments No comments