How to export a Microsoft Teams chat (2026): what users can do, what admins can do, and why history goes missing

The moment you need a Teams chat outside Teams — a customer dispute, a handover, a colleague leaving, a decision someone wants in writing — you discover the thing the search results dance around: the Teams client has no Export button. Microsoft's documentation describes two export paths, both for administrators, and a handful of things an ordinary member can do. This guide lists all of them exactly as documented, checked August 2026, and then the second question people actually arrive with: why the history they wanted to export is no longer there.

What a member can do (no admin needed)

• Copy the messages. Select text in the chat and paste it into a document. It's manual, it loses formatting and attachments, and it's the only fully self-service path Microsoft documents for a member.
• Share to Outlook. A message or thread can be sent to Outlook from Teams ("Share to Outlook") — useful to get a specific exchange into email, where it can be filed or printed to PDF. It's a message-by-message action, not a chat export.
• Share history when adding someone. When you add people to an existing group chat, "you can also choose how much of the chat history to include" — and "you can include chat history only when adding someone to an existing group chat, not for a one-on-one." This doesn't export anything, but it's the documented way to hand a chat's past to a new person inside Teams.
• Download a meeting transcript. For meetings that were transcribed, organizers and co-organizers can download the transcript as a .docx or .vtt file from the meeting chat or the Recap tab. That covers what was said in a meeting, not the chat.

None of these produce a file of the chat. For that, Microsoft documents the two paths below.

What an admin can do: the two documented export paths

1. Teams Export APIs (Microsoft Graph)

"Teams Export APIs allow you to export 1:1, group chat, meeting chats, and channel messages from Microsoft Teams." The documented shape:

• They run as an application, not a signed-in user: "application permissions are used by apps that run without a signed-in user present. Only an administrator can approve application permissions" — Chat.Read.All, ChannelMessage.Read.All, User.Read.All, plus transcript and recording permissions for meetings.
• They require "an active Microsoft Teams license assigned to the users whose data is being exported"; no Purview DLP plan is needed.
• What comes out: messages with attachments metadata, reactions, control messages ("User A added User B to the chat and shared all chat history"), edit history where a retention policy is set, and links to meeting recordings (MP4) and transcripts (VTT or DOCX).
• Deleted messages "can be accessed using export APIs up to 21 days from the time of deletion"; messages from deleted teams and channels for 30 days.

In practice this is a developer or a certified archiving partner writing against Graph, with an admin approving the app. It's the path for "export everything, regularly".

2. Purview eDiscovery / Content search

The compliance path. Teams messages are journaled into Exchange Online: "all Microsoft Teams 1:1 or group chats are journaled through to the respective users' mailboxes. All standard channel messages are journaled through to the group mailbox representing the team." An eDiscovery search over those mailboxes finds them, and the export lands as a .pst you open in Outlook — "all conversations are located in the Team Chat folder under Conversation History" — or as an Excel output where Teams data "appears as IM or Conversations". Running it requires the eDiscovery Manager role in the Purview portal.

That's the path for "export this chat for legal, HR or a dispute" — by someone with the role, not by the person in the chat.

Why the history you wanted is missing

The second search behind "export teams chat" is "teams chat history missing", and Microsoft documents exactly one mechanism: retention policies. An organization can set Teams chats and channel messages to be deleted after a period; when it fires, "a system message will replace the ones deleted by an org's retention policy", "messages deleted by a retention policy can't be recovered", and the advice is "to figure out how long your org's retention policy is, reach out to your IT admin."

Two documented details explain the surprises:

• The deletion applies to the conversation, not just to your tenant's users: "the corresponding message in the Teams client app is deleted for all users in the conversation" — including people from another organization with a longer policy, who then "won't be able to see the message in Teams" even though a copy may still exist in their mailbox for eDiscovery.
• What you see isn't the record: "messages visible in the Teams app are not an accurate reflection of whether they're retained or permanently deleted for compliance requirements." A user-deleted message stays discoverable for 21 days; policy-expired messages sit in a hidden folder for at least a day before permanent deletion, and any legal hold suspends deletion.

