Copilot Agent in SharePoint refuses to read uploaded attachments (even though they work in Testing)
We deployed a Copilot agent to SharePoint, customized in Copilot Studio. It works pretty well. But it can never read uploaded files, even though File Activity is turned on in SETTINGS, and even though uploaded files are read in the Testing environment in Copilot Studio. We have republished the agent multiple times. Is this a Microsoft bug/limitation, or have we set something up incorrectly? And if it's not meant to work, is there a way to remove that paperclip so users aren't tempted to try it? I can see them getting discouraged and abandoning the agent altogether. I asked Copilot for help, and it said it is what it is.
Copilot Notebooks shows "Se produjo un error" when processing PDF files (Case 7110857252)
Hola. Utilizo Microsoft 365 Personal y Copilot desde Microsoft Edge. Creé un cuaderno en Copilot Notebooks para estudiar material de un curso y agregué varios archivos PDF como referencias. Los archivos se cargan correctamente y aparecen en la sección de referencias del cuaderno. Sin embargo, cuando intento utilizar las funciones "Resumir mi bloc de notas" o "Sugerir preguntas para este bloc de notas", Copilot muestra el mensaje "Se produjo un error". El problema ocurre con distintos archivos PDF y persiste desde hace varios días. He contactado con el soporte de Microsoft (caso 7110857252) y me indicaron que existen reportes similares de otros usuarios relacionados con el procesamiento de archivos PDF y contenido en Copilot Notebooks. ¿Alguien más está experimentando este problema o conoce alguna solución temporal? Gracias.
Copilot in Word changed dramatically overnight and no longer provides the experience I paid to use
I am reporting a significant change that appears to be specific to Copilot in Word. Importantly, this is not a general Copilot account issue. The standalone Copilot app still contains my previous chat history, including chats that originated from Word before this change occurred. The problem appears to be isolated to the Word Copilot experience. Beginning on October 16-17, 2026, Copilot in Word changed dramatically: Previous Word Copilot chat history disappeared, leaving only newly created chats visible. Copilot in Word now states that it can only remember information within the current chat. Personalized preferences that previously carried across conversations no longer appear to work inside Word. The editing workflow has completely changed. Previously, Copilot presented one suggestion at a time inside a dedicated suggestion card. The prior interface used navigation arrows to cycle through alternatives and had clear Apply and Skip/Cancel actions. The new interface generates large numbered lists of suggestions and critiques instead of interactive rewrite cards. The writing assistance feels less natural, less personalized, and noticeably less human than before. The Copilot interface behavior and layout have also changed. My concern is not simply that the interface looks different. I upgraded my Microsoft 365 subscription to Premium primarily because of the Copilot experience in Word. I use Copilot heavily for editing school assignments and writing projects and often complete large amounts of work in a single session. The previous Word Copilot experience helped organize my writing, preserve my voice, and provide efficient rewrite suggestions without sounding like I ran my work through an AI bot. One of the main reasons I chose Copilot over competing AI tools is that it consistently felt more natural and more human when helping me edit and refine my work. The most significant change is not the appearance of the interface. The entire interaction style has changed. Previously, Copilot in Word felt like collaborating with an editor who reviewed my writing and helped improve it while preserving my voice. The new experience feels more like receiving an automated analysis report from a machine. Instead of helping me refine my writing through natural rewrites and conversational suggestions, it now generates long lists of critiques and recommendations. While those recommendations may be technically correct, they do not provide the same experience or value. They also do not consistently reflect the writing style, tone, and preferences that I had previously taught Copilot to remember. Instead of receiving rewrites that already sounded like my work, I now have to interpret the feedback and manually rewrite or adjust it so it sounds like me again. This adds additional effort and makes the editing process significantly less efficient than it was before. Because the standalone Copilot app still has my previous history, this appears to be a change in Word Copilot itself rather than an account-wide issue. I would like Microsoft to confirm: Whether Word Copilot was recently moved to a new experience or editing workflow. Whether the disappearance of all prior Word chat history is expected. Whether cross-chat personalization or memory behavior has changed. Whether the previous suggestion-card workflow, editing style, or interaction model can be restored or selected as an option. I understand that Copilot is an AI system, and I do not expect it to behave exactly like a human editor. However, one of the reasons I chose Copilot over competing tools was because it consistently helped me improve my writing while preserving my voice and reducing the amount of editing I had to do myself. After this update, I have found myself relying on Copilot less because it no longer provides the same level of personalized editing assistance, voice preservation, and workflow efficiency that I previously depended on. This change was immediately noticeable and has significantly reduced the value I receive from the Microsoft 365 subscription I purchased specifically to use Copilot in Word. I am not requesting new features. I am trying to understand whether this change was intentional, whether the previous Word Copilot experience is still available, and whether some of these issues may be related to the disappearance of my prior Word Copilot chat history and personalization. If most of these changes are the result of a history or personalization issue, I hope they can be resolved as quickly as possible so I can continue using Copilot the way I did before. However, if the behavior I am seeing is the result of a permanent redesign of the Word Copilot experience, I will need to reconsider whether maintaining my Microsoft 365 Premium subscription continues to provide the value that originally led me to purchase it.
Agent Builder agents require Microsoft 365 Copilot license for users without a license?
Hi all, Has anyone noticed a recent change in how Copilot Agent Builder (in Copilot Chat) agents work for users without a Microsoft 365 Copilot license? Our setup is: Agent created by a user with a Microsoft 365 Copilot license Created directly in Agent Builder, not published through Copilot Studio The agent is published and available within our tenant Some consumers do not have a Microsoft 365 Copilot license Copilot Credits are available (also for the environment where the agent is) and have not been exhausted This setup was working normal ly just two days ago. Unlicensed users could use the shared agents and usage was covered by Copilot Credits. Now those same users are getting a message saying that a Microsoft 365 Copilot license is required. Has anyone else started seeing this? I’m trying to understand whether we are looking at a configuration issue in our tenant or whether something has recently changed in the service/licensing behavior. Thanks for experiences!
Please Remove Daily Cap Usage for Free Copilot Text Chat
Dear Microsoft Copilot Team, I am writing to express my disappointment with the new daily usage caps on Microsoft Copilot, particularly for ordinary text-based conversations. In the past, I could use Copilot freely for everyday questions, learning, research, brainstorming, and general conversations without constantly worrying about reaching a daily limit. The newer restrictions have made the experience significantly more frustrating and less useful. I understand that running AI services requires computing resources and that Microsoft must manage operating costs. However, I believe ordinary text chat should remain uncapped, especially when it was previously possible to use Copilot much more freely. Text conversations are a fundamental part of the service, and users should not have to stop in the middle of a useful discussion because they have exhausted a daily allowance. The move toward a unified Copilot experience should make the product simpler, more consistent, and more useful—not make existing users feel that they have lost access to a service they have come to rely on. I am therefore asking Microsoft to: Remove daily usage caps entirely for ordinary text-based Copilot conversations, including for free users. Keep basic text chat freely accessible without arbitrary daily cutoffs or lengthy waiting periods. If stricter limits are necessary for resource-intensive features such as image generation or advanced research, apply those limits separately rather than restricting ordinary text conversations. Clearly communicate any usage policies and reconsider changes that negatively affect the experience of long-time users. Unlimited text chat would help preserve user trust, encourage continued engagement, and distinguish Copilot as an accessible AI assistant for everyone. Restricting basic conversations risks pushing loyal users toward competing services that offer a more suitable experience. I hope Microsoft will take this feedback seriously and reconsider the current daily cap policy. Please restore uncapped text chat so users can rely on Copilot whenever they need assistance, without worrying about running out of messages. People on Reddit and online have been criticizing these changes ever since Copilot was unified under one product between enterprise and personal, If you guys dont do anything now it might reduce user trust and might be bad business decisions so please fix Copilot Thank you for your time and consideration. I look forward to seeing Microsoft make Copilot more accessible and user-friendly again.
Microsoft Copilot Desktop App: Work account login loops back – sign out of personal account to fix
If the Microsoft Copilot desktop app repeatedly redirects work-account sign-in to the browser and returns to “Sign in to Copilot”, check whether the browser is simultaneously signed into personal and work Microsoft accounts. Signing out of the personal account may allow the work-account desktop sign-in to complete. I used Copilot to try to investigate my problem with the Desktop App - it would provide a mechanism for me to sign in, but it did so by launching a browser window, whilst the App itself returned to the login screen. That wasn't what I wanted - I have too many browser tabs open already! Copilot went a long way down the networking/proxy route, and then by chance I discovered this very much simpler solution in an identity-session conflict. Symptoms: Copilot desktop app always loops back to showing “Sign in to Copilot” after completing the sign in. The Work authentication appears to be successful. The “Which Copilot experience are you looking for?” screen appears. Choosing the work experience opens copilot.cloud.microsoft in the browser. Desktop app remains signed out and loops back to "Sign in to Copilot". Cause: The browser was simultaneously signed into personal and work Microsoft accounts. Resolution: Signing out of the personal account allowed the desktop work-account login to succeed.
Microsoft 365 Family: Copilot cannot directly access OneDrive files
I am the primary subscriber on an active Microsoft 365 Family subscription. Copilot is unable to directly access or read files stored in the OneDrive associated with the same Microsoft account. I have reproduced this both in the Windows Copilot app and in Copilot on the web. When I ask Copilot to access a specific existing OneDrive folder, it reports that it does not have access to my OneDrive and cannot see or open the folder or files. Manual file attachment does work: if I manually attach a file from OneDrive, Copilot can read and summarise it. The problem is specifically with direct OneDrive access without manually attaching the file. Microsoft Support also investigated the issue remotely using Quick Assist. They confirmed that manual file attachment works, but direct OneDrive access does not. The support agent told me that this appeared to be a "design/feature issue with Copilot" and that it was beyond his support boundary, so he was unable to resolve it. He advised me to submit the issue through Feedback Hub and also raise it here in the Microsoft Community. I have submitted the issue through Feedback Hub. I'd really love to know if anyone using Microsoft 365 Family has experienced the same problem, or found a way to enable direct Copilot access to OneDrive for the primary subscriber. I would also be interested to know whether this is currently expected functionality for Microsoft 365 Family, or whether there are additional account, rollout, entitlement, or permission requirements that are not obvious from the product interface. Any relevant experience or wisdom would be very gratefully received.Microsoft 365 Copilot DLP – Inconsistent Enforcement Between PII, Financial and Technical SITs
Hi everyone, I'm looking to understand whether anyone else has experienced inconsistent DLP enforcement when using Sensitive Information Types (SITs) to prevent Microsoft 365 Copilot from processing sensitive information entered directly into Copilot Chat prompts. We've configured a Microsoft Purview DLP policy targeting the Microsoft 365 Copilot location, with the action Prevent Copilot from processing content – Processing prompts. The policy is configured to detect built-in Microsoft Sensitive Information Types and prevent Copilot from processing prompts containing matching information. However, during testing, we're observing inconsistent behaviour depending on the category of SIT being tested. All test data has been independently validated against the corresponding Microsoft Purview Sensitive Information Types, confirming successful detection at the configured confidence levels. Observed Behaviour: PII SITs: Copilot appears to process the information before responding that it cannot assist with the request. Financial SITs: Similar behaviour is observed, with Copilot appearing to recognise the sensitive information before declining to respond. Technical SITs: Copilot processes the information and provides a response without any apparent restriction, despite the information matching the technical SITs configured within the DLP policy. This raises concerns about whether the responses we're seeing for PII and financial information are actually the result of DLP enforcement or Copilot's own built-in safeguards. More importantly, technical SITs appear to be handled differently, with no apparent enforcement taking place. Questions: Has anyone successfully validated SIT-based prompt blocking in Microsoft 365 Copilot Chat, particularly using technical SITs? Are there any known differences in enforcement behaviour between PII, financial and technical SITs? Does Copilot apply additional built-in safeguards to PII and financial information independently of Microsoft Purview DLP policies? Are there any known limitations affecting technical SIT detection or enforcement within Copilot Chat? According to Microsoft 365 Roadmap ID 515945, the functionality for safeguarding Copilot prompts using SIT-based DLP policies is marked as launched and generally available. However, Microsoft's documentation continues to reference preview availability and rollout considerations. Any insight into whether this is expected behaviour, a known limitation or if I am just being silly at this point would be appreciated. Thanks in advance.
Copilot Premium License Not Being Recognized in Copilot Standalone App
I'm experiencing an issue where the standalone Copilot app is not recognizing my Copilot Premium license. I've already worked with Microsoft Support to troubleshoot the problem. During the session, we reset Copilot, confirmed that my web-based Copilot experience is correctly showing and using the Premium version, all other office 365 apps is using the Premium version as well, and performed several other troubleshooting steps. I've also uninstalled and reinstalled Microsoft 365 multiple times. Although the issue remains unresolved, the support representative was extremely helpful and assisted in thoroughly troubleshooting and isolating the problem. Based on our testing, it appears the issue is specific to the standalone Copilot app, as my Premium subscription functions correctly in the web version. Has anyone experienced this issue before, or can someone help identify a solution? Any assistance would be greatly appreciated. Thank you.
Long chats receive 504 gateway timeout in new copilot UI
I understand this has been an issue for a lot of people. I have read multiple posts across other platforms. The new copilot UI no longer uses pagination like the old one and attempts to call upon the entire chat at once for easy navigation scrolling all the way to the top or bottom. However, for chats like mine with months of worldbuilding and character notes accumulating 2000+ messages, it does not have enough time to load them all before reaching a gateway timeout. I want to ask if anyone knows of any fixes that may be coming for this in the future since it is a pretty big issue when it comes to user satisfaction. The same chat has several different error states. Sometimes it will say 'Unable to load content'. Sometimes it will have a stable but blank page. Sometimes it will go to a white screen with the Error 504 timeout. I have attached images of all the different failure states I have seen. Basic error on white screen version of the bug. It fails to load preview and response data in this state. A screenshot of the timing window to show where it is stalling. Sometimes it will show me this general unable to load content screen. Refreshing is what leads to the white screen errors shown above. Here is a screenshot of the stable-but-blank version that sometimes shows up. Note how it is offering autocompletes like it is my first time messaging this chat. And here is a screenshot of the inspect element of this stable but blank version of the long running chat. Can anyone explain to me why this chat is having so many different failure states and what they mean and if a fix is possibly being rolled out in the future for this? I'm really sad I lost such a long important chat with so much lore.
