How to Export and Read Microsoft Copilot Conversations as Real Documents

Microsoft Copilot now sits inside Word, Excel, Outlook, Teams, GitHub, and the standalone Copilot app, which means a single workday can produce four or five different Copilot threads across four or five different surfaces. Each one looks fine in the moment, and none of them survives a week in any readable form. The export buttons are inconsistent, the share links die when a tenant policy flips, and the chat panels reset their scroll position the moment you switch tabs. If you want to reread a Copilot answer two months from now, the chat window is not where it lives. This post is the workflow we use to get Copilot threads out of Microsoft 365 and into a real document library, with code blocks, citations, and Office artifacts intact.

The same shape works for the consumer Copilot app, Copilot in Microsoft 365, Copilot in GitHub Chat, and the older Bing Chat exports if you still have them sitting in a OneDrive folder somewhere. Each surface needs its own export path, but they all land in the same place: a plain markdown file you can render once and keep for good. The rest of the post walks each surface in turn, then covers the reader setup and the library habit that makes the whole thing stick. None of the steps require admin access, scripts, or a paid add-on, which is the point.

Why Copilot is harder to export than ChatGPT

Most other assistants have one surface and one export. Copilot has at least four, and that is the root of the problem. The consumer Copilot app at copilot.microsoft.com keeps a chat history per Microsoft account, but the export option only appears on some conversations and only on desktop. Copilot in Microsoft 365 is gated by your tenant admin, so the same button can be present on Monday and gone on Tuesday after a policy change. Copilot in Teams stores threads inside the meeting object, which means the answer dies when the meeting is deleted. Copilot in GitHub Chat keeps a transcript per repo, but only for the current browser session unless you turn on the new history setting in your account preferences.

That fragmentation is the reason a single Copilot workflow needs more steps than the equivalent ChatGPT export or Claude export routes. There is no one button. There are four buttons, and two of them lie depending on which tenant or account you happen to be signed into at the time. Anyone who has worked across both a personal Microsoft account and a corporate tenant in the same week has felt this. The fix is to stop relying on the in-product buttons and treat each surface as its own export problem.

The export route that works on each surface

The goal is the same as for any other assistant. Get the conversation out as plain markdown, render it once into a real document, and keep the rendered copy in a library you can search later. The path to plain markdown is different for each Copilot surface, but the destination is the same. We use a single markdown folder per surface so the export step never has to think about routing, only about format.

For the consumer Copilot app, open the conversation, click the three-dot menu in the top right, and choose Export. The desktop web app gives you a PDF or a Word document, neither of which is what you want. Open the Word file, select all, and paste into a plain markdown editor. The code blocks survive the paste, and the citation chips become numbered footnotes, which is honest and useful when you reread the thread later.

For Copilot in Microsoft 365, the cleanest route is the Loop component. Ask Copilot to summarize the thread, then click the Loop icon under the response and open the resulting page in your browser. The Loop page exports as markdown directly from its own three-dot menu, and the export keeps the underlying SharePoint file references intact. Those references are the part that gets lost in a screenshot, and they are usually the fastest way back to the original Office file weeks later when context is thin.

For Copilot in Teams, open the meeting recap in the Teams web app, expand the AI notes panel, and use the Copy as markdown option that shipped in the late 2025 update. It is hidden behind a small clipboard icon on the right side of the panel header, which is easy to miss the first time. For Copilot in GitHub, the most reliable path is the gh-copilot CLI: the command gh copilot history --export dumps every recent thread as a folder of markdown files, one per conversation, with code blocks already fenced and language-tagged. The CLI route also bypasses the per-session browser history limit, which is the part of GitHub Chat that loses threads the most often.

Rendering the markdown into a document worth keeping

Raw markdown is not the goal. A rendered document is. Once the export sits in a markdown file, open it in a reader that handles code, KaTeX math, Mermaid diagrams, and footnote-style citations in one pass. Prism MD does this without a build step, which is why we use it as the default destination for every assistant in this series, including the Gemini and DeepSeek routes covered earlier. The reader choice matters more for Copilot than for most other assistants because Copilot answers carry artifacts the chat UI hides on first read.

