Final Streaming Response Not Displayed in Teams Pop-Out Window When Main Window Shows a Different Chat

Pandaraboina, Rajesh 0 Reputation points
2026-11-16T08:52:47.0533333+00:00

Version

  • Microsoft Agents SDK NuGet package version: 1.8.77
  • .NET version: .NET 10.0

Describe the bug

When the bot is used in a Microsoft Teams pop-out window while the main Teams window is focused on a different chat, the streaming response intermittently becomes stuck on the informative update, as shown in the attached screenshot. The final response is not displayed in the pop-out window.

The issue does not occur when the main Teams window and the pop-out window both display the same bot conversation. In that scenario, the streaming response completes successfully.

Application traces indicate that the request is processed successfully. No exception or error is logged, and the recorded SendActivity operations return successful 2xx status codes. However, the Microsoft Teams client does not display the final response.

To reproduce

Channel and configuration

  • Channel: Microsoft Teams
  • Client: Microsoft Teams desktop
  • SDK: Microsoft Agents SDK
  • StreamingResponse is enabled
  • The bot sends an informative update followed by streaming text chunks
  • The bot is hosted in Azure App Service and uses Azure Bot Service

Steps

  1. Open the bot conversation in the Microsoft Teams desktop client.
  2. Pop out the bot conversation into a separate window.
  3. In the main Teams window, open and focus a different chat.
  4. Return to the bot conversation in the pop-out window.
  5. Submit a question that generates a streaming response.
  6. Observe the informative update in the pop-out window.
  7. Wait for the streaming response to complete.

Actual behavior

The pop-out window remains stuck on the informative update, and the final response is not displayed.

Backend traces show successful processing, no logged exception, and successful 2xx responses for SendActivity operations.

When the main Teams window and the pop-out window display the same bot conversation, the streaming response completes and is displayed correctly.

Expected behavior

The complete bot response should be displayed in the pop-out window regardless of which conversation is open or focused in the main Microsoft Teams window.

If streaming cannot continue for the active Teams surface, the SDK or channel should fall back to delivering the completed response as a regular, non-streaming message.

Frequency

The issue is intermittent but is observed when:

  • The bot conversation is open in a Teams pop-out window.
  • A different chat is open or focused in the main Teams window.

Screenshots

User's image

Hosting information

  • Hosting platform: Azure
  • Deployment service: Azure App Service
  • Azure Bot Service: Yes
  • Client/channel: Microsoft Teams desktop
  • .NET version: .NET 10.0
  • Microsoft Agents SDK NuGet package version: 1.8.77

Logs and diagnostics

At the time of the issue:

  • The request is processed successfully.
  • No application exception is logged.
  • SendActivity operations return 2xx status codes.
  • The final response is not rendered in the Teams pop-out window.

Relevant timestamps, correlation IDs, conversation IDs, and sanitized traces can be provided if required.

Microsoft Teams | Development
Microsoft Teams | Development

Building, integrating, or customizing apps and workflows within Microsoft Teams using developer tools and APIs

0 comments No comments

4 answers

