Messages being streamed as a block when using QueueTextChunk

[alspires]

Version

What package version of the SDK are you using.

• Nuget package version: microsoft.agents.builder\1.3.175
• dll product version: 1.3.175

Describe the bug
A clear and concise description of what the bug is.

• Streaming with QueueTextChunk won't work as it should. It displays the whole message in a block to the user, instead of in chunks.

To Reproduce

1. Have a foreach looping through chunks
2. Call QueueTextChunk inside it for each chunk

Example implementation:

var responseStream = await _chatService.GetMessageStream(newUserMessage, cancellationToken);
await timeoutTokenSource.CancelAsync();

var chunkIndex = 0;
await foreach (var line in responseStream.WithCancellation(cancellationToken))
{
    if (!IsValidMessage(line, out var machineResponse) && machineResponse.Length <= chunkIndex)
    {
        continue;
    }

    turnContext.StreamingResponse.QueueTextChunk(machineResponse[chunkIndex..]);
    chunkIndex = machineResponse.Length;
}

Expected behavior
The message coming chunked from a streaming enabled LLM is displayed in streaming on Teams too.

Screenshots

20260209-0931-00.4162263.mp4

The exact same happens with way bigger messages as well.

Hosting Information (please complete the following information):

• How are you Hosting this: Azure/Local with DevTunnels
• Are you deploying: Everything deployed into Azure using a Microsoft sandbox account and local .env file/manifest.
• Are you using Azure Bot Services: Yes
• What Client are you using: MSTeams
• What .net version is your build in: .NET 8

Additional context
The bot talks to one of our services that is responsible to bring back an answer from the LLM (which is correctly coming in chunks). This used to work fine, it would stream as it should but suddenly stopped working.

[MattB-msft]

@alspires
Thanks for reaching out,,

This sounds quite odd.

With what you have given me to work with I cannot quickly identify what could be happening here.
in Liew of that, here is some information on the behavior itself to see if anything stands out with regards to your agent.

There are a number of factors involved with Message streaming.
the short list is:

• Client being used ( teams / Copilot / webChat / Slack / Facebook/ etc )
• AgentType being used ( AgentID agent vs app/OBO agent )
• Amount of time between Text Chunk Queues.

The AgentSDK will scale the response accordingly to the client being interacted with

In your case, your using Teams.
Message Streaming will not work with Teams under the following conditions:

