Blog
Updated 14 min read

Where Do Microsoft Teams Files Go? Every Location Explained

Founder and CEO, The Drive AI

TL;DR: Microsoft Teams does not store files. A file shared in a standard channel is stored in the Team's SharePoint site, in a folder named after the channel. A file shared in a 1:1 or group chat is stored in the sender's OneDrive, in a folder called Microsoft Teams Chat Files, and shared with the recipients. Private and shared channels get their own SharePoint site, and meeting recordings go to OneDrive or SharePoint depending on whether the meeting belonged to a channel.

Someone asks where the signed proposal went. You remember it was "in Teams". You scroll two channels and a group chat and find three versions with three names. The file is not lost. It is just not where you think it is.

"Where do Microsoft Teams files go" has more than one answer, because it depends on where the file was shared, who shared it, and what kind of channel it was.

A Microsoft Teams file is never stored in Teams itself: it is a SharePoint file or a OneDrive file that Teams shows you inside a conversation. Once you know which one, finding it, keeping it, and organizing it becomes a SharePoint or OneDrive file organization task.

Where do Microsoft Teams files go? The complete map

Every file shared in Teams lands in one of two services: SharePoint for channels, OneDrive for chats. The table covers each type of file, where it is stored, who can see it, and what happens when the sharer leaves.

Type of fileWhere it is storedWho can see itIf the person leaves
Shared in a standard channel (post or Files tab)The Team's SharePoint site, in the library folder named after the channelEvery member of the TeamNothing changes. The file belongs to the Team's site
Shared in a 1:1 chatThe sender's OneDrive, in Microsoft Teams Chat FilesThe sender and the recipientIt stays in the leaver's OneDrive, subject to the retention period your admin set
Shared in a group chat or a meeting chatThe sender's OneDrive, in Microsoft Teams Chat FilesThe people in the chat when it was shared. People added later may not see earlier filesSame as a 1:1 chat
Shared in a private channelA separate SharePoint site created for that channelMembers of the private channel onlyNothing changes
Shared in a shared channelA separate SharePoint site created for that channelShared channel members, including people from other Teams or organizationsNothing changes
Recording of a non-channel meetingThe OneDrive of the person who pressed record, in a Recordings folderMeeting participantsIt goes with the recorder's OneDrive
Recording of a channel meetingThe channel's folder in SharePoint, in a Recordings subfolderEvery member of the channelNothing changes

Two patterns explain the table. Anything shared in a channel is stored with the channel, in SharePoint, and outlives the individual. Anything shared in a chat is stored with the sender, in OneDrive, and depends on that person's account. Who can open and edit each of them, and how to change it, is in Microsoft Teams file permissions.

Are Teams files stored in SharePoint or OneDrive?

Channel files are in SharePoint. Chat files are in OneDrive. Which one applies is decided by where you clicked "share", not by the file.

When a Microsoft Team is created, Microsoft 365 silently creates a SharePoint site for it. That site has a document library, and each standard channel is a folder inside it, named after the channel. Drop a PDF into the Marketing channel, or post it in a reply, and it is written to the Marketing folder. The Files tab in a channel is not a separate store: it is a view of that SharePoint folder. Click "Open in SharePoint" and you see the same files from the other side.

A chat has no Team behind it and therefore no SharePoint site. When you attach a file in a 1:1 or group chat, Teams uploads it to your own OneDrive, into Microsoft Teams Chat Files, and creates a sharing link for the other people in the chat. The recipient never gets a copy. They get access to yours. That is why the Files tab in a chat is a list of links, not a folder, and why a chat file can stop opening when the sender's OneDrive changes.

Private channels break the first pattern on purpose. A private channel hides its content from the rest of the Team, so its files cannot sit in the Team's main site. Microsoft creates a separate SharePoint site for each private channel, and for each shared channel. One Team can own several SharePoint sites, and a search of the main site never shows private channel files.

Where are Teams meeting recordings stored?

Recordings follow the same split. A meeting scheduled in a channel stores its recording in the channel's SharePoint folder, inside a Recordings subfolder. Any other meeting, including an ad hoc call, stores its recording in the OneDrive of the person who started the recording, in a Recordings folder.

