System Error When Send Video URL

Hi Nguyen Trong Thuan,

Thank you for posting your question in the Microsoft Q&A forum. 

Please note that our forum is a public platform, and we will modify your question to hide your personal avatar in the description. Kindly ensure that you hide any personal or organizational information the next time you post an error or other details to protect personal data.

After reviewing the behavior you described, I found that similar issues have been reported in the past when handling video messages in the Teams client. The error often relates to an invalid video card aspect value, and currently, Teams does not fully support video cards in chat scenarios due to limitations around file size and security.

That said, Microsoft does provide a mechanism to embed audio and video files directly into Adaptive Cards, and supports media files hosted on OneDrive, SharePoint, YouTube, Dailymotion, or Vimeo. You can find full details in this article: https://learn.microsoft.com/en-us/microsoftteams/platform/task-modules-and-cards/cards/media-elements-in-adaptive-cards?tabs=desktop%2Cdeveloper-portal-for-teams.

From the official samples, the media URLs used are typically shareable HTTPS links rather than direct streaming endpoints (e.g., MP4 or HLS .m3u8). This distinction is important because Teams may fail to render or parse streaming URLs correctly.

Additionally, in the Teams Admin Center, there is a Video messages option under Messaging > Messaging policies. This setting is usually turned on by default, but it’s worth double-checking to ensure no related configuration has been disabled.

Finally, you can collect Teams client diagnostic logs for deeper troubleshooting (usually for Microsoft Support). Instructions are available here: Microsoft Teams log files.

Hope this helps.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Thank you for the clarification.

I’d like to add a bit more technical context from my testing so far:

1. Adaptive Card Media element As you mentioned, the media element in Adaptive Cards only works with a limited set of providers (YouTube, OneDrive, SharePoint, Vimeo, Dailymotion). This is documented behavior, and I confirm that it works only for these shareable providers. However, in my chatbot scenario, the media URL is dynamic and is returned from an API call (e.g., a replay URL generated at runtime). The URL cannot be predetermined or uploaded to OneDrive/SharePoint ahead of time, so the Adaptive Card media element is not a viable option.
2. Streaming URLs vs Static URLs I also confirm that Teams will not render:
   • Direct MP4 URLs served from a CDN
   • HLS links (.m3u8)
   • Internal or external HTTPS links that contain query parameters (?start=xxx&end=xxx)
   Even when the file itself is fully accessible in the browser. In my case, the API returns a dynamic, time-based replay link such as: https://.../abr.m3u8?start=xxxx&end=xxxx&mode=1 Sending this URL inside a Copilot Studio bot immediately results in the error: SystemError – Something unexpected happened
3. Adaptive Card fallback (Action.OpenUrl) Even when wrapped in a simple Action.OpenUrl button, Teams still rejects the message when the URL is a streaming endpoint or contains certain patterns. The same card works if I replace the URL with a static non-media link.
4. Behavior inside Copilot Studio The exact same message works inside the Copilot Studio “Test your copilot” sandbox, which suggests that the error is triggered by the Teams client parser rather than the Copilot runtime.
5. Question Given that the media URLs in my use case are dynamic and not hosted on OneDrive/SharePoint/YouTube, is there any officially supported way to send such URLs through a Teams-integrated Copilot bot without triggering the SystemError client-side? Alternatively, is there any documented restriction on what URL patterns Teams is allowed to accept inside bot messages or Adaptive Cards?

I appreciate your help in clarifying this, as it seems to be a limitation specific to the Teams client

rather than the Adaptive Card schema itself.