Quick Answer

When your compliance office asks which container holds a regulated file and the answer turns on who happened to create the channel, the platform question is already settled: as of Microsoft Learn documentation updated June 25, 2026, December 3, 2024, and February 9, 2025, “The files you see on the Files tab in a team are stored in a SharePoint site.” (Microsoft Learn, teams-connected sites, updated June 25, 2026). So the decision in front of you is not Teams or SharePoint; it is which container regulated content lands in, and who is accountable for it. Content that will carry a retention label, needs external-party access, or is a records source belongs in a standalone governed SharePoint site with a named site owner, regardless of where the conversation started. Everything else can stay where the conversation happens, in the channel and on whichever site that channel type connects to, under the owner that channel type actually gives you. The container you choose is the governance decision; the platform underneath it is the same either way.

Which Teams file belongs where: understanding containers and their owners

If nobody can say where a given file actually sits, start with what Teams created on your behalf when the team was set up. A Teams-connected site is created automatically whenever you create a team (Microsoft Learn, teams-connected sites, updated June 25, 2026). All standard channels in a team share the same SharePoint site, but each private channel has its own site. Each shared channel has its own SharePoint site for file storage. In Teams, the Files tab on each standard channel is connected to a folder in the parent site’s default document library. The Files tab on each private and shared channel is connected to the default document library in the corresponding channel site.

The placement rule: which content belongs where, and who owns it

When a file has to be placed and the team is already running, the rule below turns the container question into a records question. Work each kind of content through it before the first file goes in.

  • A records source, or content that will carry a retention label. Container: a standalone governed SharePoint site, provisioned for the records duty rather than inherited from a conversation. Owner: a named site owner who stays accountable after the team that started the conversation is archived. Retention duty: the compliance office determines which retention applies and records that determination against the site before content lands in it.
  • Content a partner or subcontractor must reach. Container: a shared channel and the SharePoint site that comes with it (Microsoft Learn, teams-connected sites, updated June 25, 2026). Owner: somebody who is a member of that channel, because “Team owners can’t see the files in a shared channel or the conversations and member list of a shared channel unless they’re members of that shared channel.” (Microsoft Learn, shared channels, updated February 9, 2025). Retention duty: the policy applied to the team, which the shared channel inherits (Microsoft Learn, shared channels, updated February 9, 2025), so content whose records duty differs from the team’s does not belong there.
  • Content only some of the team may see. Container: a private channel and its own SharePoint site (Microsoft Learn, teams-connected sites, updated June 25, 2026). Owner: “The person who creates a private channel is the private channel owner and only the private channel owner can directly add or remove people from it.” (Microsoft Learn, private channels, updated December 3, 2024), so the accountable name is that person and not the team owner. Retention duty: a retention policy can be applied to the private channel site (Microsoft Learn, private channels, updated December 3, 2024), and the compliance office decides which one.
  • Everyday working content with no records consequence. Container: a standard channel, whose files sit in a folder in the team’s parent site (Microsoft Learn, teams-connected sites, updated June 25, 2026). Owner: the team owner. Retention duty: the team’s policy, revisited when the team’s purpose changes.

Where two of these disagree, and the content is both a records source and something a partner needs, the records duty wins: the container is the standalone governed site, and external access is granted from that site rather than by moving the content into a channel.

What Teams controls that a SharePoint administrator cannot

If you are expecting a SharePoint administrator to fix a permissions problem inside a channel, check which kind of channel it is first. Site permissions for a private channel site can’t be managed independently through SharePoint (Microsoft Learn, private channels, updated December 3, 2024). Teams manages the lifecycle of the private channel site. A private channel owner or team owner (whether or not they’re a member of the private channel) can delete the private channel.

Site permissions for a shared channel site can’t be managed independently through SharePoint (Microsoft Learn, shared channels, updated February 9, 2025). A shared channel site inherits the sensitivity label of the parent team. A file that is encrypted by a sensitivity label can’t be opened by external participants unless permissions are granted. While guests (people with Microsoft Entra guest accounts in your organization) can’t be added to a shared channel, you can invite people outside your organization to participate in a shared channel by using Microsoft Entra B2B direct connect.