• Your using AgentID ( Agent365 digital workers / BluePrint based id's)
• Your agent is in a Group Chat
• Your agent is in a Channel.
  These are current limitations of the Teams client and mid-tier that they are working on.

Other than that,

• Teams has a buffer window of ~2 seconds between renders. if the whole message gets there in that time, it will not appear to stream,
• The AgentSDK is also buffering text chunks which it sends on 1 second intervals for teams (half a second for WebChat).

You can see what the agent SDK is doing by looking logs running in debug or trace mode, as you will see an http send for each event. You can also add in OTEL support to see what the agentSDK is doing with the individual events.

if none of that triggers a reason, can you give us a bit more about what may have changed? did this happen out of the blue? or was there an updated to either your agent or your Agent Registration in M365?

[alspires]

Hello @MattB-msft,

Thanks for your reply. This one is quite odd indeed.

if none of that triggers a reason, can you give us a bit more about what may have changed? did this happen out of the blue? or was there an updated to either your agent or your Agent Registration in M365?

I cannot remember of anything that could have caused streaming to just stop working properly. We migrated from Teams SDK to M365 Agents SDK by the end of last year, but testing locally would work just fine. We have also updated an LLM retrieval tool we were using, but it seems very unlikely that this would bring any problems given that, as I mentioned on my post, the answers are still coming back properly from there, as a stream, in chunks.

I was debugging this SDK's StreamingResponse.cs file last Thursday, and I'm not sure how relevant this is, but I noticed that whenever we made a call to QueueTextChunk, it seemed that it wasn't sending an intermediate message properly (in SendIntermediateMessage). It would only hit SendActivityAsync by the time that all chunks were buffered, giving this result of displaying the whole message in a block. Whereas, if I threw a breakpoint inside QueueTextChunk and stepped over each iteration, apparently giving the app more time to think, it would then display the messages as it should.

The content shared below was done without communicating with our LLM tool, I just put together a list of strings and I'm iterating over it the same way I'd do with a "normal" answer and it is giving me the same problems. So one less reason to suspect that the issue might be our LLM tool.

Line I stepped over on QueueTextChunk:

Agents-for-net/src/libraries/Builder/Microsoft.Agents.Builder/StreamingResponse.cs

Line 282 in 5434928

StartStream(250);

20260209-0940-25.4721860.mp4

Line that I mentioned on SendActivityAsync:

Agents-for-net/src/libraries/Builder/Microsoft.Agents.Builder/StreamingResponse.cs

Line 623 in 5434928

var response = await _context.SendActivityAsync(activity, cancellationToken).ConfigureAwait(false);

20260209-0938-02.0559497.mp4

[tracyboehrer]

To Matt's point, with Teams the messages are sent every second. There is a shorter initial delay. It is entirely possible that for short amounts of text, it would appear as a single streaming message. You can try reducing the StreamingResponse.Interval, but there would be a risk of Teams dropping message if that is too low. I wouldn't try anything lower than 500ms, but the 1s delay is per Teams guidance.

[alspires]

@tracyboehrer that line from StreamingResponse I've referenced makes each iteration have an 250ms interval when calling to StartStream. Should that be 500ms min then? As a side note, I've tried forcing this to 1000ms before and got the exact same output.

[tracyboehrer]

That is the initial delay so that streaming starts sooner, the subsequent delay is 1000ms for Teams. Too short and I'm not sure if Teams errors out or just drops the message. But it wouldn't matter since except in the case of specific responses from Teams, we just log that and continue streaming.

Are there any log messages appearing for this?

[alspires]

Got it.

Complete logs in debug mode below. Includes starting it up and sending 1 message in chat:

dbug: Microsoft.AspNetCore.Mvc.ModelBinding.ModelBinderFactory[12]
      Registered model binder providers, in the following order: Microsoft.AspNetCore.Mvc.ModelBinding.Binders.BinderTypeModelBinderProvider, Microsoft.AspNetCore.Mvc.ModelBinding.Binders.ServicesModelBinderProvider, Microsoft.AspNetCore.Mvc.ModelBinding.Binders.BodyModelBinderProvider, Microsoft.AspNetCore.Mvc.ModelBinding.Binders.HeaderModelBinderProvider, Microsoft.AspNetCore.Mvc.ModelBinding.Binders.FloatingPointTypeModelBinderProvider, Microsoft.AspNetCore.Mvc.ModelBinding.Binders.EnumTypeModelBinderProvider, Microsoft.AspNetCore.Mvc.ModelBinding.Binders.DateTimeModelBinderProvider, Microsoft.AspNetCore.Mvc.ModelBinding.Binders.SimpleTypeModelBinderProvider, Microsoft.AspNetCore.Mvc.ModelBinding.Binders.TryParseModelBinderProvider, Microsoft.AspNetCore.Mvc.ModelBinding.Binders.CancellationTokenModelBinderProvider, Microsoft.AspNetCore.Mvc.ModelBinding.Binders.ByteArrayModelBinderProvider, Microsoft.AspNetCore.Mvc.ModelBinding.Binders.FormFileModelBinderProvider, Microsoft.AspNetCore.Mvc.ModelBinding.Binders.FormCollectionModelBinderProvider, Microsoft.AspNetCore.Mvc.ModelBinding.Binders.KeyValuePairModelBinderProvider, Microsoft.AspNetCore.Mvc.ModelBinding.Binders.DictionaryModelBinderProvider, Microsoft.AspNetCore.Mvc.ModelBinding.Binders.ArrayModelBinderProvider, Microsoft.AspNetCore.Mvc.ModelBinding.Binders.CollectionModelBinderProvider, Microsoft.AspNetCore.Mvc.ModelBinding.Binders.ComplexObjectModelBinderProvider
dbug: Microsoft.Extensions.Hosting.Internal.Host[1]
      Hosting starting
info: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[63]
      User profile is available. Using 'C:\Users\apires\AppData\Local\ASP.NET\DataProtection-Keys' as key repository and Windows DPAPI to encrypt keys at rest.
info: Microsoft.Agents.Hosting.AspNetCore.BackgroundQueue.HostedActivityService[0]
      Queued Hosted Service is running.
info: Microsoft.Agents.Hosting.AspNetCore.BackgroundQueue.HostedTaskService[0]
      Queued Hosted Service is running.

dbug: Microsoft.AspNetCore.DataProtection.Repositories.FileSystemXmlRepository[37]
      Reading data from file 'C:\Users\apires\AppData\Local\ASP.NET\DataProtection-Keys\key-862022c5-66fa-485e-a8ee-43d4a7e5dc22.xml'.
dbug: Microsoft.AspNetCore.DataProtection.Repositories.FileSystemXmlRepository[37]
      Reading data from file 'C:\Users\apires\AppData\Local\ASP.NET\DataProtection-Keys\key-daac7337-79e8-4507-8147-5b8ee796fa58.xml'.
dbug: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[18]
      Found key {862022c5-66fa-485e-a8ee-43d4a7e5dc22}.
dbug: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[18]
      Found key {daac7337-79e8-4507-8147-5b8ee796fa58}.
dbug: Microsoft.AspNetCore.DataProtection.KeyManagement.DefaultKeyResolver[13]
      Considering key {862022c5-66fa-485e-a8ee-43d4a7e5dc22} with expiration date 2026-03-16 17:26:19Z as default key.
dbug: Microsoft.AspNetCore.DataProtection.TypeForwardingActivator[0]
      Forwarded activator type request from Microsoft.AspNetCore.DataProtection.XmlEncryption.DpapiXmlDecryptor, Microsoft.AspNetCore.DataProtection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60 to Microsoft.AspNetCore.DataProtection.XmlEncryption.DpapiXmlDecryptor, Microsoft.AspNetCore.DataProtection, Culture=neutral, PublicKeyToken=adb9793829ddae60
dbug: Microsoft.AspNetCore.DataProtection.XmlEncryption.DpapiXmlDecryptor[51]
      Decrypting secret element using Windows DPAPI.
dbug: Microsoft.AspNetCore.DataProtection.TypeForwardingActivator[0]
      Forwarded activator type request from Microsoft.AspNetCore.DataProtection.AuthenticatedEncryption.ConfigurationModel.AuthenticatedEncryptorDescriptorDeserializer, Microsoft.AspNetCore.DataProtection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60 to Microsoft.AspNetCore.DataProtection.AuthenticatedEncryption.ConfigurationModel.AuthenticatedEncryptorDescriptorDeserializer, Microsoft.AspNetCore.DataProtection, Culture=neutral, PublicKeyToken=adb9793829ddae60
dbug: Microsoft.AspNetCore.DataProtection.AuthenticatedEncryption.CngCbcAuthenticatedEncryptorFactory[4]
      Opening CNG algorithm 'AES' from provider '(null)' with chaining mode CBC.
dbug: Microsoft.AspNetCore.DataProtection.AuthenticatedEncryption.CngCbcAuthenticatedEncryptorFactory[3]
      Opening CNG algorithm 'SHA256' from provider '(null)' with HMAC.
dbug: Microsoft.AspNetCore.DataProtection.KeyManagement.KeyRingProvider[2]
      Using key {862022c5-66fa-485e-a8ee-43d4a7e5dc22} as the default key.
dbug: Microsoft.AspNetCore.DataProtection.Internal.DataProtectionHostedService[65]
      Key ring with default key {862022c5-66fa-485e-a8ee-43d4a7e5dc22} was loaded during application startup.
dbug: Microsoft.AspNetCore.Watch.BrowserRefresh.BlazorWasmHotReloadMiddleware[0]
      Middleware loaded
dbug: Microsoft.AspNetCore.Watch.BrowserRefresh.BrowserScriptMiddleware[0]
      Middleware loaded. Script /_framework/aspnetcore-browser-refresh.js (16547 B).
dbug: Microsoft.AspNetCore.Watch.BrowserRefresh.BrowserScriptMiddleware[0]
      Middleware loaded. Script /_framework/blazor-hotreload.js (799 B).
dbug: Microsoft.AspNetCore.Watch.BrowserRefresh.BrowserRefreshMiddleware[0]
      Middleware loaded: DOTNET_MODIFIABLE_ASSEMBLIES=debug, __ASPNETCORE_BROWSER_TOOLS=true
info: Microsoft.Hosting.Lifetime[14]
      Now listening on: http://localhost:5130
dbug: Microsoft.AspNetCore.Hosting.Diagnostics[13]
      Loaded hosting startup assembly Project.IA.TeamsAssistant.App
dbug: Microsoft.AspNetCore.Hosting.Diagnostics[13]
      Loaded hosting startup assembly Microsoft.WebTools.ApiEndpointDiscovery
dbug: Microsoft.AspNetCore.Hosting.Diagnostics[13]
      Loaded hosting startup assembly Microsoft.AspNetCore.Watch.BrowserRefresh
dbug: Microsoft.AspNetCore.Hosting.Diagnostics[13]
      Loaded hosting startup assembly Microsoft.WebTools.BrowserLink.Net
info: Microsoft.Hosting.Lifetime[0]
      Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
      Hosting environment: Development
info: Microsoft.Hosting.Lifetime[0]
      Content root path: C:\dev\project_path\src\Project.IA.TeamsAssistant.App
dbug: Microsoft.Extensions.Hosting.Internal.Host[2]
      Hosting started
dbug: Microsoft.AspNetCore.Server.Kestrel.Connections[39]
      Connection id "0HNJ7THP4MR4R" accepted.
dbug: Microsoft.AspNetCore.Server.Kestrel.Connections[1]
      Connection id "0HNJ7THP4MR4R" started.
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 POST http://localhost:5130/api/messages - application/json;+charset=utf-8 1077
dbug: Microsoft.AspNetCore.HostFiltering.HostFilteringMiddleware[0]
      Wildcard detected, all requests with hosts will be allowed.
dbug: Microsoft.AspNetCore.Routing.Matching.DfaMatcher[1001]
      1 candidate(s) found for the request path '/api/messages'
dbug: Microsoft.AspNetCore.Routing.EndpointRoutingMiddleware[1]
      Request matched endpoint 'HTTP: POST /api/messages'
dbug: Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler[2]
      Successfully validated the token.
dbug: Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler[8]
      AuthenticationScheme: Bearer was successfully authenticated.
info: Microsoft.AspNetCore.Routing.EndpointMiddleware[0]
      Executing endpoint 'HTTP: POST /api/messages'
info: Microsoft.Agents.Authentication.ConfigurationConnections[0]
      No assembly name given in config for connection `BotServiceConnection`.  Using default assembly lib: `Microsoft.Agents.Authentication.Msal`
info: Microsoft.Agents.Authentication.ConfigurationConnections[0]
      No type name given in config for connection `BotServiceConnection`.  Using default type name: `MsalAuth`
dbug: Microsoft.AspNetCore.Server.Kestrel[25]
      Connection id "0HNJ7THP4MR4R", Request id "0HNJ7THP4MR4R:00000001": started reading request body.
dbug: Microsoft.AspNetCore.Server.Kestrel[26]
      Connection id "0HNJ7THP4MR4R", Request id "0HNJ7THP4MR4R:00000001": done reading request body.
dbug: Microsoft.Agents.Hosting.AspNetCore.CloudAdapter[0]
      Activity Accepted: RequestId=e0b50766-f77f-4e62-bd6a-6315020a544e, Activity='{"type":"message","id":"1770649435475","timestamp":"2026-02-09T15:03:55.4920436\u002B00:00","localTimestamp":"2026-02-09T15:03:55.4920436\u002B00:00","localTimezone":"Europe/Lisbon","serviceUrl":"https://smba.trafficmanager.net/emea/27aa0024-e9e5-45ad-998d-ef5fce1c5c8d/","channelId":"msteams","from":{"id":"29:1K44XZsgvV_nfeJFTZPLSCj4vNTp7r3H1RWpV49H9b6YLbTELCJ-J9VOg8W6LGjBry5fxa5QoYkuLi2s5SQzmew","name":"Test User","aadObjectId":"ef3cf7fc-bf12-4c8c-adff-21fd9b18bf92"},"conversation":{"conversationType":"personal","tenantId":"27aa0024-e9e5-45ad-998d-ef5fce1c5c8d","id":"a:1TnFKFU7vvxSd6QPSiKN_uIVTXbHLQxtTU3r7XZlh_1BSxpHSVmyNOHwPls1BGU6o1VU9urC6A6jAynOCvSBP1HC8Sf8TMT3db2Atkl5q6G6VB1WnA0HCgv63kvcXyvZf"},"recipient":{"id":"28:5e7980e8-31b0-40d6-aca2-58113aa1e7a7","name":"TestBot"},"textFormat":"plain","membersAdded":[],"membersRemoved":[],"reactionsAdded":[],"reactionsRemoved":[],"locale":"en-US","text":"Test","attachments":[{"contentType":"text/html","content":"\u003Cp\u003ETest\u003C/p\u003E"}],"entities":[{"type":"clientInfo","locale":"en-US","country":"US","platform":"Web","timezone":"Europe/Lisbon"}],"channelData":{"tenant":{"id":"27aa0024-e9e5-45ad-998d-ef5fce1c5c8d"}},"listenFor":[],"textHighlights":[]}'
info: Microsoft.AspNetCore.Routing.EndpointMiddleware[1]
      Executed endpoint 'HTTP: POST /api/messages'
dbug: Microsoft.AspNetCore.Server.Kestrel.Connections[9]
      Connection id "0HNJ7THP4MR4R" completed keep alive response.
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 POST http://localhost:5130/api/messages - 202 0 - 2346.9670ms
dbug: Microsoft.Agents.Hosting.AspNetCore.CloudAdapter[0]
      ProcessActivity: RequestId=e0b50766-f77f-4e62-bd6a-6315020a544e, Activity='{"type":"message","id":"1770649435475","timestamp":"2026-02-09T15:03:55.4920436\u002B00:00","localTimestamp":"2026-02-09T15:03:55.4920436\u002B00:00","localTimezone":"Europe/Lisbon","serviceUrl":"https://smba.trafficmanager.net/emea/27aa0024-e9e5-45ad-998d-ef5fce1c5c8d/","channelId":"msteams","from":{"id":"29:1K44XZsgvV_nfeJFTZPLSCj4vNTp7r3H1RWpV49H9b6YLbTELCJ-J9VOg8W6LGjBry5fxa5QoYkuLi2s5SQzmew","name":"Test User","aadObjectId":"ef3cf7fc-bf12-4c8c-adff-21fd9b18bf92"},"conversation":{"conversationType":"personal","tenantId":"27aa0024-e9e5-45ad-998d-ef5fce1c5c8d","id":"a:1TnFKFU7vvxSd6QPSiKN_uIVTXbHLQxtTU3r7XZlh_1BSxpHSVmyNOHwPls1BGU6o1VU9urC6A6jAynOCvSBP1HC8Sf8TMT3db2Atkl5q6G6VB1WnA0HCgv63kvcXyvZf"},"recipient":{"id":"28:5e7980e8-31b0-40d6-aca2-58113aa1e7a7","name":"TestBot"},"textFormat":"plain","membersAdded":[],"membersRemoved":[],"reactionsAdded":[],"reactionsRemoved":[],"locale":"en-US","text":"Test","attachments":[{"contentType":"text/html","content":"\u003Cp\u003ETest\u003C/p\u003E"}],"entities":[{"type":"clientInfo","locale":"en-US","country":"US","platform":"Web","timezone":"Europe/Lisbon"}],"channelData":{"tenant":{"id":"27aa0024-e9e5-45ad-998d-ef5fce1c5c8d"}},"listenFor":[],"textHighlights":[]}'
dbug: Microsoft.Agents.Hosting.AspNetCore.CloudAdapter[0]
      Turn Response: RequestId=e0b50766-f77f-4e62-bd6a-6315020a544e, Activity='{"type":"typing","serviceUrl":"https://smba.trafficmanager.net/emea/27aa0024-e9e5-45ad-998d-ef5fce1c5c8d/","channelId":"msteams","from":{"id":"28:5e7980e8-31b0-40d6-aca2-58113aa1e7a7","name":"TestBot"},"conversation":{"conversationType":"personal","tenantId":"27aa0024-e9e5-45ad-998d-ef5fce1c5c8d","id":"a:1TnFKFU7vvxSd6QPSiKN_uIVTXbHLQxtTU3r7XZlh_1BSxpHSVmyNOHwPls1BGU6o1VU9urC6A6jAynOCvSBP1HC8Sf8TMT3db2Atkl5q6G6VB1WnA0HCgv63kvcXyvZf"},"recipient":{"id":"29:1K44XZsgvV_nfeJFTZPLSCj4vNTp7r3H1RWpV49H9b6YLbTELCJ-J9VOg8W6LGjBry5fxa5QoYkuLi2s5SQzmew","name":"Test User","aadObjectId":"ef3cf7fc-bf12-4c8c-adff-21fd9b18bf92"},"membersAdded":[],"membersRemoved":[],"reactionsAdded":[],"reactionsRemoved":[],"locale":"en-US","text":"Hello my name is TeamsAssistant. How can I assist today? Please, let me know by sending me a message in this chat! I can answer any product help related questions. Try me!","attachments":[],"entities":[{"streamType":"streaming","streamSequence":1,"type":"streaminfo"}],"replyToId":"1770649435475","listenFor":[],"textHighlights":[]}'
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:03:59Z] ConfidentialClientApplication 17556181 created
info: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:03:59Z - bad62541-7412-4d20-aee6-a0c100015998] MSAL MSAL.NetCore with assembly version '4.78.0.0'. CorrelationId(bad62541-7412-4d20-aee6-a0c100015998)
info: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:03:59Z - bad62541-7412-4d20-aee6-a0c100015998] === AcquireTokenForClientParameters ===
      SendX5C: False
      ForceRefresh: True
      AccessTokenHashToRefresh: False

