Topic: AI chat export
Microsoft Copilot Export — How to Retrieve Conversation History (2026)
Microsoft Copilot — whether the consumer version at copilot.microsoft.com or the enterprise Microsoft 365 Copilot embedded in Teams, Word, and Outlook — does not have an export button. There is no conversations.json, no ZIP download, no structured data export equivalent to what ChatGPT or Claude provide. This page documents what is stored, who can access it, and the three paths available: the Microsoft privacy dashboard for personal account data, Microsoft Purview for M365 Copilot admins, and the Microsoft Graph API for developers.
TL;DR
No user-facing export button exists in either consumer or enterprise Microsoft Copilot as of 2026. Consumer Copilot conversation history is viewable in-app and partially accessible via the Microsoft account privacy dashboard (account.microsoft.com/privacy) and GDPR data requests (privacy.microsoft.com). Microsoft 365 Copilot in enterprise organizations is covered by Microsoft Purview eDiscovery — but that path requires an IT admin with eDiscovery permissions, not a self-service user action. The Microsoft Graph API provides programmatic access to Copilot interaction history where the feature is enabled in the tenant. For individual users who need to preserve specific conversations: copy-paste from the in-app history sidebar is the only self-service path before the session expires or the account changes.
Which Microsoft Copilot? (disambiguation)
Microsoft has applied the "Copilot" name to several distinct products. This page covers two:
- Microsoft Copilot (consumer) — the AI assistant at copilot.microsoft.com, formerly known as Bing Chat (before 2024). Available free with a Microsoft account; a paid Copilot Pro tier adds priority access and enhanced features. Conversations happen in the browser or the Copilot mobile app. Powered by GPT-4o through Microsoft's Azure OpenAI Service deployment.
- Microsoft 365 Copilot (enterprise) — the AI assistant embedded in Microsoft 365 apps: Teams, Word, Excel, PowerPoint, Outlook, and the Microsoft 365 Chat (formerly Copilot chat in Teams). Licensed per-user, typically through enterprise M365 E3/E5 with a Copilot add-on. Conversations in Teams Copilot, Word Copilot, and M365 Chat are stored as part of the M365 tenant and are covered by Purview compliance policies.
This page does not cover GitHub Copilot (AI code completion for IDEs — a separate product with separate usage logs, not conversation-style AI chat), Copilot Studio (the Power Platform bot-building product), or Dynamics 365 Copilot features (CRM/ERP context). Each of those has its own data handling and access model.
Consumer Copilot: what's stored and how to access it
When you use Microsoft Copilot at copilot.microsoft.com with a signed-in Microsoft account, your conversation history is stored associated with your account. The in-app history sidebar displays recent conversations; the retention period depends on account type and Microsoft's current data retention policies, but conversations typically persist for at least several months of inactivity.
In-app history sidebar
The most accessible path: the conversation history sidebar in the Copilot interface shows past conversations with date labels. You can open any past conversation, read its content, and copy-paste text. There is no "select all conversations" or "export to file" option — each conversation must be opened and copied individually. For small numbers of important conversations, this is the practical recovery path.
Microsoft account privacy dashboard
The Microsoft account privacy dashboard at account.microsoft.com/privacy provides data access controls for your Microsoft account. The "Activity history" section may include records of Bing searches and some Copilot activity, depending on your privacy settings. This typically shows activity metadata — queries, timestamps — rather than full conversation transcripts. The dashboard also provides controls to view and clear activity history, and to request a copy of your data.
Privacy data request
A structured data export request is available through the Microsoft Privacy Request Center at privacy.microsoft.com. Submit a request under "Data subject requests" → "Access." Microsoft will compile account data and send a download link, typically within 30 days. The response includes account profile data, activity records, and some product usage data. Full Copilot conversation transcripts are not always included — Microsoft's privacy documentation notes that inference data retention depends on the product and your account's data retention settings. The response is informative about the account but often incomplete for conversation recovery.
Microsoft 365 Copilot: the enterprise access model
Microsoft 365 Copilot conversations are stored within your organization's Microsoft 365 tenant infrastructure. This is fundamentally different from the consumer product: you are not the data owner — your organization is. The implications:
- Individual users cannot self-serve their Copilot conversation history via a personal export button. The export path requires IT admin involvement.
- Your organization's Purview retention policies determine how long Copilot interaction history is retained. If the policy is set to delete after 30 days and 31 days have passed, the conversation is gone.
- When you leave an organization, your Copilot conversation history from M365 Copilot stays in the organization's tenant — you do not take it with you. This is similar to Microsoft Teams messages and OneDrive files in most enterprise configurations.
Microsoft Purview eDiscovery (admin-only path)
Microsoft 365 Copilot interactions are indexed by Microsoft Purview as a content type available for eDiscovery and compliance purposes. An M365 admin with the eDiscovery Manager or eDiscovery Administrator role can:
- Open the Microsoft Purview compliance center at compliance.microsoft.com
- Navigate to eDiscovery → Standard (or Premium for advanced features)
- Create a case scoped to "Microsoft Copilot interactions" as the content type
- Select the relevant users and date range
- Run a content search and export the results
The export format from Purview is PST (Outlook email archive format) or individual message files — not a structured JSON format like ChatGPT's conversations.json. The content includes the conversation text, timestamps, and user attribution. This is the most complete access path for M365 Copilot conversations, but it requires admin involvement and produces compliance-format output rather than user-friendly export.
Microsoft Graph API (developer path)
The Microsoft Graph API provides programmatic access to Microsoft 365 services. As of 2025–2026, Microsoft exposed Copilot interaction history through Graph endpoints under the /me/copilot/ path. Accessing this endpoint requires:
- An Azure AD application registration with the
Copilot.Interactions.Reador equivalent delegated or application permission - The feature enabled in the tenant's Copilot admin settings
- Admin consent granted for the permission scope
A sample request to list recent Copilot interactions:
GET https://graph.microsoft.com/v1.0/me/copilot/interactions
Authorization: Bearer {access_token}
The response includes interaction records with id, createdDateTime, type, and the conversation content. The exact schema and available endpoints vary by Microsoft 365 plan tier and the admin configuration of Copilot features in the tenant. Check the Microsoft Graph documentation for the current endpoint structure, as the API surface for Copilot has expanded significantly since the product's 2023 launch.
For most individual users, the Graph API path requires creating an Azure app registration and OAuth flow — this is a developer path, not a user-facing one. For organizations that want to build their own Copilot interaction archive, the Graph API is the durable solution.
What IS and ISN'T stored
| Data element | Consumer Copilot stored? | M365 Copilot stored? | User-accessible? |
|---|---|---|---|
| Conversation text (prompts + responses) | Yes (history sidebar) | Yes (Purview) | Via in-app sidebar (consumer) / admin Purview (M365) |
| Conversation timestamps | Yes | Yes | Via privacy dashboard / Purview export |
| Uploaded images or files in conversation | Yes (text reference; original not re-downloadable) | Varies by app context | Not directly downloadable |
| Web search citations used by Copilot | Yes (inline in response) | Yes | Via in-app copy-paste; not in structured export |
| Plugin / tool call results | Partially (rendered output) | Partially (rendered in context) | Via in-app copy-paste only |
| Full conversation JSON (like ChatGPT) | No | No (PST via Purview) | Not available |
| System prompt / Copilot configuration | Not exposed to users | Varies by app and admin config | No |
What is never stored or accessible
- Copilot system prompts. Microsoft's system prompts for Copilot products are not disclosed. You cannot retrieve the instructions that shaped Copilot's behavior for any session.
- Image or file content re-download. If you uploaded an image or file into a Copilot conversation, the original file is not re-downloadable from Copilot — similar to the gap in ChatGPT's file upload handling. Keep originals elsewhere.
- M365 Copilot conversations from apps you've left. When you leave an organization, M365 Copilot conversation history from that tenant stays in the tenant and is not transferred to your personal account.
Platform comparison: export capability
| Platform | User-facing export button | Structured export format | GDPR response includes transcripts? | Admin/enterprise path |
|---|---|---|---|---|
| ChatGPT (OpenAI) | Yes (Settings → Data Controls) | Yes (conversations.json in ZIP) | Partial (data export is better) | Team: Compliance API / workspace ZIP |
| Claude (Anthropic) | Yes (Settings → Account) | Yes (conversations.json in ZIP) | Partial (data export is better) | Team: DSAR / workspace admin export |
| Gemini (Google) | Partial (Google Takeout, HTML format) | Partial (HTML, not JSON) | Partial (Takeout is better) | Workspace: Google Vault eDiscovery |
| Perplexity | No | No | Partial (partial query logs) | No enterprise export path |
| Microsoft Copilot (consumer) | No | No | Partial (metadata only, often) | N/A (personal product) |
| Microsoft 365 Copilot | No (user-facing) | No (PST via Purview) | Depends on tenant policy | Purview eDiscovery (admin-only) |
The key contrast: Microsoft Copilot is one of the worst platforms for individual user data portability (no export button, no structured file) but one of the better platforms for enterprise compliance (Purview is mature, comprehensive, and legally defensible in regulated environments). ChatGPT and Claude are the inverse: strong user-facing export tools, less mature enterprise compliance coverage. Gemini Workspace (Google Vault) and M365 Copilot (Purview) are both robust for IT-admin-level compliance work; neither provides individual users with a self-service path.
The contrapositive: why Microsoft 365 Copilot decisions matter most
Microsoft 365 Copilot is embedded in the tools where consequential business decisions are documented: Teams meeting summaries, Word document drafts, Excel data analysis sessions. A product team that uses M365 Copilot to draft a technical specification in Word, then refines it through a Teams Copilot conversation, then gets Copilot to summarize the decisions in Outlook is producing decision-bearing content across three M365 apps with no unified capture path.
The irony: M365 Copilot decisions are often better-reasoned than ChatGPT decisions (Copilot has access to the organization's M365 context — recent emails, shared documents, calendar data) but harder to capture (no export button, admin-only access for the complete record). This makes deliberate at-the-time capture more important, not less:
- For Teams Copilot meeting summaries: Copy the decision-bearing sections of the summary before the meeting record ages out. The Copilot-generated summary is the best decision record you'll have, and it's only accessible in Teams for as long as the meeting record persists.
- For Word Copilot drafts: The final document is the artifact. Save it explicitly to SharePoint or a version-controlled location. Copilot drafts that live only in Word's autosave history are fragile.
- For M365 Chat (the conversational interface): Copy-paste key exchanges into a decision log document at the end of the session. The conversation is accessible in Teams history, but Teams message retention policies vary by organization.
Decision-capture workflow for Copilot conversations
For teams where Microsoft Copilot is one of several AI tools alongside ChatGPT and Claude, the practical decision-capture strategy is asymmetric: use the automatic export path for ChatGPT and Claude (both have structured exports), and use deliberate at-the-time capture for Microsoft Copilot.
The minimum capture for any Copilot session that produced a decision or recommendation:
- The app context (Teams Copilot / Word Copilot / M365 Chat / consumer copilot.microsoft.com)
- Date and rough time
- The key question or prompt that produced the decision-bearing response
- The response or recommendation, copy-pasted in full
- Any cited sources (Copilot often cites web sources or M365 documents — capture the URLs or file names)
- Who was in the conversation (for M365 Copilot in collaborative contexts like Teams)
This capture becomes the Context section of an ADR if the decision warrants one, or a row in a decision log if it doesn't. The team member who made the call is identified; the reasoning from the Copilot session is preserved; the cited sources are recorded. Without deliberate capture, the M365 Copilot reasoning is the least recoverable of any major AI platform.
For ChatGPT and Claude sessions where the actual decision-making conversation happened (as opposed to Copilot's context-gathering role), the WhyChose extractor automates the extraction — export your ChatGPT or Claude conversation history and the extractor surfaces the decision-shaped exchanges as structured records. Copilot is often the research and summarization layer before the decision conversation; the decision itself is often finalized in a ChatGPT or Claude session where the reasoning is more explicit.
Related questions
Is Microsoft Copilot conversation history included in a GDPR data subject access request?
Partially, and with limitations. A GDPR Article 15 data subject access request submitted through Microsoft's privacy request portal (privacy.microsoft.com) can return data associated with your Microsoft account, including some Bing search and Copilot activity records. However, full Copilot conversation transcripts are often not included — Microsoft treats inference-time prompts differently from stored personal data depending on product configuration and retention settings. For consumer Copilot, the GDPR path is the most accessible recovery option after the privacy dashboard. For Microsoft 365 Copilot in enterprise organizations, the response depends heavily on your organization's Purview retention policies — data retained by the organization (accessible to your admin via Purview) may not appear in a personal GDPR response. Submit the GDPR request as a parallel track while pursuing the admin Purview path if you need M365 Copilot conversation history urgently.
Can I export Microsoft Copilot conversations to a file like ChatGPT's conversations.json?
No. As of 2026, Microsoft Copilot does not have a structured data export path equivalent to ChatGPT's conversations.json or Claude's Export Data feature. ChatGPT provides a ZIP download with complete conversation history in structured JSON format; Claude provides a similar export. Microsoft Copilot provides conversation history via the in-app history panel for consumer Copilot, and through Microsoft Purview eDiscovery for M365 Copilot (admin-only, PST format — not JSON). The Microsoft account privacy dashboard (account.microsoft.com/privacy) provides some activity data but typically shows activity metadata rather than full conversation transcripts. This is the primary data portability gap for Microsoft Copilot users.
What is the difference between consumer Microsoft Copilot and Microsoft 365 Copilot for conversation history?
Consumer Microsoft Copilot (copilot.microsoft.com) stores conversation history in your personal Microsoft account and displays it in the app's history sidebar; recovery is limited to the privacy dashboard and GDPR requests. Microsoft 365 Copilot (embedded in Teams, Word, Excel, Outlook) stores conversation data as part of your organization's M365 tenant, subject to the organization's Purview retention policies; individual users cannot self-serve their own export — it requires an IT admin with eDiscovery permissions. When you leave an organization, M365 Copilot history from that tenant stays in the tenant. GitHub Copilot is a separate product (AI code completion) with its own usage logs, not covered here.
How does a Microsoft 365 admin export Copilot conversations for compliance?
Microsoft 365 Copilot interactions are covered by Microsoft Purview eDiscovery. An M365 admin with the eDiscovery Manager or Administrator role can create a content search in the Microsoft Purview compliance center (compliance.microsoft.com) scoped to Microsoft Copilot interactions, select the relevant users and date range, and export the results in PST or message file format. For programmatic access, the Microsoft Graph API exposes Copilot interaction history under the /me/copilot/ path (requires Copilot.Interactions.Read scope, admin consent, and appropriate M365 license). Retention policies in Purview determine how long Copilot interaction history is kept — verify your organization's retention settings before assuming history is available for a specific date range.
Further reading
- How to export your ChatGPT history (2026 guide) — the export path that Microsoft Copilot doesn't have: a self-service ZIP download with complete conversation history in structured JSON format, from ChatGPT Settings → Data Controls → Export data.
- How to export your Claude conversations — the symmetric Anthropic-side export: Settings → Account → Export Data, flat conversations.json array simpler than ChatGPT's mapping DAG.
- Gemini Workspace export — Google Vault, admin console, and enterprise data portability (2026) — the closest analog to Microsoft Purview for M365 Copilot: Google Vault provides admin-initiated eDiscovery export of Gemini conversations for Google Workspace organizations. Same admin-only limitation, different tooling.
- Perplexity conversation export — how to save your AI research history (2026) — the platform with the weakest export story: no export button, no structured format, partial GDPR response. A useful contrast to the Microsoft Copilot situation.
- Perplexity Spaces export — what team workspace data is recoverable (2026) — the team workspace analog: Perplexity Spaces also has no export path, with a similar manual-capture-at-session-time requirement.
- ChatGPT Team export — differences from Plus, workspace admin flow, and the Compliance API — the OpenAI enterprise export story: Compliance API for Enterprise, workspace ZIP for Team. A better-than-Microsoft self-service path for organizations whose AI platform is primarily OpenAI.
- Claude Team workspace export — admin DSAR path, member scope, and Project isolation — the Anthropic enterprise export: workspace ZIP via DSAR with member attribution and audit log. Similar admin-mediated path to the Microsoft Purview route but available to non-Enterprise customers.
- How to extract decisions from your ChatGPT chats — for teams whose decision conversations happen in ChatGPT alongside or instead of Microsoft Copilot: the structured extraction recipe that surfaces decisions from the ChatGPT export automatically, without manual capture.
- GitHub Copilot Chat export — why there isn't one, and where your history actually lives — the IDE-embedded Copilot product this page explicitly excludes: GitHub Copilot Chat stores conversations in VS Code's local workspace storage (not in any GitHub server), has no user-facing export, and is not included in GitHub's account data archive. The local-only model is a different problem than Microsoft Copilot's server-side-but-no-export gap — and the decision-capture implications differ accordingly.
- Microsoft 365 Copilot export — Purview eDiscovery, interaction logs, and data retention — the enterprise companion to this page. This page covers the consumer Copilot at copilot.microsoft.com; the M365 Copilot page covers the enterprise AI embedded in Teams, Word, Excel, and Outlook — a different product with a different storage architecture (Exchange Online SubstrateHolds, SharePoint document history) and a different access path (admin-only via Purview eDiscovery, no self-serve user export).