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.
'. On the right, a Microsoft Teams chat bubble shows the rendered output: bold heading, two bullet list items, and a blue clickable hyperlink. A label connects the two views: 'Markdown rendered by Teams'.](/media/microsoft/ab-620/AB-620-e2-q020-b.webp)
Short Explanation
Teams renders Markdown natively in chat messages, so you can use bold, hyphen bullets, and [text](URL) links right in the message node. You don't need HTML or an Adaptive Card for basic formatting.
Full Explanation
The Markdown formatting approach is correct. Microsoft Teams supports Markdown rendering in chat messages, and Copilot Studio message nodes support Markdown syntax that Teams renders correctly. 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. The plain-text dash pseudo-bullet approach 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. The HTML message type approach 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. The Adaptive Card for all formatted text approach 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.