Microsoft Teams Markdown: Messages, Cards & Webhooks (2026)
Master Markdown in Microsoft Teams — chat compose formatting, the differences from GitHub GFM, Adaptive Card markdown, and incoming-webhook message formatting for bots and CI.
Microsoft Teams supports Markdown in two places that behave differently: the chat compose box where people type messages, and Adaptive Cards / incoming webhooks where bots and CI pipelines post formatted updates. Each accepts a different subset, and mixing them up is why your webhook message renders as raw asterisks.
This guide covers both surfaces, the differences from GitHub Flavored Markdown, and copy-paste recipes for standups, incident alerts, and CI notifications.
Where Markdown works in Teams
| Surface | Markdown support |
|---|---|
| Chat & channel compose box | ✅ subset (typed or auto-format) |
Adaptive Cards (TextBlock) | ✅ limited subset |
| Incoming webhooks (legacy MessageCard) | ✅ subset |
| Workflows / Power Automate posts | ✅ via cards |
| Wiki / Loop components | partial (rich editor) |
The compose box is for humans; cards and webhooks are for automation. Both use Markdown, but the allowed tags differ — always test in the actual surface.
Compose box formatting
In the message box, Teams accepts typed Markdown that converts as you type:
**bold**
*italic* or _italic_
~~strikethrough~~
# Heading 1
## Heading 2
### Heading 3
- bulleted item
1. numbered item
> block quote
`inline code`
[link text](https://trymarkdownviewer.com)
Code blocks use triple backticks:
```json
{ "status": "ok" }
```
Unlike Slack, Teams uses doubled ** for bold — the same as GitHub. If you copy a release note from a GitHub README, the bold survives. Headings #–### render as real heading styles in the compose box (a feature Slack and Discord lack).
Compose box keyboard shortcuts
| Action | Windows | macOS |
|---|---|---|
| Bold | Ctrl + B | ⌘ + B |
| Italic | Ctrl + I | ⌘ + I |
| Underline | Ctrl + U | ⌘ + U |
| Bulleted list | Ctrl + . | ⌘ + . |
| Numbered list | Ctrl + / | ⌘ + / |
| Code block | Ctrl + Shift + K | ⌘ + Shift + K |
Use the Format button (the A with a pen) to expand the rich editor for tables, highlights, and quotes that are awkward to type.
What the compose box does NOT do
| Feature | Status | Note |
|---|---|---|
| GFM tables (typed) | ❌ | Use the Format toolbar's table button instead |
| Task list checkboxes | ❌ | Use ✅ / ⬜ emoji or a Planner tab |
| Footnotes | ❌ | Not supported |
| Nested code in tables | ❌ | Flatten or attach a file |
| Mermaid diagrams | ❌ | Paste a rendered image |
Teams' typed Markdown is closer to CommonMark than full GFM — pipe tables typed by hand won't render; you must use the toolbar's table insert.
Adaptive Cards markdown
Bots and apps post Adaptive Cards. A TextBlock element supports a limited Markdown subset:
{
"type": "TextBlock",
"wrap": true,
"text": "**Deploy complete** for _v2.4.0_\n\n- Region: us-east-1\n- Status: passing\n\n[View logs](https://example.com/logs)"
}
Adaptive Card TextBlock Markdown supports:
**bold** _italic_
- bulleted lists
1. numbered lists
[links](https://example.com)
It does not support headings, tables, images-via-markdown (use an Image element), code blocks, or strikethrough. Line breaks need \n\n between blocks — a single \n is often collapsed.
Incoming webhooks (CI & alerts)
Legacy MessageCard webhooks (still common for CI integrations) accept Markdown in their text and sections:
{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"summary": "Build passed",
"themeColor": "2EB67D",
"sections": [{
"activityTitle": "**CI: main branch**",
"text": "Build `#1284` passed in 3m 12s.\n\n- Tests: 412 passed\n- Coverage: 91%"
}]
}
Set "markdown": true on a section if your tenant defaults it off. Microsoft is migrating webhooks toward Workflows (Power Automate) with Adaptive Cards — new integrations should target Adaptive Cards, but MessageCard still works for now.
Teams vs GitHub vs Slack formatting
| Feature | Teams compose | GitHub | Slack |
|---|---|---|---|
| Bold | **text** | **text** | *text* |
| Italic | *text* / _text_ | *text* | _text_ |
| Strikethrough | ~~text~~ | ~~text~~ | ~text~ |
| Headings | #–### | #–###### | ❌ |
| Tables | toolbar only | typed GFM | Canvas only |
| Links | [text](url) | [text](url) | <url|text> |
| Code block | ``` | ``` | ``` |
Teams sits closest to GitHub for bold and links — handy when reposting README content. See the GitHub README guide for the source format and the Slack guide for the contrast.
Workplace recipes
Daily standup (compose box)
**Standup — June 3**
**Yesterday**
- Shipped webhook retry logic
- Fixed table rendering in cards
**Today**
- Adaptive Card templates
- Load test the bot
**Blockers**
- Waiting on API key rotation
Incident alert (Adaptive Card text)
**🔴 INC-284 — elevated latency**
- Impact: ~15% of requests > 2s
- Status: investigating
- Lead: @alice
[Runbook](https://example.com/inc/284)
CI notification (webhook)
**✅ Deploy succeeded** — `v2.4.0` to production
- Duration: 4m 02s
- Migrations: 3 applied
- Changelog: https://example.com/changelog
Common Teams Markdown mistakes
1. Typing pipe tables in the compose box. They render as raw text — use the Format toolbar's table button.
2. Expecting headings inside Adaptive Cards. Card TextBlock ignores # — use the size/weight properties instead.
3. Single \n in card text. Use \n\n for real line breaks between bullets and paragraphs.
4. Slack-style *bold* in Teams. Teams needs **bold** (doubled). Single asterisks make italic.
5. Code blocks in Adaptive Cards. Not supported — put code in the compose box or attach a file.
6. Forgetting "markdown": true on webhooks. Some tenants default it off, leaving raw asterisks.
Build and preview your message body
Draft long messages in the Markdown editor first, then map to the target surface:
- Compose box: keep
**bold**, headings, lists; rebuild tables with the toolbar. - Adaptive Card: strip headings/tables; convert to bold +
\n\nseparated bullets. - Webhook: keep bold, lists, inline code; avoid headings.
For CI pipelines that post to Teams, render Markdown to a sanitized intermediate with the render API, then down-convert to the card subset. Validate the Markdown source first with the validate API so malformed notes never reach the channel.
Related articles
- Slack Markdown guide — single-asterisk bold and
<url|label> - GitHub README guide — same doubled-bold syntax
- Markdown lint in CI with a GitHub Action — gate notes before posting
- Docs-as-code guide — pipelines that feed Teams
- Markdown cheat sheet — standard reference
Quick reference
| Syntax | Compose | Card | Webhook |
|---|---|---|---|
**bold** | ✅ | ✅ | ✅ |
*italic* | ✅ | ✅ | ✅ |
~~strike~~ | ✅ | ❌ | ✅ |
# Heading | ✅ | ❌ | partial |
- list | ✅ | ✅ | ✅ |
[text](url) | ✅ | ✅ | ✅ |
```code``` | ✅ | ❌ | ✅ |
| pipe table | toolbar | ❌ | ❌ |
Teams Markdown is really three subsets wearing one name. Learn which surface you're posting to — compose box, Adaptive Card, or webhook — and the raw-asterisk surprises disappear.
Written by Markdown Viewer Team. Found this useful? Try the editor →
Keep reading
Hand-picked articles related to this one.
Every Slack Markdown feature explained — bold, italic, code, lists, quotes, links, block Kit vs mrkdwn, Canvas formatting, and the quirks that break when you paste from GitHub.
Every WhatsApp formatting trick — bold, italic, strikethrough, monospace, bulleted and numbered lists, block quotes, and inline code — plus what breaks when you paste from elsewhere.
Complete Telegram formatting guide — MarkdownV2 vs legacy Markdown vs HTML parse modes, the full escaping rules, spoilers, custom emoji, and in-app shortcuts that actually work.