What is the difference between Teams, SharePoint, and Microsoft Lists?

They are three layers of one collaboration stack. Microsoft Teams is the front door — a collaboration tool where you chat, meet, and organize work into channels. SharePoint is the backend that stores files and publishes content; every Teams team is automatically connected to a SharePoint site, and the files you see on a channel's Files tab actually live in that SharePoint site. Microsoft Lists is a lightweight, structured way to store and track data (a collection of items with typed columns) that lives on a SharePoint site and can be surfaced as a tab inside a Teams channel. In short: Teams is where you talk, SharePoint is where files live, and Lists is a simple database for tracking things — and all three are wired together.

Where do files shared in a Teams channel actually get stored?

In SharePoint. When you create a team, a SharePoint site is created and connected to it automatically. The files you see on the Files tab in a team are stored in a SharePoint site — all standard channels in a team share the same SharePoint site, with a separate folder for each channel. Private channels and shared channels are different: each private channel and each shared channel gets its own separate SharePoint site, and only members of that channel can access it. So a Teams channel's Files tab is really a view into a SharePoint document library behind the scenes.

How do I build a supply or status tracker in Microsoft Lists?

Create a list, then define the columns you need. A list is a collection of data you can share with your team, and it supports typed columns — including Text, Number, Choice, Currency, Date and Time, Lookup, Yes/No, and Calculated — so you can model fields like NSN, nomenclature, quantity on hand, status (a Choice column), and a required-by date. You can create the list in SharePoint, in the Microsoft 365 Lists app, or directly in Microsoft Teams, and you can attach one or more files to a list item for supporting detail. Add the list as a tab in your logistics channel so the whole shop works the same tracker.

Can I share a Teams channel or list with someone at another command in the gov cloud?

It depends on the environment and how sharing is configured, and gov-cloud tenants (GCC, GCC High, and DoD) are more restricted than commercial. Guest access — adding an external person to a team as a Microsoft Entra B2B guest — is available between Microsoft 365 cloud environments (such as commercial and GCC) using cross-cloud guest access, when your admin allows it. But several external-collaboration features are explicitly restricted in gov cloud: for example, apps in external chats aren't supported in GCC, GCC High, and DoD environments. Whether and how you can collaborate across commands depends on your tenant's policies — confirm the current rules with your IT/security office before relying on external sharing for mission data.

Can I store CUI in Teams, SharePoint, or Lists?

Only within an environment that is authorized to hold that information, and only following your organization's data-handling and CUI marking rules — this guide does not authorize any specific data at any specific impact level. The DoD Microsoft 365 environment's authorization is governed by the DoD Cloud Computing Security Requirements Guide (SRG), and what you may store depends on your tenant's accreditation and your command's policy. Never place controlled or classified information into a workspace unless you have confirmed the environment is accredited for it and you are applying the required markings and access controls. When in doubt, ask your information owner, records manager, or security office.

How is a private channel different from a standard channel for permissions?

A standard channel is visible to all members of the team, and all standard channels share the team's single (parent) SharePoint site with a folder per channel. A private channel is restricted to only some of the team's members and has its own separate SharePoint site — only members of the private channel can access that site, and its permissions are inherited from the channel itself and shown read-only in SharePoint. Use standard channels for the whole shop's work and a private channel when a subset (for example, a small planning cell) needs a walled-off space with its own file storage.

Do I need to be a SharePoint expert to run a logistics workspace?

No. The point of the stack is that Teams and Lists put a friendly front end on SharePoint. You create a team, add channels for the way your shop is organized, drop files on the Files tab (which SharePoint stores for you), and stand up a Microsoft List for anything you need to track — all without writing code or hand-building a SharePoint site. Manage membership and most day-to-day settings from Teams; Microsoft's guidance is that managing access through Teams is the easiest approach and gives the best experience. Reach for a SharePoint admin only for tenant-level settings your shop can't change itself.

What is Flank Speed and how does this stack relate to it?

Flank Speed is the Department of the Navy's Microsoft 365 cloud collaboration environment — the Navy's tenant of the DoD Microsoft 365 cloud, providing email, Teams, OneDrive, Office apps, and SharePoint. Teams, SharePoint, and Lists are the collaboration products you use inside Flank Speed (and inside the equivalent tenants other DoD components run). This guide covers how those products work and how to build a logistics workspace with them; for the environment itself — access, Nautilus virtual desktop, and onboarding — see the Flank Speed tool page and the environment guides linked below.

Guide

Teams, SharePoint & Lists for Logistics — building a shop workspace in the DoD M365 cloud