info: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:03:59Z - bad62541-7412-4d20-aee6-a0c100015998]
      === Request Data ===
      Authority Provided? - True
      Scopes - https://api.botframework.com/.default
      Extra Query Params Keys (space separated) -
      ApiId - AcquireTokenForClient
      IsConfidentialClient - True
      SendX5C - False
      LoginHint ? False
      IsBrokerConfigured - False
      HomeAccountId - False
      CorrelationId - bad62541-7412-4d20-aee6-a0c100015998
      UserAssertion set: False
      LongRunningOboCacheKey set: False
      Region configured:
      FMI Path:
      Credential FMI Path:

info: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:03:59Z - bad62541-7412-4d20-aee6-a0c100015998] === Token Acquisition (ClientCredentialRequest) started:
         Scopes: https://api.botframework.com/.default
        Authority Host: login.microsoftonline.com
info: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:03:59Z - bad62541-7412-4d20-aee6-a0c100015998] [ClientCredentialRequest] Skipped looking for a cached access token because ForceRefresh was requested, or there are Claims but no AccessTokenHashToRefresh.
info: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:03:59Z - bad62541-7412-4d20-aee6-a0c100015998] [Instance Discovery] Instance discovery is enabled and will be performed
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:03:59Z - bad62541-7412-4d20-aee6-a0c100015998] [Region discovery] WithAzureRegion not configured.
info: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:03:59Z - bad62541-7412-4d20-aee6-a0c100015998] [Region discovery] Not using a regional authority.
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:03:59Z - bad62541-7412-4d20-aee6-a0c100015998] [Instance Discovery] Tried to use network cache provider for login.microsoftonline.com. Success? False.
info: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:03:59Z - bad62541-7412-4d20-aee6-a0c100015998] Fetching instance discovery from the network from host login.microsoftonline.com.
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:03:59Z - bad62541-7412-4d20-aee6-a0c100015998] Starting [Oauth2Client] Sending GET request
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:03:59Z - bad62541-7412-4d20-aee6-a0c100015998] Starting [HttpManager] ExecuteAsync
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:03:59Z - bad62541-7412-4d20-aee6-a0c100015998] [HttpManager] Sending request. Method: GET. Host: https://login.microsoftonline.com. Binding Certificate: False
info: System.Net.Http.HttpClient.MSALClientFactory.LogicalHandler[100]
      Start processing HTTP request GET https://login.microsoftonline.com/common/discovery/instance?*
