missing co-pilot conversation history after update:
I have updated Co-pilot this morning. when co-pilot restarted my chat history/ conversations were uploaded... except for one. the affected conversation started in January 2026 and is significantly larger than your other chats (a project based sparring exchange). I refreshed, but that did not work out: error message ("Unable to load"/white screen. other smaller conversation did up-load correct. I use Copilot app version macOS Tahoe 26.6.2 version. support could not help me and send me to this platform....
Chats desaparecido tras actualización de Copilot
Después de la actualización de Copilot, la nueva interfaz no muestra ninguna de mis conversaciones. Utilizo la misma cuenta de Microsoft en PC y móvil. Antes de que la actualización se completara, podía ver y abrir todos mis chats desde la interfaz antigua, por lo que las conversaciones seguían existiendo. Ahora la nueva experiencia muestra el historial vacío. ¿Se trata de un problema conocido de migración o sincronización del historial?M365 Copilot Chat (work) not working in Teams
We have a number of users who are licensed for M365 Copilot, yet the Copilot in Teams is only showing the free chat version. The Work/Web toggle is not present, and it's defaulting to free (web). This is also the case when accessing via www.microsoft365.com/chat But M365 Copilot features are available in Word, Excel, PowerPoint etc. It must be some policy, but I'm not sure where to start to look. Any advise on where to start would be welcomed! Licenses of affected users are assigned via Okta, and users not affected are not assigned through Okta. So that's a big clue, but why only Teams and web chat? Thank you.Microsoft 365 Copilot
Microsoft 365 Copilot – Persistent Source Access, Retrieval and Corpus Analysis Failures I am posting this because I have been experiencing persistent problems with Microsoft 365 Copilot when working with academic source material, and after multiple troubleshooting attempts, support contacts, and Level 2 escalation, I still do not have a meaningful explanation or solution. My use case is academic research. I work with a corpus of approximately 17–20 academic textbooks, handbooks, dictionaries, and reference works in linguistics and sociolinguistics. My goal is deliberately to test the maximum practical capacity of the subscription plan I am paying for, especially regarding multi-source analysis, retrieval, source grounding, session continuity, comparison, and synthesis. The subject matter itself is completely clear to me. I know what is contained in these sources, I am familiar with the terminology and relevant concepts, and I can independently verify whether Copilot has actually accessed the relevant material, omitted major sources, misunderstood terminology, or produced a synthesis that does not reflect the corpus. This is therefore not a case of an unclear prompt or of a user being unable to evaluate the answer. What I have already tested I have tried multiple ways of providing the source material. I have: used files stored within the Microsoft ecosystem; used OneDrive; tested Microsoft 365 Copilot; tested Copilot workflows involving Word; tested Notebook-style source workflows; rewritten and simplified prompts; created detailed protocols instructing Copilot to analyse all available sources; explicitly required source attribution; explicitly required comparison between authors; instructed Copilot not to stop at automatically generated summaries or partial retrieval output; converted the material into different file formats. The file-format testing produced one particularly strange result. Ironically, the most satisfactory results were obtained only after taking an original, fully functional academic PDF textbook — with intact indexing, tables, structured text, and no access restrictions — converting it first into an image-only PDF with no OCR, and then into an image-based PDF with OCR. These degraded versions are clearly less suitable for serious academic analysis than the original structured PDF. Nevertheless, they were among the versions for which Copilot was at least able to confirm that it had access to the document content. This is difficult to explain from a user perspective and suggests that the document retrieval or ingestion behaviour may not be functioning consistently. Main problems observed 1. Incomplete corpus analysis In one test, Copilot produced an academic-looking synthesis based on only three sources from a corpus of approximately 17–20 files. Only after being challenged did it acknowledge that it had not systematically reviewed the remaining files. For academic work, this is a serious problem. If the task is to analyse a corpus, using only a small subset without clearly stating that limitation makes the result unreliable. 2. Unreliable source access Copilot sometimes appears to know that the file exists but is unable to continue analysing it. Depending on the session, it may indicate that: it cannot access additional source content; only previously extracted content is available; it cannot continue beyond the currently retrieved material; the source is no longer usable in the ongoing task. This makes long-form source-based research unreliable. 3. Session continuity problems I have also observed behaviour suggesting that source or analysis sessions can become inactive or unusable. This is particularly problematic in multi-document work, because a corpus analysis requires continuity across multiple steps and multiple sources. 4. Summary versus source-content confusion At several points, Copilot treated a summary or summarised retrieval result as though it were effectively the available document content. The underlying files are not summaries. They are full academic textbooks and reference works. An automatically generated summary should not become the endpoint of the analysis if the full document is available. I repeatedly instructed Copilot to continue retrieving and analysing the underlying source text rather than stopping at the summary layer. Copilot itself eventually acknowledged that this would be the correct approach, but was still unable to continue consistently. 5. Weak source traceability For academic synthesis, I need to know which source supports each major conclusion. This remains inconsistent. A polished paragraph is not sufficient if I cannot reliably determine: which source was actually accessed; which authors were compared; which statement came from which file; which parts are synthesis and which parts are generic model knowledge. Source traceability is essential for academic work. 6. Task drift In some cases, after being repeatedly reminded of the original task, Copilot began suggesting unrelated outputs such as: a full course; a dictionary; exam preparation; a 30–50 page outline; other academic products. These were not requested. The original task was still to perform corpus-based analysis of a specific linguistic topic. 7. Word editing failures I have also encountered cases in Word where Copilot responded that it was unable to start editing the selected text and that nothing in the document had been changed. This adds to the impression that the issue is not limited to one specific Copilot surface. Example of inconsistent session behaviour I have also seen extremely simple requests behave inconsistently within the same Copilot session. For example, the exact same question: “What is the current time?” first received: “Sorry, I wasn't able to respond to that.” and shortly afterwards received a correct current-time response. This is obviously not an academic research task, but it is useful because it demonstrates that the instability is not always caused by complex source material. Support history I have already contacted multiple Microsoft support agents. I have also interacted with Level 2 technicians. I have submitted reports through Copilot feedback channels and through Microsoft support. I have provided detailed explanations of the behaviour. I have repeatedly tested the issue using different approaches. So far, I have not received a meaningful technical explanation of the root cause, and the behaviour has not materially changed. What I would like Microsoft to clarify I would appreciate technical clarification on the following points: What are the practical limits on the number of sources that Microsoft 365 Copilot can meaningfully analyse in one research workflow? Are there documented limits on retrieval depth within large PDFs? Why can a document be available in the Microsoft environment but still become inaccessible or unusable during the task? What causes source-analysis sessions to become inactive? Why can degraded image-based/OCR versions sometimes appear more accessible than the original structured PDF? How can a user verify which files were actually accessed and analysed? Why does Copilot sometimes operate only on summaries or partial retrieval output? Are there differences in source access and retrieval capability between Microsoft 365 Copilot, Word, Notebooks, and other Copilot surfaces? Is Microsoft aware of a wider issue involving source grounding, file retrieval, or session continuity? Is there a recommended workflow for reliable academic analysis across a corpus of 15–20 large reference works? I am not looking for another generic troubleshooting response. I would genuinely like to understand whether this is a known technical limitation, a retrieval issue, a session-management issue, or something else. I am willing to provide examples, screenshots, test cases, and additional details if that would help reproduce the behaviour. At the same time, I think it is reasonable to say that I cannot justify continuing to pay for a product if the core functionality I am paying for — reliable access to, analysis of, and grounding in the sources I provide — does not work consistently enough to be usable.Combining Project, Image, and Notebook Features for a Unified Experience
I'm currently using two different Copilot app experiences to manage my work, projects, and notebooks and each one excels in different areas while missing key capabilities found in the other. One app provides a much richer project management environment, with Tasks, true project folders, plugin connections, and the ability to embed instructions. The other offers a stronger, more fluid notebook experience, but lacks the depth and structure that the project-focused app provides. Switching back and forth between these environments creates friction, especially when I want my projects and notebooks to live together in one unified workspace. The separation makes the workflow feel fragmented. There are also inconsistencies across creative and experimental features. One Copilot app uses Create for image editing, while the other uses Imagen. One includes Team of Advisors, while the other doesn’t. Different experiments appear in different places, and the overall experience feels split rather than cohesive. I’d love to see these capabilities brought together into a single, integrated Copilot environment. I would love to have one place where projects, notebooks, agents, experiments, and creative tools coexist. Additionally, the video creation experience could benefit from deeper AI integration. Clipchamp is functional, but it doesn’t yet feel like an AI‑accelerated workflow. A more advanced, model video tool would dramatically improve speed and creativity for users who rely on Copilot for content production. Finally, many of us want broader access to Cowork and more agentic capabilities. The ability to design or customize our own agents would unlock huge value, especially for users who depend on Copilot for complex workflows. Right now, I often have to go elsewhere to build agentic tools because Copilot doesn’t allow enough personalization or agent creation within its own ecosystem. Bringing these experiences together ... unified projects, enhanced notebooks, consistent creative tools, richer video AI, and expanded Cowork access would create a far more powerful and seamless Copilot environment for everyone.Why is it so hard to get tech support?
The chat said they can't help me and then said to start a discussion incase a peer can help me. But its diagnosed as a back-end account issue: Based on the troubleshooting performed so far, the issue appears to be specific to your Microsoft account, as: Copilot is failing on multiple platforms (MacBook, iPhone, and web browser). The issue occurs in both normal and Incognito/InPrivate sessions. Your Microsoft 365 Personal subscription is active. Your Copilot credits are available. Another Microsoft account works normally on the same devices. At this point, I recommend reaching out to the Microsoft Copilot Technical Community, where account-specific Copilot issues can be reviewed by Microsoft moderators and specialists who can investigate service-side restrictions, account anomalies, or backend-related issues.
After a week of heavy use, Microsoft 365 Copilot is creating more work than it saves
I am posting this publicly because I want to know whether other Microsoft 365 Copilot users are experiencing similar issues. Over the last week, Copilot has repeatedly created more work instead of reducing it. The recurring issues include: Failure to consistently use information that already exists within authorized Microsoft 365 content. Incomplete deliverables that require multiple rounds of prompting and manual assembly. Loss of context during longer conversations. Conversations becoming unresponsive with no practical recovery path. Assumptions presented as if they were verified facts. Deliverables requiring manual validation before they can actually be used. A recent example perfectly summarizes the problem. While helping me prepare Microsoft feedback, Copilot generated content that exceeded the destination character limit multiple times, even after being told the limit had already been exceeded. I repeatedly had to paste the content, discover the failure myself, return to Copilot, and request another correction. The user became the validator because the AI did not validate its own output before presenting it as complete. The larger concern is that this pattern appears across many workflows. The experience often looks like this: Request submitted. Incomplete answer returned. Missing information identified. Additional prompting required. Information is finally found. Consolidation requested. Additional omissions discovered. User assembles the final product manually. That is not productivity improvement. That is transferring research, validation, correction, consolidation, and quality assurance back to the user. I would appreciate input from other enterprise users: Are you experiencing similar issues? Have you found effective workarounds? Has Microsoft discussed planned improvements around context retention, workflow continuity, conversation recovery, enterprise grounding, response completeness, and validation? I have already submitted formal feedback through the Microsoft Feedback Portal and welcome discussion from users and Microsoft representatives.Copilot in Word can't read chat attachments; Word for web file picker shows “no token obtained”
Summary of the issue I am seeing a persistent failure with Copilot attachments specifically inside Microsoft Word. Copilot in Word desktop and Word for the web can recognize an uploaded chat attachment by filename or OneDrive URL, but it cannot read the file contents. It reports the uploaded file as empty, corrupted, or in a format it cannot process. The same files are successfully read by standalone Microsoft 365 Copilot Chat using the same Microsoft account, and file uploads also work in Excel Copilot and PowerPoint Copilot. Failure started 10 days ago, with no obvious changes in settings on my end. The most useful diagnostic clue so far is that Word for the web’s Copilot attachment/file-picker path has also failed before any file was selected, showing “Something went wrong, please try again or refresh the page, no token obtained.” In Chrome, Word for the web produced a SharePoint-style error page with a correlation ID. This makes the issue look less like a bad file or local Word installation problem and more like a Word Copilot attachment-picker, OneDrive/SharePoint authorization-token, or file-handoff problem. Environment and scope Windows 11, Pro. Microsoft Word desktop: issue reproduced after updating Office and Windows. Word for the web: issue reproduced in Edge, Edge InPrivate, and Chrome. Standalone Microsoft 365 Copilot Chat / copilot.microsoft.com / m365.cloud.microsoft/chat: uploaded files can be read successfully with the same Microsoft account. Excel Copilot and PowerPoint Copilot: uploaded files work. OneDrive in Chrome: upload/download and file access work normally with the same account. Same Microsoft account used throughout. File types tested include tiny TXT files, PDFs, and DOCX files, including a complex DOCX. Copilot in Word can read the active Word document normally; the failure is limited to files uploaded as Copilot chat attachments inside Word. Observed behavior In Word desktop, Copilot chat accepts or recognizes the attachment metadata, including filename and sometimes a OneDrive URL, but when asked to read or summarize the file it says the file appears to be empty, corrupted, or in a format it cannot process. This happens even with a very small TXT test file. In Word for the web, the same general failure occurs. In one clean test, I created a brand-new blank Word document in Word for the web, opened Copilot, attached a tiny TXT file, and asked what the uploaded TXT file said. Copilot responded: “The uploaded file ingestion_test_731_1915.txt appears to be empty, corrupted, or in a format I can’t process, so I can’t read any text from it.” In another Word for the web test, clicking Copilot’s “+” attachment button and choosing either “My Files” or “Recent” opened a mostly blank window saying: “Something went wrong, please try again or refresh the page, no token obtained.” This occurred before any file was selected. In Chrome, Word for the web produced this error when trying to use the Copilot attachment flow: “Sorry, something went wrong. An unexpected error has occurred. Technical Details: Troubleshoot issues with Microsoft SharePoint Foundation.” The error included Correlation ID 64062ea2-3083-8000-a0f7-fbf4f6bb617d and Date/Time 8/4/2026 12:21:38 PM. Evidence matrix Test Result Standalone Microsoft 365 Copilot Chat / copilot.microsoft.com DOCX, PDF, and TXT uploads can be read successfully with the same account. OneDrive in Chrome Upload, download, and file access work normally. Excel Copilot Uploaded files work. PowerPoint Copilot Uploaded files work. Word desktop Copilot Attachments are recognized but reported as empty, corrupted, or unprocessable. Word for the web in Edge/InPrivate Tiny TXT attachment reported as empty, corrupted, or unprocessable. Word for the web attachment picker “No token obtained” message before file selection. Word for the web in Chrome SharePoint Foundation-style error with correlation ID 64062ea2-3083-8000-a0f7-fbf4f6bb617d. Word Copilot reading the active document Works normally. Troubleshooting already tried Updated Microsoft Office / Microsoft 365 desktop apps. Updated Windows. Restarted Word multiple times. Restarted the computer multiple times. Signed out and signed back in. Confirmed that the same Microsoft account is being used; there is only one Microsoft account involved. Toggled connected experiences off and back on, including restarts between changes. Started Word in Safe Mode. In Safe Mode, Copilot chat opened but did not activate properly; the Copilot pane appeared to cycle in the background and sub-windows were blank/unusable. Tested with a brand-new blank Word document in Word for the web. Tested in Edge, Edge InPrivate, and Chrome. Tested with very small TXT files as well as PDF and DOCX files. Confirmed OneDrive itself works normally in Chrome by uploading and accessing files successfully. Confirmed standalone Copilot and Excel/PowerPoint Copilot can process uploaded files successfully. Why this does not look like a local file or browser problem The same uploaded files work in standalone Microsoft 365 Copilot Chat, and OneDrive upload/download works normally. The issue also reproduces across Word desktop and Word for the web, across multiple browsers, and with a brand-new blank Word document. Because Word Copilot can read the active document but cannot acquire or process uploaded chat attachments, the failure appears isolated to the Word-integrated Copilot attachment picker, authorization-token acquisition, or OneDrive/SharePoint file-handoff path. Most likely failure area My current working theory is that Word-integrated Copilot is failing to obtain or pass the required SharePoint/OneDrive authorization token for Copilot chat attachments. The “no token obtained” message and the SharePoint Foundation correlation ID point toward the file-picker or backend handoff path rather than file contents. It may be account-specific, feature-flight/routing-specific, or a Microsoft-side regression affecting Word Copilot attachment handling. Request for help Has anyone seen Word Copilot attachments fail in this way while standalone Copilot, OneDrive, Excel Copilot, and PowerPoint Copilot all still work? Are there known Word Copilot attachment-picker, OneDrive/SharePoint token, or feature-routing issues that can affect only Word-integrated Copilot? If Microsoft support or engineering can trace backend logs, the most relevant correlation ID I have is 64062ea2-3083-8000-a0f7-fbf4f6bb617d from 8/4/2026 at 12:21:38 PM in Word for the web in Chrome. I would especially appreciate suggestions for anything beyond the standard local troubleshooting already tried. At this point, the pattern suggests the next useful step is probably backend investigation of the Word Copilot attachment/file-picker authorization flow rather than more file-format testing or local repair.
New Copilot update has made a chat inaccessible
I am experiencing an issue with a Copilot chat that appears to have become inaccessible after a recent update where the . This happened since Friday 21st August. I first noticed when all of my chats were migrated except one chat which is no longer visible in my chat history. I am logged into the same Microsoft account for the chat that is missing on which I created it. I have tried searching for it on the desktop app and in the browser with no luck. By some chance I had a Chrome browser tab open from an older Copilot session, which shows the older Copilot UI and the chat is there. The chat is fully functional: I can open it, view its history, send new messages, and receive responses. But this chat only is visible in the old UI and cannot be accessed in the new Copilot experience. The URL cannot be copied and pasted into a new tab because it redirects the copilot.microsoft.com URL to copilot.com and goes to a blank chat. The problem is if I close this browser tab, it will not be visible anymore. I have tried on the desktop app, a fresh browser tab, a fresh browser using incognito mode and even on mobile and on all of those, the new Copilot UI/Experience loads up without the chat I need. As part of my troubleshooting on the old Copilot Experience, I moved the chat to a "Project". But now I am unable to move it out of the "Project" And the new Copilot experience doesn't have a "Projects" section but instead a "Notebooks" section and I can't find it there either. You can see in both screenshots the UI is different. Because the chat now is in a Project it has a URL in the format: https://copilot.microsoft.com/projects/{project-id}/chats/{chat-id} Opening this URL on other devices or browsers redirects to the new Copilot experience and starts a new chat instead of opening the existing Project chat. As mentioned before on the new Copilot experience, this chat cannot be found anywhere else, even in the list "Chats". I can confirm that this is the same Microsoft account since my other chats have synced correctly. I have tested the URL on other browsers too with the redirect issue. The Project chat remains accessible and functional only within the old Copilot session. The chat I need contains an active, ongoing project. Although it remains accessible in the current browser tab, I have no reliable way to reopen it elsewhere, and I am concerned that if the session is lost or if I have to restart my browser or PC, I may permanently lose access to the Project chat and its accumulated context. Could you please investigate whether this Project chat is associated with an older Copilot experience, a migration issue, or a synchronisation problem between Project chats and the newer Copilot interface? Thanks, JCreated agents are shown twice in "Shared with you"
Hi all I've noticed for myself, and for several of our users, that when agents are created in Copilot Studio, and shared. Each agent is shown twice, when people access their "Shared with you" in Copilot. Why is that, and does anybody else experience this?