Microsoft Teams, SharePoint, and Microsoft Lists are the everyday collaboration stack inside the Department of the Navy's Flank Speed environment and the wider DoD Microsoft 365 cloud. Teams is the front door for chat, meetings, and channels; SharePoint is the backend that actually stores the files behind every Teams channel; and Microsoft Lists is a lightweight, no-code database — ideal for a supply, status, or parts tracker — that a logistics shop can stand up without a developer. This guide, framed for a working federal or military logistician, shows how the three fit together and how to build a shared logistics workspace on top of them, with the gov-cloud sharing and CUI caveats called out.

Operator: Microsoft 365 (the DoD/Navy tenant is operated as Flank Speed under the Department of the Navy / PEO Digital); products documented per Microsoft
Regulatory authority: DoD Cloud Computing Security Requirements Guide (SRG) for the hosting environment; DoD/Navy data-handling and CUI policy; Microsoft 365 US Government service descriptions for product behavior
Access type: account_required
Last verified: 2026-07-04

Microsoft Teams, SharePoint, and Microsoft Lists are the everyday collaboration stack inside the Department of the Navy's Flank Speed environment and the wider DoD Microsoft 365 cloud. For a working logistician they answer three different needs with one connected toolset: Teams is the front door — where a shop chats, meets, and organizes work into channels; SharePoint is the backend that actually stores the files behind every Teams channel and publishes shared content; and Microsoft Lists is a lightweight, no-code database — the right tool for a supply, status, or parts tracker that a shop can stand up without a developer. The three are wired together on purpose: create a team and you automatically get a SharePoint site behind it, and a Microsoft List can live on that site and appear as a tab in a Teams channel. This page is a logistician-framed reference for how the stack fits together and how to build a shared logistics workspace on top of it — with the gov-cloud sharing limits and CUI cautions called out, because they behave differently in the DoD environment than in the commercial cloud.

At a glance

Teams = the front door. A collaboration tool where you chat, meet, and organize work into channels. Each team is connected to one or more SharePoint sites where the team's files are stored.
SharePoint = the backend. A tool for creating sites, publishing content, and storing files. A SharePoint site is created automatically whenever you create a team, and the files on a channel's Files tab are stored there.
Lists = a lightweight database. "A list is a collection of data that you can share with your team members." It supports typed columns and can be created in SharePoint, the Lists app, or Teams — ideal for a tracker.
Standard vs. private vs. shared channels store files differently. All standard channels share the team's single (parent) SharePoint site; each private and each shared channel gets its own separate site accessible only to that channel's members.
Gov cloud is more restricted for external collaboration. Guest access works across Microsoft 365 clouds via cross-cloud guest access, but features like apps in external chats aren't supported in GCC, GCC High, and DoD.
The environment is Flank Speed. For the Navy, this stack lives inside the DoD Microsoft 365 tenant known as Flank Speed. Access, virtual desktop, and onboarding are covered on the tool page and environment guides.
CUI is a policy question, not a feature you toggle. Whether you may store controlled information depends on your tenant's accreditation (governed by the DoD Cloud Computing SRG) and your command's data-handling policy. Confirm before you store.

The collaboration stack: three layers, one system

It helps to stop thinking of Teams, SharePoint, and Lists as three separate apps and start thinking of them as three layers of one system. Microsoft's own documentation describes exactly how they relate.

Teams is where people collaborate. It is "a collaboration tool where you can chat with other people about a particular subject or task," and "each team is connected to other tools that you can use to collaborate with others." A channel is "a location in a team where you can collaborate with others on a specific thing," and a team can have many channels for different purposes.
SharePoint is where content lives. It is "a tool for creating web sites, publishing content, and storing files." A SharePoint site is a web site "where you can create web pages and store and collaborate on files" — and critically, "a Teams-connected site is created automatically whenever you create a team." You rarely have to build one by hand; making a team makes the site.
Lists is a lightweight database. A Microsoft List is "a collection of data that you can share with your team members and people who you've provided access to" — a set of items with typed columns, well suited to tracking. Lists can be created "in SharePoint, the Lists app in Microsoft 365, or Microsoft Teams," and a list ultimately lives on a SharePoint site.

The connective tissue is what makes the stack powerful. The files you see on the Files tab in a team are stored in a SharePoint site — Teams is a friendly front end over SharePoint storage. And because a list lives on a SharePoint site, you can surface the same list as a tab inside a Teams channel so the whole shop is looking at one tracker. You get a chat-first interface (Teams), durable file storage and content management (SharePoint), and structured tracking (Lists) without stitching three products together yourself.