info: System.Net.Http.HttpClient.MSALClientFactory.ClientHandler[100]
      Sending HTTP request GET https://login.microsoftonline.com/common/discovery/instance?*
info: System.Net.Http.HttpClient.MSALClientFactory.ClientHandler[101]
      Received HTTP response headers after 599.9715ms - 200
info: System.Net.Http.HttpClient.MSALClientFactory.LogicalHandler[101]
      End processing HTTP request after 610.5292ms - 200
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:00Z - bad62541-7412-4d20-aee6-a0c100015998] [HttpManager] Received response. Status code: OK.
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:00Z - bad62541-7412-4d20-aee6-a0c100015998] Finished [HttpManager] ExecuteAsync in 623 ms
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:00Z - bad62541-7412-4d20-aee6-a0c100015998] Finished [Oauth2Client] Sending GET request  in 628 ms
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:00Z - bad62541-7412-4d20-aee6-a0c100015998] Starting [OAuth2Client] Deserializing response
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:00Z - bad62541-7412-4d20-aee6-a0c100015998] Finished [OAuth2Client] Deserializing response in 12 ms
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:00Z - bad62541-7412-4d20-aee6-a0c100015998] [Instance Discovery] Tried to use network cache provider for login.microsoftonline.com. Success? True.
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:00Z - bad62541-7412-4d20-aee6-a0c100015998] [Instance Discovery] After hitting the discovery endpoint, the network provider found an entry for login.microsoftonline.com ? True.
info: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:00Z - bad62541-7412-4d20-aee6-a0c100015998] Authority validation enabled? True.
info: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:00Z - bad62541-7412-4d20-aee6-a0c100015998] Authority validation - is known env? True.
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:00Z - bad62541-7412-4d20-aee6-a0c100015998] Starting TokenClient:SendTokenRequestAsync
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:00Z - bad62541-7412-4d20-aee6-a0c100015998] [TokenClient] Before adding the client assertion / secret
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:00Z - bad62541-7412-4d20-aee6-a0c100015998] [TokenClient] After adding the client assertion / secret
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:00Z - bad62541-7412-4d20-aee6-a0c100015998] [Token Client] Fetching MsalTokenResponse ....
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:00Z - bad62541-7412-4d20-aee6-a0c100015998] Starting [Oauth2Client] Sending POST request
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:00Z - bad62541-7412-4d20-aee6-a0c100015998] Starting [HttpManager] ExecuteAsync
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:00Z - bad62541-7412-4d20-aee6-a0c100015998] [HttpManager] Sending request. Method: POST. Host: https://login.microsoftonline.com. Binding Certificate: False
info: System.Net.Http.HttpClient.MSALClientFactory.LogicalHandler[100]
      Start processing HTTP request POST https://login.microsoftonline.com/botframework.com/oauth2/v2.0/token
