Chat SDK now supports reactions and ephemeral messages on Teams

**Chat SDK**’s Microsoft Teams adapter now supports reactions and ephemeral messages through the same API used by its other adapters. Bots can add and remove reactions on Teams messages, and they can send native, user-targeted ephemeral messages that only the intended recipient sees.

On the product side, ephemeral delivery is exposed as **thread.postEphemeral()** and **channel.postEphemeral()**. That gives bot authors a single call path for private, in-context messages—such as permission prompts—without a separate Teams-only surface. Reaction add/remove sits on the same shared adapter model, so Teams bots no longer need custom reaction plumbing to match other Chat SDK channels.

For engineers building multi-platform bots, adapter parity matters more than a feature checklist. One reaction and ephemeral API across adapters cuts platform forks, reduces “works elsewhere, broken on Teams” edge cases, and keeps permission and confirmation flows inside the conversation instead of bouncing users to DMs or external UIs.

In market terms, Teams is often the holdout when chat SDKs chase Slack- or Discord-style interactivity. Shipping reactions and native ephemeral messages on the same API as other adapters narrows that gap and makes Chat SDK more viable for Teams-first or mixed-workspace products that previously delayed Teams support or maintained a second code path.

Practical takeaway: if you already use Chat SDK elsewhere, re-check the Teams adapter for reaction handlers and **postEphemeral** on thread and channel objects, especially for permission prompts and other one-user-only UX. Watch how complete the remaining release items—such as author emails—land in the same unified API so Teams stays aligned with the rest of the adapter set rather than lagging on the next parity pass.