Forum Discussion
Copilot in Word can't read chat attachments; Word for web file picker shows “no token obtained”
I am having the same issue. I have not been able to go into as much detail as you, but I find that Copilot in Word works intermittently - sometimes it shows me files from OneDrive that were deleted years ago (like 2013???). Sometimes the file upload works and Copilot is able to read the file. Sometimes it will not read an uploaded file, but then straight after it told me the file was unreadable, I use the "/" command to access recent OneDrive files, select the file and it can read it. I have tried everything the internet has suggested for this issue, including clean installs etc. I recently purchased a new PC with a fresh Windows install, did a fresh Office 365 install and still have the issue. No help from Microsoft at all.
The only solution I found is employing the M365 Copilot desktop app, where the files upload just fine - no token or ingestion issues. The downside is that M365 can't edit Word files directly (or at least, not easily if the files are complex, like with several tables and lots of text and complex formatting), so usually I have to tell it to prepare some specific section of text as a Word file for download, and then manually insert it into the actual Word file I am working on, and then, once the section is pasted into the working file, use Word Copilot for any further work with it.
The other downside is that the M365 chat is not persistent for very long, I am not sure what the timeout is if I am not actively using M365 Copilot, but probably less than an hour. So if I am working on the same task and the same set of files, I have to re-upload them every time I take a break from it.
Of course, all this still beats not having Copilot/AI for what I do... Can't imagine life without it now.