info: System.Net.Http.HttpClient.MSALClientFactory.ClientHandler[100]
      Sending HTTP request POST https://login.microsoftonline.com/botframework.com/oauth2/v2.0/token
info: System.Net.Http.HttpClient.MSALClientFactory.ClientHandler[101]
      Received HTTP response headers after 1761.1945ms - 200
info: System.Net.Http.HttpClient.MSALClientFactory.LogicalHandler[101]
      End processing HTTP request after 1768.1464ms - 200
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:02Z - bad62541-7412-4d20-aee6-a0c100015998] [HttpManager] Received response. Status code: OK.
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:02Z - bad62541-7412-4d20-aee6-a0c100015998] Finished [HttpManager] ExecuteAsync in 1777 ms
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:02Z - bad62541-7412-4d20-aee6-a0c100015998] Finished [Oauth2Client] Sending POST request  in 1782 ms
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:02Z - bad62541-7412-4d20-aee6-a0c100015998] Starting [OAuth2Client] Deserializing response
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:02Z - bad62541-7412-4d20-aee6-a0c100015998] Finished [OAuth2Client] Deserializing response in 18 ms
info: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:02Z - bad62541-7412-4d20-aee6-a0c100015998] ScopeSet was missing from the token response, so using developer provided scopes in the result.
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:02Z - bad62541-7412-4d20-aee6-a0c100015998] Finished TokenClient:SendTokenRequestAsync in 1820 ms
info: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:02Z - bad62541-7412-4d20-aee6-a0c100015998] Checking client info returned from the server..
info: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:02Z - bad62541-7412-4d20-aee6-a0c100015998] Saving token response to cache..
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:02Z - bad62541-7412-4d20-aee6-a0c100015998]
      [MsalTokenResponse]
      Error:
      ErrorDescription:
      Scopes: https://api.botframework.com/.default
      ExpiresIn: 86398
      RefreshIn: 43199
      AccessToken returned: True
      AccessToken Type: Bearer
      RefreshToken returned: False
      IdToken returned: False
      ClientInfo returned: False
      FamilyId:
      WamAccountId exists: False
