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.

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:

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.