Revoke a Teams chat file after a project ends

A project chat can end while its attachments remain accessible. Microsoft stores files sent in chats in the sender's OneDrive for Business, where links and direct grants may remain. Removing a person from a conversation or deleting the message is not a reliable substitute for reviewing the file's permissions. The owner should identify the exact file and decide whether to remove one person's access, one link or all sharing, because other collaborators may still need it.

Before you start​

Get the file name and the original chat, and make sure you own the file or can contact the owner. Ask whether a successor needs a copy before you revoke access. If the file is part of a legal or retention workflow, follow the organization's policy; do not delete records to make a link disappear.

Do it step by step​

1. In Teams, open the chat and its Shared tab, then identify the exact file. If there are multiple versions with the same name, check the owner and modified time before acting.
2. Open the file in OneDrive for work or school and select Manage access. Inspect People, Groups and Links. A person may have direct access, access through a broad link or access through a parent folder.
3. If only one recipient should lose access, remove or change that person's direct grant or the relevant link. If every external share should stop, use Stop sharing after confirming that necessary internal collaborators have another route.
4. Check whether a parent folder or SharePoint site still grants access. A child-file link removal will not override inherited permission; involve the site owner or admin if that is the real source.
5. Refresh Manage access and, if possible, test with a previously authorized non-owner account. Confirm the link now fails or the permission is reduced, while intended collaborators still have access.
6. Record the decision in the project's handoff notes and check copies shared by other owners separately. If the file contained secrets, rotate those credentials rather than assuming permission revocation makes them secret again.

Check the result​

The unwanted person or link is absent from Manage access and a practical access test confirms the restriction. Legitimate collaborators retain the intended route.

If something goes wrong​

If an access entry reappears, check inherited folder or group membership. If the owner is another teammate, ask them to make the change; copying the file to your own OneDrive does not revoke their original. If a meeting recording is involved, inspect the recording's separate OneDrive or SharePoint permissions.

Know the limit​

Revocation stops future access through the controlled path; it cannot pull back downloaded copies, screenshots or a forwarded document. A deleted Teams message is a conversation change, not a proof of file-permission change. Retention and legal hold may preserve records even after collaboration ends. Teams storage locations Microsoft manage access