Skip to content

[Dev-Docs AI Improvement]: Conversation events in your Teams bot by sayali-MSFT #14370

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
docsautomation wants to merge 1 commit into from
Closed

[Dev-Docs AI Improvement]: Conversation events in your Teams bot by sayali-MSFT #14370

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,9 @@ A bot receives a `conversationUpdate` event in either of the following cases:

The `conversationUpdate` event is sent to your bot when it receives information on membership updates for teams where it has been added. It also receives an update when it has been added for the first time for personal conversations.

> [!NOTE]
> Microsoft Teams does not provide a bot event that notifies an app when a user blocks the bot or blocks the conversation. This behavior is a platform limitation and no dedicated activity is sent to the bot for that user action. It applies to standard Teams bot conversation event handling, including personal app messaging scenarios. Supported bot lifecycle events include installation and conversation updates, but blocking is not exposed as a subscribable event.

The following table shows a list of Teams conversation update events with more details:

| Action taken | EventType | Method called | Description | Scope |
Expand Down Expand Up @@ -490,6 +493,7 @@ protected override async Task OnTeamsMembersAddedAsync(IList<TeamsChannelAccount
}
}
}
```

```

Expand Down Expand Up @@ -1060,6 +1064,8 @@ export class MyBot extends TeamsActivityHandler {
}
```

```

# [JSON](#tab/json)

```json
Expand Down Expand Up @@ -1212,7 +1218,7 @@ The `messageReaction` event is sent when a user adds or removes reactions to a m
| EventType | Payload object | Description | Scope |
| --------------- | ---------------- | ----------------------------------------------------------------------- | ----- |
| messageReaction | reactionsAdded | [Reactions added to bot message](#reactions-added-to-bot-message). | All |
| messageReaction | reactionsRemoved | [Reactions removed from bot message](#reactions-removed-from-bot-message). | All |
| messageReaction | reactionsRemoved | [Reactions removed from bot message](#reactions-removed-from-bot-message). | All |

### Reactions added to bot message

Expand Down Expand Up @@ -1596,6 +1602,7 @@ async onInstallationUpdateActivity(context: TurnContext) {
}
```


# [Python](#tab/python)

* [SDK reference](/python/api/botbuilder-core/botbuilder.core.activityhandler?view=botbuilder-py-latest&preserve-view=true#botbuilder-core-activityhandler-on-installation-update)
Expand Down Expand Up @@ -1654,4 +1661,4 @@ In the development phase, it's always helpful to send meaningful messages in con
* [Channel and group chat conversations with a bot](channel-and-group-conversations.md)
* [Receive all channel messages for bot and agents](channel-messages-for-bots-and-agents.md)
* [Create Teams conversation bot](channel-and-group-conversations.md)
* [Triggers in Bot Framework Composer](/composer/concept-events-and-triggers)
* [Triggers in Bot Framework Composer](/composer/concept-events-and-triggers)