For account managers running QBRs, is M365 Copilot enough or do you need workflow-specific agents?
Hi Microsoft 365 Copilot community, I’m trying to better understand how account managers and customer-facing teams are using Copilot for recurring business review workflows. Imagine you manage dozens of merchant or customer accounts. Every quarter, you need to prepare business reviews, summarize account performance, identify changes from the prior period, create executive-ready slides, recommend next actions, and send follow-up notes. For those of you doing similar work today: - Is Microsoft 365 Copilot enough for this workflow using prompts across Excel, PowerPoint, Word, Outlook, and Teams? - Where does the process still become manual or hard to repeat? - Do you need batch handling across many accounts, or is one account at a time enough? - How important is quarter-over-quarter history tracking? - Do you want outputs organized automatically in OneDrive or SharePoint so each account has a durable review history? - What would make this kind of workflow trustworthy enough for executive or customer-facing use? I’m especially interested in the business-user perspective: account managers, customer success managers, partner managers, sales operations, merchant services teams, and anyone who prepares recurring customer/account reviews. For context, we recently built a Microsoft 365 Marketplace agent called Merchant QBR AutoPilot that explores this pattern: batch QBR scorecards, PowerPoint outputs, OneDrive organization, and follow-up email drafts. But my main question is broader: what would you actually want Copilot or a workflow-specific agent to do for quarterly account reviews? Curious how others are approaching this.
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.
The GPT 5.5 Think Deeper Model on Copilot is not responding
I have tried all possible troubleshooting methods to correct this issue but the GPT 5.5 Think Deeper model seems to not be working and the Microsoft Support team also was not able to provide any help on this issue. Can you suggest what possible issue it could be at my end and how to fix the same and this issue is being faced by everyone on my Microsoft 365 License Everytime I ask for a response from GPT 5.5 Think Deeper model I am getting the error message " Sorry, I wasn't able to respond to that. Is there something else I can help with? " And these are for AI commands that it had been responding properly beforeCoPilot account issue
Bot WC said: 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. Where can a specialist sort this for me?How to Avoid Tasks Copilot "You've reached our weekly Tasks limit"
I’ve been using both Chat‑Copilot (CC) and Tasks‑Copilot (TC) extensively, and I wanted to share a brief summary provided by TC, that may help others understand how each tool works, why TC sometimes stops responding, and how to avoid running into limits. ⭐ 1. Chat‑Copilot and Tasks‑Copilot serve different purposes Chat‑Copilot Real‑time conversational AI Great for brainstorming, drafting, coding, calculations, and iterative design Stateless — each message is processed independently Very stable and rarely gets stuck Tasks‑Copilot Designed for multi‑step workflows Can create and maintain documents Runs long‑lived background tasks Maintains persistent state More powerful for structured work More fragile because it depends on a task‑execution pipeline These two systems are independent. Chat can work perfectly even when TC is frozen. ⭐ 2. Why Tasks‑Copilot hits limits or becomes unresponsive TC can stop responding when: A task runs too long A multi‑step workflow fails mid‑execution The task state becomes corrupted The weekly quota system triggers The backend fails to reset on Friday Too many “pipeline‑style” requests are issued in a short time When this happens, TC may: stop responding entirely ignore all prompts remain stuck across all devices and browsers This is a backend state issue, not a browser or device problem. ⭐ 3. How to avoid triggering TC limits Here are practical ways to keep TC healthy: Use Chat‑Copilot for: brainstorming engineering design calculations drafting text generating diagrams or prompts step‑by‑step reasoning Chat handles these extremely well and never “uses up” TC capacity. Use Tasks‑Copilot only for: creating structured documents maintaining long‑form reports assembling multi‑section deliverables tasks that explicitly require persistent state Avoid these patterns in TC: “Build the entire document end‑to‑end” “Run this whole workflow” “Generate all sections at once” Rapid‑fire edits or repeated task triggers Very large or complex requests Instead, break work into small, single‑action steps. ⭐ 4. When TC gets stuck, what can users do? For consumer Microsoft 365 Personal accounts: There is no user‑accessible reset button Frontline support cannot reset TC’s task state Creating a business account does not fix the issue The only options today are: submit feedback post on the Tech Community wait for the backend to refresh This is a known limitation of the current TC preview. ⭐ 5. What would help users going forward A few improvements would make TC much more reliable: A user‑visible “Reset Task State” button Error messages instead of silent failures More predictable weekly resets Support tools that allow agents to clear stuck task containers
Retention after deletion
We currently have no retention or deletion policy set for copilot chats. I'm aware that these are now seperate from teams chats. We are considering setting deletion to 6 months but this may take time to proceed through. If users manually delete chat logs in the meantime how long are they retained in any form by default?
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, J