A logistics workspace pattern

Here is a concrete pattern a supply or logistics shop can stand up in the DoD M365 environment. It uses nothing but the built-in stack.

Create a team for the shop. When you create a new team from scratch, "a new SharePoint site is created and connected to the team." That parent site is your shop's shared file storage, and every member of the team gets access to it.
Add channels that match how the shop is organized. A team starts with a standard channel called General that always appears first and can't be deleted (every team must have at least one channel). Add more standard channels for the way you actually work — for example, one per function (Receiving, Issue, Turn-in) or per effort. In SharePoint, "the standard channels display as folders in the parent site," so your channel structure and your file structure line up.
Use the Files tab as your document library. Drop your working files — receipts, turn-in documents, correspondence, working spreadsheets — on a channel's Files tab. Behind the scenes, "the Files tab on each standard channel is connected to a folder in the parent site's default document library," so you are really building an organized SharePoint document library just by using Teams.
Stand up a Microsoft List as your tracker. Add a list (see the next section) for whatever your shop needs to track continuously — open requisitions, parts status, equipment on hand — and pin it as a tab in the relevant channel so everyone works the same data.
Wall off a subset with a private channel when you need to. If a small cell needs a space others can't see (for example, a planning group), create a private channel: it has its own separate SharePoint site and "only members of the private channel can access this site." Use it deliberately — a private channel's storage and permissions are genuinely separate from the rest of the team.

The result is a single workspace where the conversation (Teams), the documents (SharePoint), and the running data (Lists) live together and stay in sync — instead of a chat thread, a shared drive, and an emailed spreadsheet that drift apart.

Lists as a tracker

For most logistics tracking, a Microsoft List is the right tool — lighter than a database, more disciplined than a spreadsheet, and shareable to the whole shop.

Start by creating a list. You can create one "in SharePoint, the Lists app in Microsoft 365, or Microsoft Teams," and you can start blank, from an existing list, from Excel/CSV, or from a template. Then define the columns that model your data. Lists support typed columns — "Text, Number, Choice, Currency, Date and Time, Lookup, Yes/No, and Calculated" — which is enough to build a real tracker.

A simple parts / status tracker might use:

Nomenclature — single line of Text.
NSN — Text (a National Stock Number is a fixed-format identifier, so treat it as text, not a number).
Quantity on hand — Number.
Status — a Choice column with a fixed set of options (for example, On hand, On order, Backordered, Turned in) so entries stay consistent and are easy to filter.
Required by — Date and Time.
Document — attach one or more files to the list item for the backing paperwork. "You can attach one or more files to a list item to provide additional details."

Because a Choice column constrains entries to a defined set, a status field built as Choice keeps a shop tracker clean — no free-typed "on-hand"/"onhand"/"OH" variants to reconcile. Add the finished list as a tab in your logistics channel and the whole shop shares one authoritative view.

If your tracker needs to go further — automatic alerts when a status changes, an approval step, or a form-style data-entry app — that is where the Power Platform comes in, and it has its own gov-cloud rules. See the companion guide on Power Apps & Power Automate for logisticians.

This is the area where the DoD/gov-cloud environment behaves differently from the commercial cloud, and where a logistician most needs to be careful.

Inside your organization, sharing is straightforward. For standard channels, "team owners and members are automatically included in the site owners and members permission groups," and files and folders "can be shared with anyone in the organization by using sharable links." Microsoft's guidance is that "managing access through Teams is recommended for easiest user management and the best user experience" — so add and remove people at the Teams level rather than hand-editing SharePoint permissions.

Private and shared channels tighten this further. A private channel's permissions "are inherited from the channel itself," can't be managed in SharePoint, and are shown there only in read-only mode. A shared channel has its own site, and while files can be shared with channel members, "sharing with people outside the organization who aren't channel members isn't supported."

Reaching outside your organization is where gov cloud diverges most. Two mechanisms exist, and they are not the same:

External access lets your users "find, call, and chat with people who have Microsoft identities, including those from other organizations" — but external-access users cannot be given access to your Teams resources and cannot share files in that mode.
Guest access invites an outside person into a team as a Microsoft Entra B2B collaboration guest, where they can "chat, call, meet, and collaborate on files." Guest access "is available between Microsoft 365 cloud environments (such as commercial and GCC) by using cross-cloud guest access." So cross-cloud collaboration is possible — but it is admin-gated and configuration-dependent.