info: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:02Z - bad62541-7412-4d20-aee6-a0c100015998] [SaveTokenResponseAsync] ID Token not present in response.
info: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:02Z - bad62541-7412-4d20-aee6-a0c100015998] Cannot determine home account ID - or id token or no client info and no subject
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:02Z - bad62541-7412-4d20-aee6-a0c100015998] [SaveTokenResponseAsync] Entering token cache semaphore. Count Real semaphore: True. Count: 1.
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:02Z - bad62541-7412-4d20-aee6-a0c100015998] [SaveTokenResponseAsync] Entered token cache semaphore.
info: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:02Z - bad62541-7412-4d20-aee6-a0c100015998] [SaveTokenResponseAsync] Saving AT in cache and removing overlapping ATs...
info: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:02Z - bad62541-7412-4d20-aee6-a0c100015998] Looking for scopes for the authority in the cache which intersect with https://api.botframework.com/.default
info: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:02Z - bad62541-7412-4d20-aee6-a0c100015998] Intersecting scope entries count - 0
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:02Z - bad62541-7412-4d20-aee6-a0c100015998] Not saving to ADAL legacy cache.
dbug: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:02Z - bad62541-7412-4d20-aee6-a0c100015998] [SaveTokenResponseAsync] Released token cache semaphore.
info: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:02Z - bad62541-7412-4d20-aee6-a0c100015998]
        === Token Acquisition finished successfully:
info: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:02Z - bad62541-7412-4d20-aee6-a0c100015998]  AT expiration time: 2/10/2026 3:04:00 PM +00:00, scopes: https://api.botframework.com/.default. source: IdentityProvider
info: Microsoft.Agents.Authentication.Msal.MsalAuth[0]
      False MSAL 4.78.0.0 MSAL.NetCore .NET 8.0.23 Microsoft Windows 10.0.26100 [2026-02-09 15:04:02Z - bad62541-7412-4d20-aee6-a0c100015998] Fetched access token from host login.microsoftonline.com.
info: System.Net.Http.HttpClient.Microsoft.Agents.Builder.RestChannelServiceClientFactory.LogicalHandler[100]
      Start processing HTTP request POST https://smba.trafficmanager.net/emea/27aa0024-e9e5-45ad-998d-ef5fce1c5c8d/v3/conversations/a%3a1TnFKFU7vvxSd6QPSiKN_uIVTXbHLQxtTU3r7XZlh_1BSxpHSVmyNOHwPls1BGU6o1VU9urC6A6jAynOCvSBP1HC8Sf8TMT3db2Atkl5q6G6VB1WnA0HCgv63kvcXyvZf/activities/1770649435475
info: System.Net.Http.HttpClient.Microsoft.Agents.Builder.RestChannelServiceClientFactory.ClientHandler[100]
      Sending HTTP request POST https://smba.trafficmanager.net/emea/27aa0024-e9e5-45ad-998d-ef5fce1c5c8d/v3/conversations/a%3a1TnFKFU7vvxSd6QPSiKN_uIVTXbHLQxtTU3r7XZlh_1BSxpHSVmyNOHwPls1BGU6o1VU9urC6A6jAynOCvSBP1HC8Sf8TMT3db2Atkl5q6G6VB1WnA0HCgv63kvcXyvZf/activities/1770649435475
info: System.Net.Http.HttpClient.Microsoft.Agents.Builder.RestChannelServiceClientFactory.ClientHandler[101]
      Received HTTP response headers after 985.8218ms - 201
