From 4994c3328e80cbea777b0588c9d96e1606bc8988 Mon Sep 17 00:00:00 2001
From: "docsautomation[bot]"
 <198554515+docsautomation[bot]@users.noreply.github.com>
Date: Tue, 26 May 2026 10:23:17 +0000
Subject: [PATCH] Update
 msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
 by sayali-MSFT

---
 .../conversations/subscribe-to-conversation-events.md | 11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md b/msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
index 6f4ac003568..3ae6aabec25 100644
--- a/msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
+++ b/msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
@@ -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 |
@@ -490,6 +493,7 @@ protected override async Task OnTeamsMembersAddedAsync(IList<TeamsChannelAccount
         }
     }
 }
+```
 
 ```
 
@@ -1060,6 +1064,8 @@ export class MyBot extends TeamsActivityHandler {
 }
 ```
 
+```
+
 # [JSON](#tab/json)
 
 ```json
@@ -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
 
@@ -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)
@@ -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)
\ No newline at end of file