The owner of a recording is whoever pressed record, and when that person leaves, it follows their OneDrive retention. If recorded client calls matter, schedule them in a channel or move the recordings to a shared library while the recorder is still around.

How do I find files shared in Teams?

Start from where the file was shared, not from search. Teams search matches message text and filenames, so if you do not remember the wording it will not help.

For a channel file, open the channel's Files tab and sort by modified date; a file posted in a thread is still in that folder. For a chat file, open the chat's Files tab. If you sent it, it is also in your OneDrive under Microsoft Teams Chat Files. If a colleague sent it and the link no longer opens, they moved or deleted it, and only they can put it back.

For files from people who have left, ask your Microsoft 365 admin. A deleted user's OneDrive can be kept for a retention period and handed to a manager, and a deleted Team's SharePoint site can be restored for a limited window. After that, the files are gone. If files are vanishing from view rather than from storage, start with why Teams files keep disappearing.

How do you keep Teams channel files organized?

Because channel files are SharePoint files, the way to keep them organized is to organize the SharePoint folder, not the conversation. A workflow does that once and keeps doing it.

A Teams file workflow is a plain-English instruction that watches the Team's SharePoint document library, or the Teams channel itself, reads each file that arrives, and files it where it belongs. With The Drive AI there are two ways in, and they end in different places.

The first is to connect SharePoint and watch the Team's document library. A file dropped in a channel is already a file in that library, so a workflow with the File Uploaded trigger reads it with Ask AI About the File, then uses Move and Rename to file it in place, inside SharePoint. The channel still shows it in the Files tab, now under a real folder with a real name. Nothing is imported, and nothing outside the folder you named is touched. Libraries that belong to a Team are marked in the picker. SharePoint document library workflows covers this route in full.

The second is to connect Teams for Microsoft Teams file management and use the Messaging trigger. A workspace admin makes one Teams connection for the workspace and chooses the teams it covers; each workflow watches the channels it names, or every channel in a team, and never chats. Each file shared in the channel starts a run, and because the run comes from the conversation rather than the library, it gives the file a home with Save a Copy: a copy goes to The Drive AI or a connected drive, renamed and filed. The channel and its SharePoint folder are never modified. This is the route for an organized archive alongside the channel, covered in Microsoft Teams file workflows. A workflow cannot post back to Teams: Send a Message reaches Slack or an email address only.

Here is what you would type. Each step then appears on a canvas with labels (Reads the file, Waits for you, Sends outside) so you can see which steps open the file.

When a file lands in the Finance channel folder, check whether it is an invoice. If it is, read the vendor and invoice date and file it under Vendors, one folder per vendor and one per year, like Vendors/Pinecone Systems/2026, renamed vendor, invoice number, date. If not, leave it where it is.
When a file is shared in the Client Delivery channel in Teams, work out which client it is for and save a copy to Clients/Northwind/Deliverables in The Drive AI, renamed with the client, document type, and date.
Every Sunday night, go through every file in the General channel folder, including ones already filed. Sort each into Invoices, Contracts, or Reports by what it contains and rename it with the client and date.

The last one uses the On a Schedule trigger, set to every file on every run. That is how a channel folder that has been a pile for two years gets sorted in place, and how it stays sorted. Organizing SharePoint files automatically with AI walks through that first pass. To hold a file for a person instead, add a condition: "if it is a contract, ask Priya to approve before anything moves".

Which option fits: manual, built-in, Power Automate, or a workflow?

Every option below works. They differ on whether they read the document and whether they touch files already there.

CapabilityThe Drive AI WorkflowsManual filingTeams and SharePoint built-inPower Automate
Files by what the document saysYes. Ask AI About the File reads the fileIf someone opens itNo. Views and columns rely on metadata people enterNot without AI Builder
Keeps channel files in SharePointYes, when it watches the library. Moves and renames in placeYesYesYes
Renames from contentsYes. Rename infers the name or uses a patternBy handNoPatterns from metadata
Reorganizes files already filedYes. On a Schedule, every file, every runSlowlyBulk edit of columns, not foldersA scheduled flow you build
Waits for a person to approveYes. Ask a Person to Approve shows the planInformallyVia Power AutomateYes, approvals action
Posts a message back to TeamsNo. Slack and email onlyYesNot applicableYes

