Chat SDK now supports reactions and ephemeral messages on Teams
Chat SDK’s Teams adapter adds reactions, user-only ephemeral messages, custom token supply, and routing fixes useful for building safer agent approval and progress flows.
The Teams adapter now supports **reactions** and **ephemeral messages** through the shared Chat SDK API. It also exposes author emails, accepts a custom token factory, shows native DM status, and fixes group routing and mention conversion.
Use targeted messages for permission prompts or user-specific agent output, and reactions or native status for lightweight progress feedback. The **custom token factory** removes the need for a static client secret on runtimes without Azure IMDS.
The Teams adapter now supports **reactions** and **ephemeral messages** through the shared Chat SDK API. It also exposes author emails, accepts a custom token factory, shows native DM status, and fixes group routing and mention conversion. Use targeted messages for permission prompts or user-specific agent output, and reactions or native status for lightweight progress feedback. The **custom token factory** removes the need for a static client secret on runtimes without Azure IMDS. These capabilities apply specifically to the Microsoft Teams adapter. The material does not describe delivery guarantees, supported reaction sets, or how ephemeral content behaves under Teams retention policies.
This makes Teams a more capable surface for interactive agents, especially where approvals, private responses, progress cues, and non-static authentication matter. It strengthens the shared-adapter approach while also showing that channel parity remains uneven: these additions are Teams-specific, and retention and delivery semantics still require platform-level validation.