-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Description
When using the Teams “streaming” pattern (sending typing activities with streaminfo and a final streamed message), suggested actions do not render in Microsoft Teams. The same logic works if streaming is disabled. Also, suggested actions render correctly in Microsoft 365 Copilot.
With streaming ON: suggested actions are present in logs and payloads, but not shown in the Teams client.
With streaming OFF: suggested actions render as expected.
Tried both inlining suggested actions on the final message and sending them as a separate follow-up message; neither renders when a streaming session was used.
Expected behavior
Suggested actions render beneath the final message when:
Included in the final streamed activity, or
Sent as a separate message immediately after the streamed final.
Actual behavior
Suggested actions do not render in Teams if the conversation used streaming (final or follow-up), even though the payload includes them.
The same suggested actions do render:
When streaming is disabled, or
In Microsoft 365 Copilot.
Repro steps
Start a streaming session by sending typing activities with streaminfo:
End the stream with a final message and suggested actions (variant A: inline on final):
Or send suggested actions as a separate message right after the final (variant B: follow-up):
Observe that in Teams, suggested actions are not rendered when streaming was used. Disable streaming (send only a single final message) and observe that suggested actions render correctly. In Copilot, suggested actions render even with streaming.
Notes and workarounds tried
Inlining vs separate message: both attempted.
Visible text vs zero-width character: both attempted; no change.
Delay after final message before sending suggestions: tried (e.g., 50–200 ms); no change.
With adaptive card attachments vs plain text final: both attempted; no change when streaming was used.
Targeting suggestedActions.to to the current user ID in personal chat: set; no change.
Request
Is this suppression of suggested actions with streaming expected by design in Teams?
If not, could you confirm the correct approach or provide a fix?
If it is by design, what is the recommended pattern to present quick-reply UX alongside streamed responses (e.g., Adaptive Card action set, message extensions, or a supported “quick actions” surface)?