Logistics and distribution
Microsoft Teams chats vs channels: what can be licensed?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
In Microsoft Teams, channel messages are usually the strongest licensing candidates because they record shared work in a team setting; group chats need case-by-case review, and one-to-one chats are generally excluded. The working rule: license conversations that read like team records, not private correspondence, and only after notice, rights and privacy review with counsel.
Key takeaways
- Standard channels record team work in a shared space and are the usual starting point for any Teams licensing scope.
- Group chats qualify only when they are named, work-focused and tied to a process such as order exceptions or returns.
- One-to-one chats carry the highest expectation of privacy and are generally left out of licensed datasets.
- Messages from guests, customers and vendors in shared spaces raise third-party rights questions of their own.
- Employee notices, acceptable use policies and counsel review set the final scope, deal by deal.
Why does the chat vs channel difference matter for licensing?#
The chat vs channel difference matters because each Teams conversation type carries a different expectation about who will read it, and that expectation drives both privacy risk and buyer value. A post in the order desk channel is written for the whole team. A one-to-one chat between a branch manager and an inside sales rep is written for one person.
At many distributors, Teams replaced email for daily coordination. Channels such as Order Desk, Will-Call, Vendor Escalations and Returns hold years of threads where someone asks about a short shipment, a buyer confirms a substitute part and a manager approves a credit. Those threads show how the work actually gets done, which is what AI teams building workflow agents look for.
The same tenant also holds chats about sick days, performance problems and weekend plans. Sorting the first kind from the second is the core of any Teams scope.
Channels, group chats and 1:1 chats compared#
Channels, group chats and one-to-one chats sit on a spectrum from team record to private correspondence. The table below shows the typical approach for each; the final call is made with counsel after the rights review.
The split also matches how Microsoft stores and governs the data. Microsoft says Teams chat messages sit in a hidden folder in the mailbox of each user in the chat, while channel messages use a similar hidden folder in a group mailbox, and both are reached through eDiscovery rather than opened directly. Microsoft Purview also treats channel messages and chats as separate retention policy locations, so IT can confirm which history still exists for each type before counsel scopes anything.
| Conversation type | What it usually holds | Expectation of privacy | Typical approach |
|---|---|---|---|
| Channels (standard) | Threads on orders, returns, vendor issues and branch operations, visible to the whole team | Lower: written for a team audience | Usual starting point, after notice review and removal of personal and confidential details |
| Group chats | A mix of process coordination and side conversation among a few people | Mixed: depends on the chat's purpose | Include by allowlist only, for named chats used as working rooms for a process |
| One-to-one chats | Direct exchanges between two people, often personal, HR or manager topics | Highest: written for one reader | Generally excluded; any exception needs counsel sign-off |
What makes a channel thread licensable?#
A channel thread is a good licensing candidate when it documents a business process from request to outcome and contains little personal material. Membership alone is not enough: a channel open to the whole company can still be full of off-topic posts.
Private and shared channels need their own review. Private channels are often created precisely because the topic is sensitive, such as a pricing committee or an HR investigation. Shared channels include people from other organizations, whose messages your company may not have the right to license.
- The channel has a clear business purpose, such as order exceptions, returns or carrier issues.
- Threads reference record numbers from other systems: sales orders, RMAs, purchase orders or tracking numbers.
- Replies show a decision and an outcome, not just a question.
- Few posts discuss health, discipline, compensation or other personal matters.
- No external guests post in the channel, or their messages can be removed cleanly.
- History is still retained under your Microsoft 365 retention settings and can be exported.
When can group chats be included?#
Group chats can be included when they function like a small channel: a named chat with a stable membership and a single working purpose. A chat called Branch 4 Will-Call, used every day to coordinate counter pickups, behaves like a team record.
Ad hoc group chats are different. They start around one problem and drift into lunch orders, family news and complaints about a manager. Reviewing them line by line costs more than the records are worth, so the usual approach is an allowlist of specific chats rather than a blanket inclusion.
Before any group chat is added, someone who knows the work should read a sample and confirm that the chat stays on topic across its history, not only in recent months.
Why are one-to-one chats usually left out?#
One-to-one chats are usually left out because they are where employees raise personal matters, and the records add little that channels and business systems do not already show. An inside sales rep may tell a manager about a medical appointment, a pay question or a conflict with a coworker in the same chat where they confirm a price.
The decisions that matter in direct chats tend to surface elsewhere. A price approval given in a one-to-one chat usually shows up as an override in the ERP or a note on the sales order. Licensing the ERP record with its reason captures the decision without exposing the private exchange.
What do employees, guests and counsel need to see first?#
Employee notices, guest access and privileged conversations need review before any Teams scope is fixed. These checks decide what the company can license, separate from what would be useful.
Laws that may apply include state employee monitoring and privacy laws and, for staff outside the US, laws such as GDPR. Which ones apply is assessed deal by deal with counsel.
| Check | What to look for | Usual owner |
|---|---|---|
| Employee policies | Acceptable use and handbook language on company systems and business records | HR and counsel |
| Notices | Monitoring and privacy notices, including any state notice and acknowledgment duties | Counsel |
| External participants | Guests, shared channels and chats with customers or vendors | IT and counsel |
| Privileged material | Channels or chats with in-house or outside lawyers | Counsel |
| Sensitive topics | HR investigations, medical leave, union matters, compensation | HR and counsel |
| Retention and holds | Retention policies, deleted history and active legal holds | IT and counsel |
Illustrative: scoping Teams at a three-branch distributor#
Illustrative: a fictional industrial distributor with three branches has used Teams for several years. It has channels for each branch, an Order Desk channel, a Vendor Escalations channel and a Returns channel, plus hundreds of group chats and one-to-one chats. A shared channel with its largest supplier includes the supplier's staff.
Counsel reviews the employee handbook, which describes Teams as a company system for business use, and the monitoring notice given at hiring. The team scopes in the Order Desk, Vendor Escalations and Returns channels, plus two named group chats used by the will-call counters. The shared supplier channel, all private channels and all one-to-one chats are excluded.
During preparation, employee and customer names are replaced with consistent placeholders, and threads that mention medical leave or discipline are removed. The result is a smaller scope than the full tenant, but one the company can explain to employees and defend to its counsel.
How SourceX handles Teams scope#
SourceX treats each Teams conversation type as a separate scoping decision within the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The fit check starts with metadata only, such as which channels exist, their purpose and how far history goes back; no messages are shared at that stage.
The Rights step reviews notices, policies and external participants. The SourceX Evidence Packet then records which channels and chats were included, what was removed during preparation and who authorized the release. The company approves every step, and the records are licensed, not sold, so ownership stays with the company.
Frequently asked questions
Does the company own the messages employees send in Teams?
A company generally controls business records created on its systems, but control is not the same as permission to license. Employee notices, state privacy and monitoring laws, contracts with customers and vendors, and where employees work all shape what can be used. Counsel reviews those factors before any Teams messages are scoped in.
Can we license channel messages that mention customers by name?
Customer names, contacts, account numbers and pricing are usually removed or replaced during preparation. Customer contracts may also restrict how confidential information is used, so the rights review checks those terms. Threads that only make sense with a customer's confidential details are often dropped rather than edited.
Are files and meeting recordings in Teams part of the same scope?
No. Microsoft says files shared in Teams chats are stored in the sharer's OneDrive, while files uploaded to channels are stored in the team's SharePoint site, so they follow OneDrive or SharePoint retention rather than Teams message retention. Meeting recordings and transcripts carry voice and likeness questions. Each is scoped as its own record type with its own review, rather than following the decision made for messages.
Can messages from former employees be included?
Messages from former employees in an approved channel are usually treated like any other channel message, subject to the notices and policies in effect when they were written. Check first that the history survived: Microsoft says a deleted mailbox covered by an active Teams retention policy becomes an inactive mailbox that keeps the Teams data, but without such a policy departed staff's chats may be gone. Counsel may treat departed staff differently in some jurisdictions, and their names are replaced during preparation like everyone else's.
Do we need employee consent, or is notice enough?
The answer depends on where employees work, what your policies and notices already say, and which laws may apply. Some companies update notices before licensing employee-created records even when not strictly required. Counsel decides the approach deal by deal.
Sources
- Teams chats are stored in hidden folders in each user's mailbox and channel messages in a group mailbox; Purview treats chats and channel messages as separate retention locations; chat files sit in OneDrive and channel files in SharePoint; a deleted mailbox under an active Teams retention policy becomes an inactive mailbox. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.