info: System.Net.Http.HttpClient.Microsoft.Agents.Builder.RestChannelServiceClientFactory.LogicalHandler[101]
      End processing HTTP request after 990.885ms - 201
dbug: Microsoft.Agents.Hosting.AspNetCore.CloudAdapter[0]
      Turn Response: RequestId=e0b50766-f77f-4e62-bd6a-6315020a544e, Activity='{"type":"message","serviceUrl":"https://smba.trafficmanager.net/emea/27aa0024-e9e5-45ad-998d-ef5fce1c5c8d/","channelId":"msteams","from":{"id":"28:5e7980e8-31b0-40d6-aca2-58113aa1e7a7","name":"TestBot"},"conversation":{"conversationType":"personal","tenantId":"27aa0024-e9e5-45ad-998d-ef5fce1c5c8d","id":"a:1TnFKFU7vvxSd6QPSiKN_uIVTXbHLQxtTU3r7XZlh_1BSxpHSVmyNOHwPls1BGU6o1VU9urC6A6jAynOCvSBP1HC8Sf8TMT3db2Atkl5q6G6VB1WnA0HCgv63kvcXyvZf"},"recipient":{"id":"29:1K44XZsgvV_nfeJFTZPLSCj4vNTp7r3H1RWpV49H9b6YLbTELCJ-J9VOg8W6LGjBry5fxa5QoYkuLi2s5SQzmew","name":"Test User","aadObjectId":"ef3cf7fc-bf12-4c8c-adff-21fd9b18bf92"},"membersAdded":[],"membersRemoved":[],"reactionsAdded":[],"reactionsRemoved":[],"locale":"en-US","text":"Hello my name is TeamsAssistant. How can I assist today? Please, let me know by sending me a message in this chat! I can answer any product help related questions. Try me!","attachments":[],"entities":[{"streamId":"1770649443069","streamType":"final","streamResult":"success","type":"streaminfo"}],"replyToId":"1770649435475","listenFor":[],"textHighlights":[]}'
info: System.Net.Http.HttpClient.Microsoft.Agents.Builder.RestChannelServiceClientFactory.LogicalHandler[100]
      Start processing HTTP request POST https://smba.trafficmanager.net/emea/27aa0024-e9e5-45ad-998d-ef5fce1c5c8d/v3/conversations/a%3a1TnFKFU7vvxSd6QPSiKN_uIVTXbHLQxtTU3r7XZlh_1BSxpHSVmyNOHwPls1BGU6o1VU9urC6A6jAynOCvSBP1HC8Sf8TMT3db2Atkl5q6G6VB1WnA0HCgv63kvcXyvZf/activities/1770649435475
info: System.Net.Http.HttpClient.Microsoft.Agents.Builder.RestChannelServiceClientFactory.ClientHandler[100]
      Sending HTTP request POST https://smba.trafficmanager.net/emea/27aa0024-e9e5-45ad-998d-ef5fce1c5c8d/v3/conversations/a%3a1TnFKFU7vvxSd6QPSiKN_uIVTXbHLQxtTU3r7XZlh_1BSxpHSVmyNOHwPls1BGU6o1VU9urC6A6jAynOCvSBP1HC8Sf8TMT3db2Atkl5q6G6VB1WnA0HCgv63kvcXyvZf/activities/1770649435475
info: System.Net.Http.HttpClient.Microsoft.Agents.Builder.RestChannelServiceClientFactory.ClientHandler[101]
      Received HTTP response headers after 475.5386ms - 202
info: System.Net.Http.HttpClient.Microsoft.Agents.Builder.RestChannelServiceClientFactory.LogicalHandler[101]
      End processing HTTP request after 480.0501ms - 202

[MattB-msft]

Looking at the logs, it looks like your sending data queue text chunk fast enough for the buffer to pick it all up and send it as a block

• the agent received a message with the text "test".
• It immediately replied with a typing event ( I assume you have start typing timer enabled in AgentApplicationOptions )
• that caused it to create an access token to communicate to Teams.
• then it sent that and acked it.
• Then control was turned over to the route handler
• The route handler sent only one message with the text "Hello my name is TeamsAssistant. How can I assist today? Please, let me know by sending me a message in this chat! I can answer any product help related questions. Try me!"

We do not log the delay between route handover and next send here.. ( that's what OTEL is generally used for ), However form my read of the message, it looks like you populated everything and called "end stream" before it sent the first chunk.

Thus the message you did send looks like a stream-based message but with final as the only segment.

You could use a StreamingMessage Informative message before you enter your LLM call, that will start the stream and guarantee at least 2 sends.
or you could put a delay in your queue text chunk loop.

Though your really just slowing it down at that point :)

You could try increasing the volume of text to get the system to split it up.

However,
I know teams has been working on improving processing performance all up, you could be seeing that here.