Who owns each container: team owner, channel owner, site owner

If nobody can name the owner of a container, the placement rule has nothing to attach to. The membership for each team is stored in a Microsoft 365 group and that group also gives those people access to the team’s parent SharePoint site (Microsoft Learn, teams-connected sites, updated June 25, 2026). Team owners and members are automatically included in the site owners and members permission groups. Review and archival cadence for a named owner is set out on the SharePoint Site Ownership and Lifecycle Governance page, which owns that decision.

Regulated content in channels: where retention and records duties apply

When a file’s records duty outlives the conversation that produced it, the retention question moves ahead of the platform question. Retention policies can also be used for private channel sites (Microsoft Learn, private channels, updated December 3, 2024). Admins can apply a retention policy on a team where all channels, including shared channels, inherit the retention policy (Microsoft Learn, shared channels, updated February 9, 2025). The compliance office owns the determination of which retention applies to which content, and the IT director owns naming the container before the first file goes in. For guidance on FINRA books-and-records and other regulatory duties, see the Embedding Governance into How the Enterprise Operates and Scales page.

Where Teams chats and channel files sit when legal needs to search or hold them

Before the first matter, name two kinds of location for a team, not one: channel files sit in SharePoint, in the team’s site or the channel’s own site, and channel messages sit in Exchange Online mailboxes, so a search or hold scoped to the site alone misses the conversation (Microsoft Learn, Finding content in Microsoft Teams in eDiscovery, updated April 2, 2026).

Standard channels. Microsoft states that “All channel messages and posts are stored in the Exchange Online mailbox associated with the team.” and that “Files shared in a channel are stored in the SharePoint site associated with the team.” (same source). A hold on that site alone keeps the files and leaves the posts out.

Private channels. “Files shared in a private channel are stored in a dedicated SharePoint site associated with the private channel.” For the messages, Microsoft states: “You need to search private channel mailboxes when searching for content in private channel messages.” (same source).

Shared channels. “Files shared in a shared channel are stored in a dedicated SharePoint site associated with the shared channel.” For the messages, the search runs back to the parent team: “Because Teams doesn’t support an eDiscovery search of a single system mailbox for a shared channel, you need to search the mailbox for the parent team (by selecting the name of the Team mailbox) when searching for message content in shared channels.” (same source).

Chats outside any channel. “Messages in 1:1 chats are stored in the Exchange Online mailbox of all chat participants.” and “Files shared in a 1:1 chat are stored in the OneDrive account of the person who shared the file.” (same source). Neither sits in a team’s site, so a matter that turns on chats is scoped to people’s mailboxes and OneDrive accounts rather than to a team.

The IT director names these locations for each team and channel before the first matter; the legal or compliance office owns the decision to search or hold them.

Does the answer change in GCC High?

The container rule does not change: GCC High subscriptions “include the core Exchange Online, SharePoint, and Skype for Business features” (Microsoft Learn, Office 365 GCC High and DoD, updated August 3, 2026). What changes is which channel types and cross-cloud access paths you can use, so check those against Microsoft’s GCC High documentation before you provision.

Shared channels. Microsoft’s Teams service description (updated July 8, 2026) lists standard and private channels as available in GCC High and shared channels as not available. Microsoft’s developer guidance for channel apps describes shared channels in GCC High and states: “SharePoint and the SharePoint pages apps aren’t supported for shared channels in GCC, GCC High, DoD, and Teams operated by 21Vianet environments.” (Microsoft Learn, Agents and tab apps for shared and private channels, updated September 17, 2026). The two pages differ on whether shared channels are offered in GCC High at all, so confirm in your own tenant before a partner’s content is planned for one; on either reading, SharePoint apps are not a shared-channel option there.

External access from another Microsoft cloud. Microsoft states: “B2B direct connect is not supported for collaboration with Microsoft Entra tenants in a different Microsoft cloud.” (Microsoft Learn, Enable B2B collaboration across Microsoft clouds, updated July 27, 2026). B2B direct connect is how people outside your organization join a shared channel, so a partner whose tenant is in a different Microsoft cloud cannot be connected to a channel that way. Guest access through B2B collaboration is a separate path: the same page lists B2B collaboration as available between the Microsoft Azure commercial cloud and Microsoft Azure Government, and states that “Both organizations must enable collaboration with each other”.

