Can our Microsoft Teams history be licensed to AI companies, and how do we get it out?

Updated October 25, 2026 · How we research

What is in Teams, and why do buyers value it?

Teams holds channel conversations, one-to-one and group chats, meeting chats, and links to meeting recordings and transcripts. Files shared in Teams are stored in SharePoint and OneDrive behind the scenes.

AI companies look for this kind of record because it captures real work: people asking for help, sorting out problems, and agreeing on next steps. Channel threads tied to projects or support work are usually more useful than casual chat.

How do you export Teams content?

As of October 2026, Microsoft documents two main paths:

• Microsoft Purview eDiscovery: a compliance user runs a search across Teams and other locations, then exports the results. Microsoft says Teams exports include messages posted in a 12-hour window around each matching item, and export packages are deleted 14 days after they are created.
• Teams Export APIs (part of Microsoft Graph): an app reads chat and channel messages in bulk. Microsoft says these require an active Teams license for the users whose data is exported, and application permissions that only an administrator can approve.

Who has to do it?

For Purview, Microsoft says the person exporting needs the Export and Preview roles, which come with the eDiscovery Manager role group. Assigning those roles requires Organization Management membership or the Role Management role. Microsoft also says the eDiscovery user needs a Microsoft 365 E3 or E5 license.

For the Export APIs, an administrator must approve the app's permissions, such as permission to read all chats or all channel messages. In practice, this means your IT administrator or managed services provider will be involved.

Do you need to export at all?

Some buyer programs read Teams through an app registered in your Microsoft tenant rather than receiving export files. Look closely at the permissions it requests: reading all chats, which includes private one-to-one messages, is much broader than reading selected channel messages. Approve only what the license covers, and remove the app's consent when the work ends.

What should stay out?

Teams mixes work threads with very personal conversations. Common exclusions:

• One-to-one and group chats, which work like direct messages.
• HR, legal, finance, and leadership teams and channels.
• Meeting recordings and transcripts, which capture voices and may need consent from attendees.
• Shared and external channels with other companies.
• Customer personal data, health or financial details, and anything covered by an NDA (nondisclosure agreement).

What rights questions come up?

Microsoft's terms generally let a customer access and export its own tenant data. That does not settle whether you may license it. Employee privacy laws, customer contracts, and recording consent rules can all limit reuse. Check our guides on who owns the data and on employee and customer privacy, and get legal advice before you sign.

Where should you start with Teams data?

Separate channel conversations from private chats at the outset, since most companies license only selected channels. Confirm who in IT holds the eDiscovery roles, and check whether meeting recordings or transcripts exist, because those raise consent questions. Remember that files shared in Teams live in SharePoint and OneDrive; see Can our SharePoint or Google Drive files be licensed to AI companies, and how do we get them out?.

General information, not legal, tax or financial advice.