Power Automate fits when the trigger is a column change and the action is a Teams message. A workflow fits when the decision depends on what is inside the file and the outcome is a folder and a name.

What it will not do

A workflow watching a SharePoint library moves and renames in place. It does not import unless the sentence includes Save a Copy, and then only to the place named. A workflow started from a Teams channel copies; it never edits or removes anything in the channel. Steps marked ai read the file and can occasionally be wrong, which is what Ask a Person to Approve is for. Approvals wait three days by default and thirty at most, then take the Expired path. Connecting SharePoint or Teams needs the Max plan on a personal workspace or any Team plan. Each member connects their own SharePoint account, while Teams has one connection per workspace, made by an admin. SharePoint Online only; SharePoint Server is not supported.

Setting it up

  1. Connect SharePoint with a Microsoft 365 work or school account. A tenant administrator approves the app once for the organization; if the connection is refused, the app gives you the approval link, the permissions in plain language, and a request message to paste into a ticket.
  2. Find the Team's site by name or paste its URL, then pick the document library. Team libraries are marked. For the Messaging route, a workspace admin connects Teams instead, and the workflow names the channel.
  3. Type the sentence: which folder to watch, what to check, where to file, what to rename. The steps appear on the canvas with their labels.
  4. Edit the folder path, the approver, or the wait time on the canvas, then turn it on.
  5. Watch the activity feed. Every run is recorded, can be replayed exactly as it happened, and can be retried from the step that failed.

For triggers, steps, and approvals across every source, see the complete guide to document processing automation.

Frequently Asked Questions

Where do files shared in a Teams chat go?

Files attached in a 1:1 or group chat are uploaded to the sender's OneDrive, into a folder named Microsoft Teams Chat Files, and shared with the other people in the chat through a link. Recipients do not get a copy. If the sender moves or deletes the file, the link in the chat stops working for everyone else.

Are Microsoft Teams files stored in SharePoint or OneDrive?

Both, depending on where the file was shared. Files posted in a standard channel are stored in the Team's SharePoint site, in the library folder named after the channel. Files sent in a chat are stored in the sender's OneDrive. The Files tab in a channel is a view of the SharePoint folder; in a chat it is a list of links.

Where do private channel files go?

Each private channel gets its own SharePoint site, separate from the Team's main site, so that only channel members can reach the files. Shared channels work the same way. This is why one Team can own several SharePoint sites, and why searching the main document library never surfaces private channel files.

What happens to Teams chat files when someone leaves the company?

The files stay in the leaver's OneDrive. When the account is deleted, Microsoft 365 keeps that OneDrive for a retention period set by the admin, who can hand it to a manager. After that, the files are removed and the chat links stop working. Channel files are unaffected because they belong to the Team's SharePoint site, not to a person.

Can a workflow post a message back to the Teams channel?

No. Send a Message in The Drive AI reaches Slack or an email address only, never Microsoft Teams. A workflow watching a Team's SharePoint library or a Teams channel can read, move, rename, copy, and hold files for approval, and every run is recorded in the activity feed, but confirmation to the channel has to arrive by email or Slack.

What is the Microsoft Teams Chat Files folder in OneDrive?

The folder OneDrive creates the first time you attach a file in a Teams chat. Every file you send in a 1:1 or group chat is uploaded there and shared by link; the people in the chat get the link, not a copy, so moving or deleting the file breaks it for them. Channel files never appear in it, because they go to the Team's SharePoint site. ChatGPT and Microsoft Teams covers what ChatGPT can reach in either place.

Organizing what the channels collect

Teams shows you files. SharePoint and OneDrive keep them. Once the channel folders are the thing being organized, the conversation can stay as messy as conversations are, and the files still end up named and filed. Build your first workflow on your Team's library, or see how file workflows handle files from every source.

Share it with your network

You might also find useful