Using a flow bot instead of a service account to send to a teams channel results in the adaptive card not being rendered

i think that flow‑bot hits the raw bot‑fw invoke path so the renderer never hydrates the newer card bits; just drop the ver and re‑post, and maybe peek at the team’s msg‑policy after… folks usually run into that next.

Hi Philippos Aziz

As far as I know, this behavior occurs because Adaptive Cards posted as the Flow bot are more strictly validated by Microsoft Teams than cards posted as a user (service account).

That said, when the card contains unsupported schema versions or elements, Teams fails to render it and shows “We’re sorry, this card couldn’t be displayed.”

In order to resolve this issue, I think you can firstly try the approaches below:

Downgrade the Adaptive Card schema version

• Update the Adaptive Card JSON to use version 1.4 or lower.
• Cards using version 1.5 or newer features (such as Table, Action.Execute, or filtered ChoiceSet) are known to fail when posted by the Flow bot.

You can read here for more insight: https://mattjimison.com/2023/03/02/adaptive-cards-not-displaying-in-microsoft-teams/

Note: This information is provided as a convenience to you. These sites are not controlled by Microsoft, and Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please ensure that you fully understand the risks before using any suggestions from the above link.

Remove unsupported Adaptive Card elements

• Avoid newer elements not fully supported by Teams Flow bot, such as:
  • Table
  • ChoiceSet with style: "filtered"
  • Action.Execute
• Use supported alternatives like TextBlock, FactSet, ColumnSet, and Action.OpenUrl instead

You can read this discussion for more insight: https://github.com/microsoft/Teams-AdaptiveCards-Mobile/issues/30

Note:

• When posting Adaptive Cards as the Flow bot, ensure that the Power Automate (Workflows) app is enabled and allowed in Microsoft Teams, as the Flow bot relies on this app to post messages to channels.
• Additionally, if the card contains input fields or submits actions, use a “Post adaptive card … and wait for a response” action, non‑wait actions only support limited interactions (such as OpenUrl), and unsupported actions may cause the card to fail rendering.

Hope my answer will help you, for any further concern, kindly let me know in the comment section.

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.