How Teams Chat Attachments Really Work: Storage, Sharing and Recovery

The paperclip is the easy part. The important question is what happens after you send the file.

In Microsoft Teams, a file shared in a one-to-one or group chat is normally stored in the OneDrive of the person who shared it. A file shared in a channel is stored in SharePoint. Those two routes have different owners, permissions and recovery risks.

That distinction explains many familiar problems: “I can see the message but not the file”, “the file broke after someone left”, and “why is this document in one person’s OneDrive when the whole group uses it?”

The short answer

• Chat file: stored in the sharer’s OneDrive; access is granted to chat participants.
• Channel file: stored in the SharePoint site associated with the team or channel.
• Existing cloud file: sharing it may keep the file in its current OneDrive or SharePoint location rather than create a new governed team copy.
• A chat message is not the permission boundary: the file’s OneDrive or SharePoint permissions still decide who can open it.
• For durable team records: use an appropriate channel or governed SharePoint library, not one employee’s chat upload.

Microsoft’s current eDiscovery documentation confirms the storage split for one-to-one chats, group chats, channels and meetings.

How to attach or share a file in Teams

The exact icons and labels can change between Teams releases and device sizes, but the supported choices are consistent.

Desktop or web

1. Open the chat or channel conversation.
2. In or near the compose box, select Actions and apps, Attach file, or the paperclip/file control shown in your client.
3. Choose an existing cloud file or upload one from your device.
4. Check the file name and the audience.
5. Add enough context for recipients to know what the file is and what you want them to do.
6. Send the message.

Microsoft’s current support guide covers sharing files from OneDrive, a chat or a channel and describes the current Teams file-sharing routes.

Mobile

1. Open the chat or channel in the Teams mobile app.
2. Use the +, attachment or actions control beside the compose box.
3. Choose a recent/cloud file, photo or device file where your mobile policy permits it.
4. Select the file and send it with a short explanation.

Mobile options can differ by platform, tenant policy and Teams version. Test the managed iOS or Android experience your users actually have before writing internal instructions around one icon.

Uploading a copy and sharing an existing file are not the same

This is the second distinction that matters.

Upload from the device

Teams uploads a file into the storage associated with that conversation. For a chat, that is the sharer’s OneDrive. For a channel, it is the relevant SharePoint site or channel site.

The uploaded file is now a cloud file. Teams sends a message that points recipients to it and applies or requests the necessary sharing access.

Share an existing OneDrive or SharePoint file

The original file can stay where it already lives. Recipients work against that governed source if their permission allows it.

This can prevent duplicate copies, but location still matters. A policy document in a controlled SharePoint library should usually remain there. A project record that only exists in one person’s OneDrive may be too dependent on that person’s account.

Before sending, ask:

• Is this the authoritative copy?
• Who owns its location?
• Should recipients edit or only read?
• Will access still make sense after the chat membership changes?
• Is this file allowed to be shared with everyone in the conversation?

Where Teams files are stored

One-to-one and group chat

Microsoft says files shared in one-to-one and group chats are stored in the OneDrive account of the person who shared the file. The sharer therefore sits inside the file’s ownership and lifecycle path.

This is appropriate for conversational collaboration. It is weaker for a record that must outlive a person, project phase or informal chat.

Standard channel

Files shared in a standard channel are stored in the SharePoint site associated with the team, normally within the document library structure used by that channel. They are not stored in a channel folder called “Microsoft Teams Chat Files”.

Private and shared channels

Private and shared channels have their own SharePoint sites rather than simply using a folder in the parent team site. Microsoft’s Teams-connected sites overview explains the differences and why membership must remain aligned with the channel.

Do not move or independently manage a private/shared channel site as if it were an ordinary standalone site. Its relationship to Teams is part of the access model.

Permissions: why the message can be visible while the file is blocked

Teams messages and files do not use one single permission object.

A participant may be able to read the chat history yet receive Access denied on a file because:

• the original sharing permission was removed;
• the file was moved or deleted;
• the file came from a site they cannot access;
• the group chat membership changed;
• a sensitivity label, sharing policy or conditional-access rule blocks access;
• the person is an external-access user rather than a guest with access to the resource;
• the sharer’s account or OneDrive lifecycle changed.

Do not solve this by creating an anonymous link unless the organisation has explicitly approved that sharing model. Open the file in OneDrive or SharePoint, inspect its access, and grant only the access that is actually required.

Guest access is not the same as external access

Microsoft distinguishes two common outside-organisation experiences:

• External access supports finding, calling, meeting and chatting with people in other organisations.
• Guest access adds the person to your organisation as a guest so they can participate in a team and collaborate on team resources where permitted.

Microsoft summarises the distinction in its guide to guest and external access in Teams.

Do not assume that because an external participant can chat, they can receive every file type or open every organisational link. If outside collaboration is important, test the exact identity type, tenant policy and file location.

What happens when chat membership changes?

Adding someone to a group chat does not justify assuming that every previously shared file will be exposed to them. Teams can offer choices about how much chat history to include, while each file retains its own cloud permissions.

After adding or removing participants:

1. Review files that remain operationally important.
2. Inspect their OneDrive or SharePoint access directly.
3. Remove access that is no longer needed.
4. Move durable team records to a governed team location if necessary.
5. Test with the affected account rather than inferring access from the chat roster.

For sensitive work, avoid treating a long-running group chat as a document-management system.

Find a file again

Depending on the current Teams interface, shared files may appear in a Shared, Files or related conversation view. Search can also find a message or file when indexing and permission allow it.

If Teams does not surface the file:

• return to the message where it was shared;
• open OneDrive and search by name, owner or recent activity for a chat file;
• open the team’s SharePoint site for a channel file;
• check the channel type so you search the correct SharePoint site;
• look in the relevant recycle bin if the file was deleted;
• ask the owner to inspect Manage access, not merely resend the same broken link.

The location is more reliable than the Teams tab label. Start with chat versus channel, then follow the corresponding OneDrive or SharePoint path.

What happens when the person who shared a chat file leaves?

Because a chat-uploaded file belongs to the sharer’s OneDrive, your organisation’s offboarding and retention process matters. Account deletion is not a safe content-management plan.

For files that have become business records:

1. Identify them before the owner leaves.
2. Move or copy the authoritative version into an approved SharePoint library or team channel.
3. preserve the required metadata, permissions and retention treatment;
4. update the conversation or working instructions with the new link;
5. confirm that downstream flows, bookmarks and references use the governed location.

Do not move every conversational attachment by default. Classify the file by business value and record obligation.

Safe troubleshooting sequence

The attachment control is missing

Compare desktop, web and mobile. Check whether the user is in a meeting chat, external chat or another context with different capabilities. Then review Teams messaging/app policies, device restrictions and service health. Avoid telling users to clear all local data as the first response.

One participant cannot open the file

Open the file’s OneDrive or SharePoint location and inspect Manage access. Confirm the affected identity, link type and sign-in account. Test the file directly in a private browser session if appropriate.

Everyone gets a broken link

Check whether the file was renamed, moved, deleted or restored under a different identity. For a channel, confirm the correct connected site. For a chat, ask the original sharer to inspect OneDrive.

The wrong people can edit

Change the file permission at the source. Replacing words such as “please don’t edit” in the chat does not enforce read-only access.

A file contains sensitive information

Stop broadening access. Follow the organisation’s incident and information-protection process. Review existing permissions, link scope, audit information and any sensitivity/retention controls before deciding the recovery action.

A practical governance rule

Use chats for conversation and short-lived collaboration. Use channels and governed SharePoint libraries for documents that belong to a team, process or business record.

That does not ban chat attachments. It gives them the right role:

• a screenshot for quick diagnosis: chat may be fine;
• a draft between two colleagues: OneDrive sharing may be fine;
• the approved operating procedure: governed SharePoint library;
• a project deliverable the team must retain: channel or controlled library;
• a file for an external party: approved sharing location and explicit permission review.

Frequently asked questions

Where are files uploaded to a Teams chat stored?

In the OneDrive account of the person who shared the file, according to Microsoft’s current storage documentation.

Where are files uploaded to a Teams channel stored?

In SharePoint. Standard-channel files use the team-connected site; private and shared channels use their associated channel sites.

Does adding someone to a group chat give them every old file?

Do not assume it does. Chat history choices and file permissions are separate. Review access to important files directly in OneDrive or SharePoint.

Can an external Teams user receive a file?

It depends on whether they are using external access or guest access, the tenant policies and the file’s sharing configuration. Test the real scenario.

Should important team files be kept in a chat?

Usually not as the only governed copy. Move durable team records to an approved SharePoint library or channel where ownership and retention do not depend on one person’s OneDrive.

Keep your Teams and SharePoint guidance current

The Teams, SharePoint & Intranet Mastery Space brings current Microsoft changes, file-governance patterns and practical troubleshooting into one maintained place.

Remember the boundary: chat files are OneDrive files; channel files are SharePoint files. Once you know which side of that line you are on, permissions and recovery become much easier to reason about.