Crucially, several external-collaboration features are explicitly restricted in gov cloud. Per Microsoft, apps in external chats aren't supported in Government Community Cloud (GCC), GCC High, and Department of Defense (DoD) environments. So a workflow that depends on an app running in a chat with an outside command may simply not work in the DoD tenant, even though it works in the commercial cloud.

The practical rule for a logistician: treat external and cross-command sharing as something to confirm with your IT/security office, not something to assume. What your tenant allows is a configuration and policy decision, and gov cloud starts from a more restrictive baseline than commercial.

Records and CUI handling

Two facts matter here, and the rest is your command's policy.

First, where your data physically lives: a Teams channel's files are SharePoint content, and a Microsoft List is SharePoint content. So your organization's SharePoint governance — retention, sensitivity labeling, records management — applies to the working files and trackers you create in Teams and Lists, because that is where they are stored. Sensitivity labels, for instance, can be applied to the team or its parent site and are inherited by channel sites.

Second, what you are allowed to put there is a policy and accreditation question, not a toggle in the product. The DoD Microsoft 365 environment's authorization is governed by the DoD Cloud Computing Security Requirements Guide (SRG), and what categories of information you may store depend on your tenant's accreditation and your command's data-handling rules. This guide does not authorize any specific data — controlled unclassified information (CUI) or otherwise — at any specific impact level.

The working rule: never place controlled or classified information into a Teams channel, SharePoint site, or List unless you have confirmed the environment is accredited to hold it and you are applying the required CUI markings and access controls. When in doubt, ask your information owner, records manager, or security office before you type. See the DoD M365 environment for logisticians hub for how impact levels and accreditation work at the environment level.

Common gotchas

"Teams files" are SharePoint files. There is no separate Teams file store. Deleting, moving, or re-permissioning a channel's files means touching SharePoint — because "the files you see on the Files tab in a team are stored in a SharePoint site." Understanding this prevents a lot of confusion about "where did my file go."
Private channels fragment your storage. Every private channel spins up its own separate SharePoint site. That is the point (isolation), but it means a team with many private channels has many separate document libraries to manage. Use private channels deliberately, not reflexively.
Manage membership in Teams, not SharePoint. For channel sites, "site permissions can't be managed in SharePoint" and display read-only; Microsoft recommends managing access through Teams. Hand-editing SharePoint permissions on a Teams-connected site is the road to a confusing, drift-prone setup.
Model NSNs and stock numbers as Text, not Number. A Number column will strip leading characters and formatting. Use a Text column for identifiers and a Number column only for true quantities and dollar values.
External sharing is not the same as internal sharing. External-access users can't access your Teams resources or share files; guest access is a separate, admin-gated path; and some external features (apps in external chats) don't exist in GCC/GCC High/DoD at all. Don't assume a cross-command workflow that works in the commercial cloud works in the DoD tenant.
CUI is a policy decision. The stack can technically hold a file; whether it is allowed to depends on your tenant's accreditation and your command's rules. Confirm before you store controlled information.

Flank Speed — the Department of the Navy's Microsoft 365 cloud environment; the tenant this collaboration stack runs inside for the Navy. Start there for access, onboarding, and the Nautilus virtual desktop.
DoD M365 environment for logisticians — the hub guide: what the DoD Microsoft 365 environment is, impact levels and accreditation (DoD Cloud SRG), and what tools you have.
Power Apps & Power Automate for logisticians — the companion spoke: when a List tracker isn't enough and you need alerts, approvals, or a custom app on top of your SharePoint List, with the gov-cloud connector and licensing caveats.

Last verified

This page was last reviewed on 2026-07-04. The product behavior described here — how Teams, SharePoint, and Lists relate; where channel files are stored; how standard, private, and shared channels differ; the Lists column types; and the external-access vs. guest-access distinction — is sourced from Microsoft's own documentation (Microsoft Learn "Teams and SharePoint integration," updated 2025-05-29; "Use guest access and external access to collaborate…," updated 2026-07-01; "Availability and use of Teams apps by different types of users…," updated 2026-06-25; and Microsoft Support "Introduction to lists"). Two items are deliberately not asserted and are flagged for human confirmation against a DoD/DON primary before publication: (1) the specific cross-command external-sharing rules for the Navy Flank Speed tenant (tenant policy, not generic product behavior), and (2) the specific impact level and CUI authorization of the Flank Speed environment — stated here only as SRG-governed and tenant-specific. Confirm both with your IT/security office or the authoritative DoD Cloud SRG / Flank Speed documentation. To suggest a correction, use the site's correction path.

