Power Platform Community Forum Thread Details

I am experiencing a channel behavior difference between Microsoft Teams and Copilot for Microsoft 365.

In a Copilot Studio Adaptive Dialog, we run a long-running image generation job and poll its status every ~25 seconds using InvokeFlowAction. During each poll, a loading/progress Adaptive Card is sent using SendActivity.

Expected behavior:
Adaptive Cards sent during polling should render incrementally, as they do in Test Chat and Microsoft Teams.

Actual behavior:
In Copilot for Microsoft 365, intermediate loading/progress cards are not rendered incrementally. Instead, all intermediate cards are buffered and only the final Adaptive Card is displayed at the end of the dialog execution.

This prevents showing real-time progress updates for long-running operations in Copilot for Microsoft 365.

Categories:

Building Copilot Studio chatbots in Microsoft Teams

Hi there,

Based on the current Microsoft documentation, I would not treat this as an Adaptive Card JSON issue. This looks like a channel behavior difference between Teams/Test Chat and Microsoft 365 Copilot.

Copilot Studio and Adaptive Cards are channel-dependent: support for Adaptive Cards and other message formats can vary depending on the client/channel. Microsoft also documents asynchronous, proactive and streaming patterns for custom engine agents built with Bot Framework / Teams SDK, while Copilot Studio-built agents do not support asynchronous messages in the same way.

For a Copilot Studio low-code agent published to Microsoft 365 Copilot, I would avoid relying on multiple SendActivity calls in the same dialog execution to render incremental progress cards. A safer design is:

Start the long-running image generation job.

Store a JobId and status externally.

Return one immediate acknowledgement card.

Let the user ask “check status” in a new turn, or notify the user through another channel when the job is completed.

Return the final Adaptive Card only when the image generation is complete.

If real-time progress updates inside Microsoft 365 Copilot are a hard requirement, the recommended approach would be to implement a custom engine agent using Microsoft 365 Agents SDK / Teams SDK, where streaming responses and asynchronous follow-up messages are supported by the documented architecture.

Hope this helps!
Paolo

✅ Did this solve your issue? → Accept as Solution
👍 Partially helpful? → Click "Yes" on "Was this reply helpful?" or drop a Like!

Want more tips on Power Platform & AI? Follow me here:

🔗 LinkedIn: https://www.linkedin.com/in/paoloasnaghi/
▶️ YouTube: https://www.youtube.com/@BeyondThePlatforms
📸 Instagram: https://www.instagram.com/beyond_the_platforms/
🌐 Website: https://www.beyondtheplatforms.com/