Forum Discussion
Word Copilot attachments fail with NoTokenObtained
Word Copilot cannot read local or cloud attachments with my Microsoft account.
Cloud file attachment opens OneDrive Picker but fails with NoTokenObtained, timeout, or “Sorry, something went wrong.” Local files are accepted but reported as empty/corrupted.
The same files work correctly in Microsoft 365 Copilot Chat with the same account.
The issue reproduces on different computers, different networks, new Edge profile, new Windows user, and Word for the web without Office desktop installed.
Word Copilot can read the active document, so only the attachment pipeline appears broken.
Correlation IDs: 49a92ea2-7068-2001-bf16-3cf7d0c388fd and b39b30a2-b012-f000-cf51-72bd844c5dea.
Please escalate to Word Copilot / OneDrive File Picker / Microsoft 365 Copilot engineering.
1 Reply
Copilot reads the active Word document, but its attachment picker fails across computers, networks, profiles, and Word for the web, while the same files work in Microsoft 365 Copilot Chat. More client resets are unlikely to help; the failure is scoped to Word’s attachment or OneDrive authorization path. Confirm the test file has a supported format, normal permissions, and a cloud location accessible to the account. Ask the tenant administrator to check Microsoft 365 Service health for Word, Copilot, or OneDrive incidents. If none is listed, open a Microsoft 365 service request and provide both correlation IDs, exact UTC timestamps, tenant and user identifiers, Word and browser versions, and one non-sensitive sample. State that active-document grounding succeeds while attachments fail in desktop and web Word. Do not post tokens or private documents publicly. Support can correlate server traces and route the case; the community cannot.
