A Copilot Studio developer wants a message node to display a formatted response that includes bold text, a bulleted list of three steps, and a hyperlink to a documentation page. The agent is deployed on Microsoft Teams. Which approach should the developer use?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Teams renders Markdown natively in chat messages — use bold, - bullet lists, and [text](url) links directly in your message node. No HTML, no Adaptive Card needed for basic formatting. Answer: B.
Full explanation below image
Full Explanation
Microsoft Teams supports Markdown rendering in chat messages, and Copilot Studio message nodes support Markdown syntax that Teams renders correctly.
Option B is correct. In a Copilot Studio message node, the developer can use standard Markdown: text for bold, - or * for unordered list items, and [link text](https://docs.example.com) for hyperlinks. When the agent sends this to a Teams user, Teams renders the Markdown as formatted text with proper bold weight, bullet points, and clickable hyperlinks. This is the correct and simplest approach for basic formatting.
Option A is incorrect. Using dash characters as pseudo-bullets in plain text produces dashes in the text stream — visually similar on some clients but not semantically formatted and rendering inconsistently across channels.
Option C is incorrect. Microsoft Teams does not render arbitrary HTML tags in chat messages. Sending <ul><li>Item</li></ul> would display the raw HTML angle brackets as literal characters, not a formatted list.
Option D is incorrect. Plain message nodes in Copilot Studio absolutely support formatting through Markdown. Adaptive Cards are appropriate for interactive forms, structured data display, and rich media — they are not required for basic text formatting.