Locating documents and sharing them with others within Microsoft Teams channels or chats
Hi @Johannes Kingma,
Welcome to Microsoft Q&A forum.
Based on your screenshot, the "NoTokenObtained" error message displayed in your file picker typically indicates a momentary disruption in the authentication handshake between the Microsoft Teams desktop app and the underlying SharePoint or OneDrive services. This specific error prevents the application from retrieving the necessary security token required to browse, select, and attach files from your Team channels to a chat.
To help resolve this behavior and restore file access, please follow the troubleshooting steps outlined below:
1/ Reset the Microsoft Teams app
Since standard refresh commands may not be responsive, a formal reset of the application's components is the most effective way to clear authentication hangs:
- Type Settings in the Windows search box and select the Settings app from the results.
- Select Apps > Installed apps and then type Microsoft Teams in the search box.
- Locate the New Microsoft Teams app, select the More options button (...) on the right, and then select Advanced options.
- In the Reset section, select Reset.
- Restart Teams and sign in again to establish a fresh connection.
2/ Perform a clean restart.
If the clear cache does not succeed, please close the application entirely.
- It is important to right-click the Teams icon in your system tray (located near the clock on the taskbar) and select Quit Teams.
- Merely clicking the "X" at the top of the window may only minimize the app. Relaunching the application after a full quit will establish a completely new session and re-verify your credentials.
3/ Utilize direct file sharing.
As an alternative to the built-in file picker, open the Teams and channel where the document is stored and go to the Files tab. Find the file, then select … (More options) (or Share) and choose Copy link. Paste that link into your chat to share the file without using the file picker. If Copy link doesn’t work in Teams, open the file in SharePoint/OneDrive and copy the link from there.
4/ Reach out to IT support
If the error persists after a full reset, please reach out to the IT department for further assistance. A persistent token failure often indicates a backend synchronization conflict or a security policy restriction within your account profile that requires administrative intervention. IT can review your sign-in logs to determine if a conditional access policy or a tenant-level credential mismatch is preventing the authentication handshake.
I hope this response has helped address your question and clarify the behavior you're experiencing. Please feel free to reply if you have any further questions; I would be pleased to assist further.
Thank you for your patience and your understanding. I look forward to continuing the conversation.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.