Frequently asked questions

What is the difference between Teams, SharePoint, and Microsoft Lists?: They are three layers of one collaboration stack. Microsoft Teams is the front door — a collaboration tool where you chat, meet, and organize work into channels. SharePoint is the backend that stores files and publishes content; every Teams team is automatically connected to a SharePoint site, and the files you see on a channel's Files tab actually live in that SharePoint site. Microsoft Lists is a lightweight, structured way to store and track data (a collection of items with typed columns) that lives on a SharePoint site and can be surfaced as a tab inside a Teams channel. In short: Teams is where you talk, SharePoint is where files live, and Lists is a simple database for tracking things — and all three are wired together.
Where do files shared in a Teams channel actually get stored?: In SharePoint. When you create a team, a SharePoint site is created and connected to it automatically. The files you see on the Files tab in a team are stored in a SharePoint site — all standard channels in a team share the same SharePoint site, with a separate folder for each channel. Private channels and shared channels are different: each private channel and each shared channel gets its own separate SharePoint site, and only members of that channel can access it. So a Teams channel's Files tab is really a view into a SharePoint document library behind the scenes.
How do I build a supply or status tracker in Microsoft Lists?: Create a list, then define the columns you need. A list is a collection of data you can share with your team, and it supports typed columns — including Text, Number, Choice, Currency, Date and Time, Lookup, Yes/No, and Calculated — so you can model fields like NSN, nomenclature, quantity on hand, status (a Choice column), and a required-by date. You can create the list in SharePoint, in the Microsoft 365 Lists app, or directly in Microsoft Teams, and you can attach one or more files to a list item for supporting detail. Add the list as a tab in your logistics channel so the whole shop works the same tracker.
Can I share a Teams channel or list with someone at another command in the gov cloud?: It depends on the environment and how sharing is configured, and gov-cloud tenants (GCC, GCC High, and DoD) are more restricted than commercial. Guest access — adding an external person to a team as a Microsoft Entra B2B guest — is available between Microsoft 365 cloud environments (such as commercial and GCC) using cross-cloud guest access, when your admin allows it. But several external-collaboration features are explicitly restricted in gov cloud: for example, apps in external chats aren't supported in GCC, GCC High, and DoD environments. Whether and how you can collaborate across commands depends on your tenant's policies — confirm the current rules with your IT/security office before relying on external sharing for mission data.
Can I store CUI in Teams, SharePoint, or Lists?: Only within an environment that is authorized to hold that information, and only following your organization's data-handling and CUI marking rules — this guide does not authorize any specific data at any specific impact level. The DoD Microsoft 365 environment's authorization is governed by the DoD Cloud Computing Security Requirements Guide (SRG), and what you may store depends on your tenant's accreditation and your command's policy. Never place controlled or classified information into a workspace unless you have confirmed the environment is accredited for it and you are applying the required markings and access controls. When in doubt, ask your information owner, records manager, or security office.
How is a private channel different from a standard channel for permissions?: A standard channel is visible to all members of the team, and all standard channels share the team's single (parent) SharePoint site with a folder per channel. A private channel is restricted to only some of the team's members and has its own separate SharePoint site — only members of the private channel can access that site, and its permissions are inherited from the channel itself and shown read-only in SharePoint. Use standard channels for the whole shop's work and a private channel when a subset (for example, a small planning cell) needs a walled-off space with its own file storage.
Do I need to be a SharePoint expert to run a logistics workspace?: No. The point of the stack is that Teams and Lists put a friendly front end on SharePoint. You create a team, add channels for the way your shop is organized, drop files on the Files tab (which SharePoint stores for you), and stand up a Microsoft List for anything you need to track — all without writing code or hand-building a SharePoint site. Manage membership and most day-to-day settings from Teams; Microsoft's guidance is that managing access through Teams is the easiest approach and gives the best experience. Reach for a SharePoint admin only for tenant-level settings your shop can't change itself.
What is Flank Speed and how does this stack relate to it?: Flank Speed is the Department of the Navy's Microsoft 365 cloud collaboration environment — the Navy's tenant of the DoD Microsoft 365 cloud, providing email, Teams, OneDrive, Office apps, and SharePoint. Teams, SharePoint, and Lists are the collaboration products you use inside Flank Speed (and inside the equivalent tenants other DoD components run). This guide covers how those products work and how to build a logistics workspace with them; for the environment itself — access, Nautilus virtual desktop, and onboarding — see the Flank Speed tool page and the environment guides linked below.