The roadmap entry marks the feature as In development. It targets General Availability with an estimated date of November 2026. The listed platforms are Desktop, Linux and Mac, and the cloud scope is Worldwide (Standard Multi-Tenant). The roadmap itself says its release dates and descriptions are estimates and can change. Treat November as the plan, not a promise.
What Microsoft has actually announced
The roadmap entry is short. Here is what it confirms:
- What changes: Markdown support in the Teams compose box expands, so there are more ways to structure and format messages.
- Where: Desktop, Linux and Mac, per the roadmap metadata. The entry does not mention web or mobile.
- Who: Worldwide Standard Multi-Tenant tenants. GCC, GCC High, DoD and other sovereign clouds are not listed.
- When: Estimated November 2026, with the status still In development.
Here is what it does not say:
- Which new Markdown elements or syntax are coming
- Whether existing shortcuts will behave differently
- Whether users or admins need to turn anything on
- How messages with the new formatting will look on clients outside the listed platforms
That last group matters. Asking "will we finally get tables?" is reasonable, but nothing Microsoft has published for this item answers it.
Section summary: This is a confirmed roadmap plan with a target month and a platform list. The actual feature set has not been published.
Where Teams Markdown stands today
To see what "expanded" might mean, start with what works now. Microsoft's support documentation says Markdown gives you a live preview of your formatted text inside your compose box as you type, and you can always undo your formatting by pressing Ctrl+Z. Microsoft also admits that Teams uses a Markdown-style syntax. While we refer to it as "Markdown," it doesn't fully match standard Markdown, and some formatting may behave differently.
Microsoft currently documents this compose-box syntax:
| Formatting | What you type in Teams |
|---|---|
| Bold | *bold text* |
| Italic | _italic text_ |
| Strikethrough | ~strikethrough~ |
| Numbered list | A number followed by the item |
| Bulleted list | * Item or - Item |
| Hyperlink | [Text](URL) |
| Inline code | A backtick at each end |
| Multi-line code block | Three backticks |
| Headings 1–3 | #, ##, ### plus heading text |
| Block quote | > |
If you come from GitHub or another Markdown editor, two of these will catch you out. Teams uses one asterisk for bold and one tilde for strikethrough, where standard Markdown uses two. A Markdown guide published this month by Markdific notes that Teams uses one asterisk for bold and one underscore for italic, which differs from standard Markdown conventions.
Code blocks get extra tooling. Microsoft's code-block documentation lists three ways to insert one: type /code, press Ctrl+Shift+Alt+B on Windows and web (Cmd+Shift+Option+B on Mac), or type three backticks. You can pick a language for syntax highlighting, wrap long lines, and turn the block into a collaborative Loop component before you send it. Microsoft also says code blocks created on desktop display on mobile, but you can only create them on desktop.
Mobile is the other big gap. Microsoft's Markdown page says for now, you can view but not generate Markdown-formatted messages on your mobile device. Use the desktop or web app to collaborate and share code. Since the new roadmap item lists only Desktop, Linux and Mac, don't expect it to change mobile authoring.
Section summary: Teams already has a working but non-standard set of Markdown shortcuts for desktop. The expansion adds to that base. It is not a first-time launch.
The paste problem nobody puts in the release notes
Many users get frustrated when they paste Markdown into Teams instead of typing it. Several third-party guides describe the same behavior. One from Markdown Editor Online says the compose box converts bold, italic, headings, lists, links, and triple-backtick code blocks as you enter them, but pasted Markdown arrives as plain text with the symbols still showing. The same guide calls the conversion a typing shortcut, not a parser.
This is third-party observation, not Microsoft documentation, and paste behavior can vary by client version. It does explain a common complaint: AI chatbots answer in Markdown, and that output often shows up in Teams as raw ## and **. The roadmap entry doesn't say whether the expansion changes paste handling. Watch for this one when the feature arrives.
A clue from the developer side
Teams clients can already display more Markdown than people can type. Microsoft's developer documentation for agent and bot messages describes an opt-in "extended Markdown mode," enabled by setting a message's textFormat to extendedmarkdown. Microsoft says this mode supports additional CommonMark and GitHub Flavored Markdown features, including:
- Fenced code blocks with language identifiers
- LaTeX/KaTeX math, inline and as blocks
- Markdown image syntax
- Pipe-delimited tables with column alignment
- Task lists, with read-only checkboxes
- Inline citations
Microsoft tells developers to test these messages with the latest Teams desktop, web, iOS and Android clients. In other words, the rendering engine for richer Markdown already exists in Teams.
The caveat matters: this is a separate feature for apps and agents. Nothing ties it to the roadmap item. It would be tempting to assume tables and task lists are coming to the human compose box because bots already have them, but that is speculation. It is fair to say the gap between what agents can send and what people can type is now obvious. An expansion of compose-box Markdown would narrow it, whatever form it takes.
Section summary: Teams can already render tables, task lists and math from agents. Whether people get any of that in the compose box is still unannounced.
What users and IT admins should do now
For everyday users on Windows, Mac or Linux desktop:
- Learn the current syntax. Single asterisks for bold, single tildes for strikethrough,
#to###for headings,>for quotes. - Type, don't paste, if you want shortcuts to convert. Press Ctrl+Z (Command+Z on Mac) to undo a conversion you didn't want.
- Use the code-block tools (
/code, the keyboard shortcut, or three backticks) for anything longer than a line. - Don't assume Markdown copied from GitHub, a wiki or an AI assistant will render the same way. It probably won't until Microsoft documents otherwise.
For IT administrators and help desks:
- Watch Message Center for the matching post. That is usually where Microsoft gives the actual feature list and any admin controls.
- Brief support staff that current Teams formatting doesn't follow standard Markdown, so "bold doesn't work" tickets can be closed with "use one asterisk."
- Check your cloud. The roadmap lists only Worldwide Standard Multi-Tenant. Government and sovereign-cloud tenants shouldn't plan around November.
- Update internal docs and training after the feature ships and Microsoft publishes the new syntax. Teaching rules that are about to change is wasted effort.
- Expect mixed-client teams. Authoring is listed for desktop platforms only. Users working mostly on mobile won't gain new authoring options from this item.
The bigger picture
The change is small, but it reflects a broader trend. Markdown has spread from developer tools into everyday business writing, partly because AI assistants produce so much of it. Slack, Discord and GitHub have all trained people to type asterisks and expect formatting. Teams has had Markdown-style shortcuts for years, and its own documentation still describes them as only partly Markdown.
The question is whether "expanded" means a few more shortcuts or real CommonMark compatibility. Microsoft hasn't said, and the developer docs show that full compatibility with existing formatting behavior isn't simple. Microsoft made extended Markdown opt-in for agents because it is not fully backwards compatible with the default formatting behavior. The human compose box could face similar tradeoffs.
Until the feature list arrives, here is the bottom line: Microsoft is improving Markdown in the Teams compose box on desktop, Mac and Linux. GA is targeted for November 2026, and the details are still unannounced. In the meantime, use one asterisk for bold.