Whether a given contract or data set needs GCC High is your compliance office’s determination. We manage GCC High migrations end-to-end: from eligibility validation and licensing coordination with your AOS-G supplier through identity architecture, data migration, security baseline configuration, and post-migration governance. i3solutions plans and runs these migrations for regulated defense organizations, structuring each phase around the compliance evidence assessors expect.

Honest counter-case: when Teams is the right answer

If your organization runs everything in Teams and nothing has gone wrong, the Teams channel model is working for your content and your retention rules. A small team whose content never carries a retention label, needs external access, or represents a records source can live safely in a Teams channel and its channel site. A dedicated records site is still needed if your organization runs a records management program that requires archiving by department or legal matter rather than by conversation.

What a first conversation produces

An i3solutions SharePoint consulting engagement produces named deliverables: a governance documentation package, architecture artifacts, and runbooks. i3solutions has delivered enterprise SharePoint and Power Platform programs for aerospace and defense manufacturers, major defense organizations, a financial-services firm, a national healthcare system, and military organizations.

Governance Framework Links

If the container rule is going to hold once people start creating workspaces, it has to sit inside a governance model somebody already owns. The following pages establish that framework:

Frequently Asked Questions

Microsoft Teams vs SharePoint: which is right for our collaboration needs?

Both, because Teams keeps its files in SharePoint: “The files you see on the Files tab in a team are stored in a SharePoint site.” (Microsoft Learn, teams-connected sites, updated June 25, 2026). For a regulated enterprise the real choice is the container each kind of content goes into and the person accountable for it: records sources and labeled content belong in a governed SharePoint site that has a named owner, and working content stays in the channel.

Where are Teams files actually stored?

In SharePoint. Files posted in a standard channel go to a folder in the parent team’s site, and private and shared channels each get a separate SharePoint site of their own (Microsoft Learn, teams-connected sites, updated June 25, 2026). Files shared in a one-to-one or group chat are the exception: Microsoft stores them in the OneDrive account of the person who shared the file.

Can guests be added to a Teams shared channel?

No. Guest accounts can’t be added to a shared channel. Microsoft brings people from outside your organization in through Microsoft Entra B2B direct connect instead, and guest access in Teams must still be turned on before they can be invited (Microsoft Learn, shared channels, updated February 20, 2026).

Where does eDiscovery search Teams content?

In two kinds of location: Exchange Online mailboxes for chat and channel messages, and SharePoint sites or OneDrive accounts for files (Microsoft Learn, Finding content in Microsoft Teams in eDiscovery, updated April 2, 2026). Shared channel messages are searched through the parent team’s mailbox, and private channel messages through the private channel mailboxes.

Are Teams and SharePoint available in GCC High?

Yes. Microsoft’s GCC High and DoD service description states that subscriptions include the core Exchange Online and SharePoint features, and its Teams service description lists Teams, standard channels and private channels as available in GCC High (updated August 3, 2026 and July 8, 2026). On shared channels Microsoft’s pages differ: the same Teams table (updated July 8, 2026) lists shared channels as not available there, while Microsoft’s guidance on agents and tab apps for shared and private channels (updated September 17, 2026) lists tab apps in shared channels as available in GCC High, so confirm in your own tenant. Microsoft also states that B2B direct connect is not supported with tenants in a different Microsoft cloud.

Key Takeaways

If you are deciding which container holds regulated content, the placement rule depends on three criteria: retention, external access, and records consequences. For each kind of content, name the container, the owner, and the retention period before the first file goes in. Every Teams file already lives in a SharePoint site (Microsoft Learn, teams-connected sites, updated June 25, 2026), so the choice is the site’s governance model and its named owner.

If you are deciding between Microsoft Teams and SharePoint for regulated content, the decision is which container regulated content lands in, and who is accountable for it, not which platform.