Can you sell Microsoft Teams chats to AI companies?
Only a small, cleaned slice, and only after an admin or developer has pulled it. Teams messages are not kept in one place. Microsoft says 1:1 and group chats sit in the mailboxes of the participants, channel posts in a mailbox tied to the team, and shared files in OneDrive or SharePoint. That split explains why an export is a compliance or developer task and not a button for a team owner.
What Teams holds, and where
| Channel posts and replies | Conversation in standard channels. Microsoft stores these in the Exchange Online mailbox associated with the team. |
| 1:1 and group chats | Kept in the mailbox of every participant, which is why the same chat can appear more than once in a raw pull. |
| Files shared in conversations | Channel files sit in the team's SharePoint site. Files shared in chats sit in the OneDrive of the person who shared them. |
| Meeting recordings and transcripts | Held in the organizer's OneDrive. Transcripts are separate text files from the recording. |
| Reactions and edit history | Reactions can be exported. Earlier versions of edited messages are kept when the user is on hold or a retention policy applies. |
How data leaves Teams, route by route
| Tool | What an export gives you | What is missing or needs an admin |
|---|---|---|
| Purview eDiscovery | An admin with eDiscovery permissions builds a case, searches the right mailboxes and sites, and exports. Teams chats appear as IM or Conversations, and PST files open in Outlook. | Private channels have their own mailboxes and sites, and a shared channel is searched through the parent team mailbox. Microsoft retired the classic export tool in August 2025, so current steps differ from older guides. |
| Teams Export APIs in Microsoft Graph | Programmatic export of 1:1, group, meeting and channel messages by date range, with attachment information, reactions and system messages. | An admin must approve application permissions, and the page recommends $top of 250 at most. Messages deleted by users are available for 21 days, deleted teams, channels and users for 30. |
| Retained messages API | Where a retention policy or hold exists, deleted messages beyond 21 days and earlier edited versions can still be exported. | It depends on your tenant having that policy in place before the messages were deleted. |
Tool names belong to their owners and are used only to say where records usually live. Export features change by plan and version, so check the current rules for your account.
Who can run it
The Graph export route needs an app with Chat.Read.All and ChannelMessage.Read.All permissions, and Microsoft says only an administrator can approve application permissions. Microsoft also requires an active Teams license on the users whose data is exported.
Purview eDiscovery needs a user with eDiscovery permissions. Microsoft's page on the older export flow named the eDiscovery Manager role group for the export role; check with your Microsoft 365 admin which roles apply in the current portal.
The retention policy question
Chats can be removed by users, by retention policies or by a time limit on the policy. The first thing to learn is whether your tenant deletes Teams messages after a set period. If it does, older history may simply not be there.
Ask your admin to check whether a hold or a retention policy applies to Teams chat and channel messages before anyone counts messages.
Counting and de-duplicating
Because a group chat is stored for every participant, count conversations rather than copies. Microsoft's own eDiscovery pages describe grouping messages into transcripts by conversation and handling duplicate copies; a developer using the Graph API has to do that work in code.
Count channel posts by team and channel, not just overall. A few busy channels with a clear purpose make a stronger description than a total across every team.
Cleaning
Teams text includes display names, @mentions, email addresses, meeting links and file links. Each must map to a stable code. Guests, external users and customers who joined a chat did not agree to anything on your side; leave their content out.
What stays out of a Teams set
| 1:1 chats | Left out of a first set, because they are private conversations between two people. |
| Guest and external participants' messages | Not yours to license. |
| Meeting recordings and transcripts | Voices and names, so they need consent handling and stay out of a text set. |
| Links, tokens and attachments with personal data | Removed from the text, or the message goes out. |
More on this: how personal details are removed, who carries the risk and how you get paid.
An example, invented for illustration
A regional engineering firm uses Teams channels for each project. The Microsoft 365 admin confirms that no retention policy deletes channel posts, and a developer exports posts from four project teams by date range through the Graph API. The firm replaces display names and mentions, removes anything with a client address, leaves out every chat and recording, and reads a sample before a count is written down.
Questions owners ask about this
Where are Teams messages actually stored?
Microsoft says 1:1 and group chats are in the mailboxes of the participants, standard channel posts in the mailbox associated with the team, and channel files in the team's SharePoint site.
Can a team owner export a channel?
Not through anything we found. The routes are Purview eDiscovery for admins with the right permissions, or the Graph export APIs for a developer with admin-approved permissions.
How long can I recover a deleted Teams message?
Microsoft says messages a user deleted are available through the export API for 21 days, and deleted teams and channels for 30. A hold or retention policy can extend that.
Do the export APIs cost extra?
Microsoft's export page says an active Teams license is needed and no Purview DLP license is required. A separate Microsoft licensing page says the Teams APIs stopped being metered in August 2025, but older pages still show payment models, so confirm.
Didn't find your question? Ask us directly.
Sources
The vendor's own pages this guide draws on. Some help centers did not open for us, and where a step rests on a summary and not the page itself, the guide says so. Menus and limits change by plan and version, so check the current pages for your account.
Keep reading
Related kinds of records
- Team chat: Slack and Teams threads, where one person must stay one person and direct messages stay out.
- Outlook and Microsoft 365 email export: How company email and Teams chat leave Microsoft 365, and what retention and privacy settle first.
- Slack data export: Channels, threads and the settings that decide how much of your chat history can leave.
- SharePoint and OneDrive export: Version limits, eDiscovery export and Graph version lists for SharePoint libraries and OneDrive, and what a download misses.