A few details matter on the Copilot side specifically, and they are easy to test on any candidate reader before committing. Footnote rendering, tenant-scoped link preservation, mixed-language code blocks, and Mermaid support together cover most of what a Copilot thread will throw at the reader. The list below is the smoke test we run on any new reader candidate before moving real work into it. If a reader drops any of these, the rendered document loses the part of the answer that made it worth exporting in the first place.

• Copilot citations come back as superscript numbers with a footnote block at the bottom, so a reader that renders Markdown footnotes natively keeps the click-to-jump behavior intact.
• Copilot in Microsoft 365 often includes inline references to SharePoint files, and those URLs are tenant-scoped, so the rendered document needs to keep them as live links rather than flattening them to plain text.
• Copilot for GitHub answers contain shell and code blocks that frequently mix languages, so a reader that supports per-block language hints reads back the diff cleanly weeks later.
• Copilot in Teams notes sometimes include Mermaid diagrams of meeting flow when you ask for them, so Mermaid support is worth checking before the first long meeting recap.

The reason this matters is that a Copilot answer is rarely prose alone. It is usually a small artifact, a code block, a table, a citation footnote, or a Loop card, embedded in a paragraph of context. If the reader drops any of those parts, the answer stops being useful as a reference, and the export step you went through becomes wasted work. The render step is the part that turns the export into something you will open again.

Building a Copilot library you can search later

One Copilot thread is a document. Twenty Copilot threads is a library, and that is where the workflow earns its keep. Once the export habit is in place, the next problem is finding the right thread three weeks later when a teammate asks a question you already answered in a Teams meeting recap or a GitHub Chat session. A library that you cannot search is a graveyard, and most Copilot threads end up in one because the export step never happened in the first place.

The pattern that works for us is one folder per Copilot surface, a flat filename convention with the date and a three-word topic, and a daily sync to a personal cloud drive. We covered the search side of this in detail in the save and reread workflow, and the same rules apply here. The only Copilot-specific addition is keeping the SharePoint reference URLs intact, because they are often the fastest way back to the original Office file when the conversation alone does not have enough context. If your team is going to read these threads together rather than alone, a shared rendered library beats a screenshot every time, and the team sharing pattern in the series covers that case in more depth.

FAQ on Copilot exports and reading

Does Copilot have a built-in export to markdown?

Not consistently across surfaces, and that is the part that surprises people the most. The consumer Copilot app exports to PDF or Word, neither of which is markdown without a conversion step. Copilot in Microsoft 365 exports through Loop pages, which do support markdown directly. Copilot in Teams added a Copy as markdown button in late 2025, and Copilot in GitHub exports cleanly through the gh-copilot CLI. There is no single button that covers all four surfaces, which is why the workflow above treats each one separately.

Can I export Copilot conversations from my phone?

Only the consumer Copilot app on iOS and Android exposes an export option on mobile, and even there it appears on some conversations and not others. The reliable route is to open the same thread on copilot.microsoft.com on a desktop browser and export from there. Copilot in Microsoft 365 on mobile does not expose Loop export at all in the current build. Copilot in Teams on mobile shows the meeting recap but hides the Copy as markdown control behind the desktop-only panel layout. In practice, mobile is a reading surface for the rendered output, not a capture surface for the raw export.

Will tenant admin policies block these exports?

They can, and you should expect them to at some point in any enterprise tenant. Copilot in Microsoft 365 export options are tenant-scoped, which means an admin can disable Loop, the export menu, or both. The consumer Copilot app and the GitHub CLI route are not affected by tenant policy because they sit on a separate account boundary. If your tenant is locked down, the workaround is to do the Loop export on a personal Microsoft account where the policy does not apply, then bring the markdown file back into your work environment manually.

What about Bing Chat history from before the Copilot rename?

Old Bing Chat threads still live in the Copilot account history if the same Microsoft account is signed in. The same export route applies, and the markdown output looks identical to current Copilot threads because the underlying conversation format did not change with the rename. Anything older than the 90-day default retention window is gone, and there is no recovery path for that. If you have a thread you want to keep from that era, the time to export it is before the retention window closes, not after.