So if the chat is gone from your screen, an eDiscovery search by an admin may still find it — for a while.

Where this leaves a team

Put together, Teams' documentation describes a space whose history belongs to the tenant: members read it, admins export it, retention decides how long it exists, and every path out — API, PST, copy-paste — hands you the messages in the language they were written in. For a single-language team inside one organization that's a coherent design. It gets awkward in two cases: a member who needs their history without an admin, and a team whose history is in three languages, where the export is only as readable as the reader's languages.

What an export looks like when the history is built to be kept

We build InterMIND around the record a space leaves behind, so the equivalent facts, stated the same way:

• Self-service export. On plans that include data export, Settings → Backup & Restore → Create Backup produces a ZIP of your chats — messages, meeting transcriptions, files, images and recordings — and Restore from Backup brings selected chats back, with pins, reactions and translations. No admin role, no API. Documentation: Backup & Restore.
• The meeting's record has a permanent link. Every meeting's recap — summary, decisions, action items, recording — lives at one address, minted when the meeting is scheduled, open to signed-in members of that meeting. Channels keep the recap of every session. (Meeting recap)
• The history reads in each member's language. Chat history, recap and documents are rendered per reader — a member who reads Polish reads last month's decision in Polish, without exporting anything. (How much of your meeting still exists a week later)
• Retention you control. Data stays until you or your team owner delete it — the criterion is written into the privacy policy — and the team audit log exports as CSV for owners and admins. Deletion and export are self-service in the product, which is also what our DPA says.

Which path for which need

See it instead of reading about it

• Try the live demo — no signup; speak, and hear the room translated per listener in any of 23 languages.
• Start your first meeting — guests join by link, each in their own language.
• Read the Backup & Restore docs — what the ZIP contains and how restore works.

FAQ

How do I export a Teams chat?

As a member: copy the messages, or share individual messages to Outlook. As an admin: run a Purview eDiscovery / Content search over the participants' mailboxes and export the result as a .pst, or use the Teams Export APIs through an admin-approved application. Microsoft's client documentation offers no Export button for a chat.

How do I export a Teams chat to PDF?

Microsoft doesn't document a PDF export. The documented routes end in a .pst (eDiscovery), JSON via Graph (Export APIs), or a message shared to Outlook — from Outlook, an email prints to PDF. Copying the chat into a document and saving it as PDF is the practical member-level route.

Why is my Teams chat history missing?

Because of a retention policy, per Microsoft: deleted messages are replaced by a system message, "can't be recovered", and the advice is to ask your IT admin how long the policy keeps messages. The deletion applies to everyone in the conversation, including people in other organizations.

Can I see chat history from before I was added to a group chat?

Only if the person who added you chose to include it: when adding people to an existing group chat, the adder chooses how much history to include; for one-on-one chats there's no such option.

Can an admin export a Teams chat between two people?

Yes — 1:1 chats are journaled into the mailboxes of both participants, so an eDiscovery search on either mailbox finds them, and the Export APIs cover "1:1, group chat, meeting chats, and channel messages".

How do I export my own chats without an admin?

In Teams, you can't beyond copy and Share to Outlook. In InterMIND, Backup & Restore on plans with data export creates a ZIP of your chats, transcriptions, files and recordings, and restores selected chats later.

Same question, but the chat is on WhatsApp?

Different tool, different limits — Export chat, what it carries, and what to do when the menu item isn't there: how to export a WhatsApp chat.

Sources: Microsoft Learn — Export content with the Microsoft Teams Export APIs, Microsoft Learn — Finding content in Microsoft Teams in eDiscovery, Microsoft Learn — Learn about retention for Teams, Microsoft Support — Teams messages about retention policies, Microsoft Support — Chat with others in Microsoft Teams, Microsoft Support — Share to Outlook from Microsoft Teams, Microsoft Support — Start, stop, and download live transcripts in Microsoft Teams meetings. Microsoft changes features and admin tooling over time; check the pages for the current state. All facts checked August 2026.