The feature is listed as in development, with general availability targeted for November 2026. Here's what Microsoft has committed to, what it hasn't said, and how this differs from the side-by-side options Teams already has.
What the roadmap entry says
According to Microsoft's roadmap description, when you open a PDF, Markdown, or HTML file from a Teams chat or channel message, the conversation will appear next to the file. Teams will also take you directly to the message where the file was shared. Microsoft says the goal is to let you catch up on the discussion and reply without closing the file preview or switching back to chat.
The roadmap record lists these details:
| Field | Roadmap value |
|---|---|
| Roadmap ID | 574094 |
| Product | Microsoft Teams |
| Status | In development |
| Platforms | Desktop, Mac, Web |
| Release ring | General Availability |
| Cloud instance | Worldwide (Standard Multi-Tenant) |
| Target GA | November 2026 |
The navigation part may matter as much as the split view. In a channel with hundreds of replies, finding the original "here's the draft, please review by Friday" message is often harder than reading the file. Jumping straight to that point in the thread gives you the context behind the file without scrolling for it.
Section summary: PDF, Markdown and HTML files opened from chats or channel messages will show the conversation beside the preview and jump to the original message. The rollout targets desktop, Mac and web in the worldwide commercial cloud.
What the entry doesn't say
The roadmap entry is short, and several obvious questions aren't answered in it:
- Other file types. Only PDF, Markdown and HTML are named. Nothing in the entry mentions Word, Excel, PowerPoint, images or video.
- Mobile. The listed platforms are Desktop, Mac and Web. Teams on iOS and Android isn't mentioned.
- Sovereign clouds. Only the Worldwide (Standard Multi-Tenant) instance is listed. GCC, GCC High, DoD and other national clouds aren't covered.
- Admin controls and licensing. The entry doesn't mention a policy toggle, a tenant setting or a license requirement.
- Editing. The entry describes previewing a file next to the conversation. It doesn't say you'll be able to edit or annotate the file in that view.
- Other entry points. The described trigger is opening a file from a chat or channel message. Files opened from meeting chats, the Files app or channel file tabs aren't addressed.
Microsoft also warns on the roadmap page itself that its entries are estimates and that all information is subject to change. Entries can be removed once a feature ships, or if it's cancelled or postponed. Treat November 2026 as a target, not a date to plan around.
Section summary: The confirmed scope is narrow. Anything beyond three file types, three platforms and one cloud is unconfirmed.
How Teams previews files today
Microsoft's current support guidance on sending files explains why this matters. Microsoft says that messages with image, video and many types of document attachments will automatically include a preview of the attached files, and that messages containing a single PDF or 3D files (GLB, STIL, FBX, .OBJ) can be previewed inline. To open one, you select Preview to view the file directly within the chat or channel.
The same documentation lists limits that are worth knowing before the new feature arrives:
- Permissions and sensitivity labels. If you don't have permission to view the file or the file is encrypted using certain sensitivity labels, you won't see a preview. However, you can request permission to access the file.
- External chats. Messages sent in chats with external users also won't include file previews.
- Unsupported formats. Certain file types, such as .zip files, can't be previewed.
The roadmap entry doesn't say whether the new side-by-side view will follow these rules, loosen them or work around them. Since the feature is built around the preview experience, it seems likely that the current permission and labeling limits will carry over. That's an inference, not something Microsoft has stated. If your organization relies heavily on sensitivity labels or external collaboration, test this rather than assume it.
Section summary: Today's previews already stop at permissions, some sensitivity labels, external chats and unsupported formats. Microsoft hasn't said whether the new feature changes any of that.
This isn't the Edge side-by-side feature
Teams already has a side-by-side mode, but it covers something different. Microsoft's support documentation explains that when you open a webpage link from a Teams chat while logged into Microsoft Edge, the chat window opens in the Edge browser to view the content and chat side-by-side. The aim, in Microsoft's words, is to view links without needing to switch back and forth between apps.
That feature is about web links, and it happens in Edge. Roadmap item 574094 is about files: PDF, Markdown and HTML attachments opened inside Teams. The goal is similar, but the trigger, the content and the app are different. If you've already handled the Edge link behavior in your environment, this new feature is a separate change.
There's a developer-side precedent too. Microsoft Learn documents Collaborative Stageview, which lets Teams apps open content in a new Teams window with a conversation side panel. Microsoft recommends it when content is opened from a chat, channel or channel tab. That shows Teams has supported content-plus-conversation layouts for some time. Microsoft hasn't said that roadmap item 574094 is built on Stageview, though. The same documentation says the Teams web client supports only the full-screen Stageview Modal, not the pop-out layouts, so it can't tell us how the new file feature will behave in the browser. Since the roadmap lists Web as a platform, browser users should wait to see how it actually looks.
Section summary: Edge already pairs web links with chat, and developers have Collaborative Stageview. The new feature applies the same idea to PDF, Markdown and HTML files in Teams.
Who benefits
This is a small change, and it doesn't need to be more. Some likely use cases:
- Developers and DevOps teams. Markdown support suggests Microsoft has technical teams in mind. READMEs, runbooks, design notes and changelogs often get passed around in chat, and the reasoning behind a change usually sits in the thread rather than the file.
- Reviewers and approvers. Contracts, specs and reports are commonly shared as PDFs. Reading the document next to the "can you check section 4?" message is easier than switching back and forth.
- Anyone receiving exported reports. Many tools produce HTML reports and dashboards. Previewing one next to the discussion about it saves a trip to the browser.
- People catching up after time off. Jumping to the message where the file was shared helps when a channel has moved on since.
Microsoft hasn't published productivity figures for this feature, and none are claimed here. The benefit is fewer context switches.
What IT admins should do
Microsoft hasn't documented any policy controls, so the preparation is simple:
- Watch roadmap ID 574094 for status changes from "In development" to "Rolling out." Microsoft says entries can be removed or changed.
- Check the Microsoft 365 Message Center for a related post. That's usually where Microsoft adds rollout details and admin guidance.
- Plan a quick test when it appears in your tenant. Try a labeled PDF, a file shared in an external chat, a Markdown file in a channel, and both the desktop and web clients.
- Brief your help desk. Users will ask why their Word documents don't open this way and why a PDF from an external partner shows no preview. Based on the roadmap scope and current preview rules, those are the most likely sources of confusion.
- Don't promise mobile or sovereign-cloud support. The roadmap doesn't list either.
Bottom line
Roadmap item 574094 puts the conversation next to the file and takes you to where it was shared, which is how many people expected Teams to work already. The scope is narrow: PDF, Markdown and HTML files, opened from chats and channel messages, on desktop, Mac and web, in the worldwide commercial cloud. The target is November 2026, and Microsoft says that date can change.
Questions about external chats, sensitivity-labeled files, browser behavior and mobile support are still open. Expect firmer answers once the feature reaches a Message Center post or a real tenant.