Sort by: Oldest
  1. AI answer

    2026-11-16T08:53:59.98+00:00

    No public Microsoft record confirms this exact Teams desktop pop-out defect for Microsoft Agents SDK .NET 1.8.77, so the practical mitigation is to disable streaming for affected Teams conversations and send the completed answer as a normal message while the client-rendering issue is escalated.

    Make the fallback application-controlled rather than expecting Teams or StreamingResponse to convert an incomplete stream automatically:

    1. Generate and accumulate the complete response server-side.
    2. For Teams, bypass StreamingResponse and send one ordinary message activity.
    3. Retain streaming for other channels, or expose it behind a feature flag so it can be re-enabled after validating a Teams client or SDK update.
    4. Do not send both the streamed final activity and a fallback message unconditionally; that can create duplicate answers when streaming succeeds.

    Conceptually:

    var finalText = await GenerateCompleteAnswerAsync(cancellationToken);
    
    if (turnContext.Activity.ChannelId == "msteams" &&
        options.DisableTeamsStreaming)
    {
        await turnContext.SendActivityAsync(
            MessageFactory.Text(finalText),
            cancellationToken);
        return;
    }
    
    // Existing informative-update and streaming implementation.
    await StreamAnswerAsync(turnContext, finalText, cancellationToken);
    

    There is no documented channel-side guarantee that a failed streaming presentation automatically falls back to an ordinary message. The documented lifecycle must be completed explicitly: informative update, text chunks, then stream finalization. After finalization, no more updates can be sent.^1^

    Validate the stream contract before classifying it as client-only

    Successful 2xx responses confirm that Teams accepted the activities, but do not prove that all activities belonged to one correctly formed stream or that the client rendered the final transition.

    Capture sanitized outbound activity payloads and verify:

    • The first informative update returns a stream ID, and every later chunk and final activity uses that same ID. A Microsoft Teams SDK issue specifically recommends checking the stream ID per emitted chunk when behavior suggests multiple streams.^2^
    • Only one stream is open for the conversation. Multiple conversations may stream concurrently, but each conversation can have only one open stream.
    • Every update remains associated with the triggering user activity. Streaming is intended for replies handled within that incoming activity’s handler, not proactive messaging.
    • The complete operation finishes within ten minutes of the first informative update or content chunk.
    • No informative update is sent after the first content chunk; later informative updates are not displayed.
    • The final operation actually closes the stream rather than only sending the last text chunk.^3^

    If constructing the protocol directly, the final activity must contain the complete text, the original replyToId, the original streamId, and streamType: final; it must omit streamSequence. Each intermediate REST update contains the full accumulated text rather than only the newly generated token.^3^

    Isolate and report the client defect

    Because the failure depends on which conversation the main Teams window displays, preserve the successful same-conversation test as the control case and collect:

    1. Exact Teams desktop build from Settings → About Teams.
    2. Whether the same reproduction succeeds in Teams web.
    3. A screen recording showing both windows and their active conversations.
    4. UTC timestamp, tenant region, conversation ID, activity IDs, correlation IDs, stream ID, and sanitized payload sequence.
    5. The result of a non-streaming build using the same bot, prompt, and final text.
    6. Whether the failure affects multiple users and devices on the same Teams build.

    Submit an issue to the public microsoft/Agents-for-net repository and open a Microsoft support case for Teams/Azure Bot Service. The public .NET issue history contains other Teams streaming limitations and timeouts, but none of the available reports match the pop-out/focus-dependent rendering failure described here. For example, the open timeout report concerns streams being cut off during long-running operations, not separate Teams windows.^4^

    Do not treat clearing cache, reinstalling Teams, Adaptive Card invoke-response changes, or the JavaScript SDK’s buffering-delay issue as established fixes for this case; those reports concern different symptoms and execution paths.


    References

    1. StreamingResponse class-Remarks
    2. [Dev support]: Informative Update Streaming #2506 - GitHub
    3. Stream Agent Messages - Teams | Microsoft Learn
    4. #503 Teams stream timeout when streaming a message
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Hin Vo 1,840 Reputation points Independent Advisor
    2026-11-16T10:49:21.03+00:00

    Hi @Pandaraboina, Rajesh

    For now, I am not aware of any documented limitation stating that streaming responses are unsupported in Teams pop-out windows when the main Teams client is focused on a different conversation.

    Since the bot successfully completes processing and the SendActivity operations return successful 2xx responses, the issue appears more likely related to Teams client rendering or streaming session handling rather than Azure Bot Service delivery.

    For a deeper investigation, Microsoft Support would need to be involved. A support engineer can review the collected diagnostics, analyze the Teams client and backend behavior, and determine whether this is a known issue or a potential product bug. If necessary, the case can be escalated to the appropriate engineering team for further analysis.

    Reference: Get support - Microsoft 365 admin | Microsoft Learn 

    Note: To create a support ticket, you need to have Microsoft 365 admin privileges and if you aren’t admin of your organization, please contact the admin of creating a new ticket. 

    I apologize for not being able to provide a definitive answer in the community forum. As a fellow community member, I do not have access to Microsoft's internal diagnostic tools or engineering resources to verify whether this behavior is caused by a Microsoft service issue. Therefore, I would recommend contacting Microsoft Support or the relevant development support channel so the issue can be properly investigated.

    Thank you for your understanding.

    Was this answer helpful?


  3. Hin Vo 1,840 Reputation points Independent Advisor
    2026-11-16T10:56:38.1366667+00:00

    Hi @Pandaraboina, Rajesh

    Thank you for your response.

    If you receive any updates or findings from the support team regarding this behavior, please feel free to share them in this post, as they may help other users who encounter a similar issue.

    Warm thanks and have a nice day.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments

  4. Ashlesha Pawar (Tata Consultancy Services Limited) 650 Reputation points Microsoft External Staff
    2026-11-17T07:00:55.3666667+00:00

    Hi Rajesh,

    Thank you for sharing the detailed steps. The difference in behavior depending on which chat is open in the main Teams window is helpful for narrowing down the issue.

    We will engage the relevant engineering team for an initial review and guidance on ownership and diagnostics.

    At this stage, we have not independently reproduced the behavior or confirmed whether it originates in the Teams client, SDK, or channel. Successful 2xx responses alone do not confirm that the final streaming response was rendered by the client.

    Could you please share:

    • Your exact Teams desktop version and OS version.
    • Approximately how often this occurs.
    • Whether the final response appears when you switch the main window back to the bot conversation or close and reopen the pop-out.
    • A sanitized snippet showing how you send streaming updates and complete the stream, including the EndStreamAsync call.

    Please remove any credentials or sensitive information from the snippet. Diagnostic logs containing sensitive details should be shared securely through your support case rather than posted publicly.

    We will update this thread when we have verified findings or further guidance.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.