Use Adaptive Cards in Copilot Studio

Note

This article describes features used in agents or agent flows powered by the standard harness.

Adaptive Cards describe user interface content in JSON. A host app, such as Microsoft Teams, renders the card in its own interface. Use cards in agents to collect user input or show information.

The host app determines which card versions and features are supported. Choose a schema version that works in every channel where you publish your agent.

Note

Copilot Studio supports the Adaptive Cards schema versions 1.6 and earlier. However, the appropriate schema version depends on the targeted host app:

• The Bot Framework Web Chat component (that is, the default website integration pattern) supports version 1.6 but doesn't support Action.Execute
• The live chat widget (used for Omnichannel for Customer Service) is limited to version 1.5
• Teams is also limited to version 1.5

In addition, Copilot Studio only renders version-1.6 cards in the test chat, not on the canvas.

Learn more in AdaptiveCard.

Choose the node that fits your task:

• Use an interactive Adaptive Card node to ask for information.
• Add an Adaptive Card to a Message or Question node to show information.

Tip

Create cards in the built-in designer described in Ask questions with Adaptive Cards, or reuse a card from another topic and adapt it to your task.

Learn more about the schema and samples at Adaptive Cards.

Best practices for interactive cards

When you use interactive Adaptive Cards (cards with Submit buttons), include data that identifies the card or action in each submit action. Validate that data when processing the response, especially when earlier cards remain visible. A fixed action identifier distinguishes actions; it doesn't by itself prevent duplicate submissions or identify each rendered instance of a card.

Learn more in Submit button behavior for agents with consecutive cards.