Cowork Not Allowing Extensive Usage
As a part of the Copilot app updates, Tasks is becoming Cowork (https://support.microsoft.com/en-us/microsoft-365-copilot/learning/changes-microsoft-copilot-app). This support page (https://support.microsoft.com/en-us/microsoft-365-copilot/ai-credits-and-limits-for-microsoft-365-subscriptions) states that my subscription level includes "Extensive usage" for Cowork. I have been using Tasks seemingly without limit since that feature was introduced. I recently began to familiarize myself with the new Cowork, and in only a few hours of exploring how it worked, I ended up with a message that I had "reached your monthly Cowork limit". At the beginning of the day on October 9 I had never used Cowork, and at the end of the day I was told to wait until November 1 to use it again.
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!
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.
COPILOT DENIES ACCESS IN BETA VERSION
Hello, I am a Microsoft 365 Insider on the Beta Channel. I recently gained access to the multi-model preview features (Grok and Fable) in Word. While Word was open, my VPN accidentally connected to a restricted region (Russia). Shortly afterward, I was blocked from accessing Copilot and received the following error: "Copilot n’est pas disponible dans votre région." I have since permanently disabled the VPN and returned to my regular home network. However, whenever I rejoin the Beta Channel, the regional restriction immediately returns. I have already tried performing a clean installation of Office, verifying my Windows region settings, and resetting my privacy settings. Unfortunately, none of these steps has resolved the issue. Could this restriction be associated with an account-level setting or a server-side regional eligibility check? If so, is there an official troubleshooting procedure or a Microsoft support team that can review my account's eligibility and help restore access to the preview features? I would appreciate any guidance on how to resolve this issue. Thank you!ر
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.#7110313362 Regressão na integração do Copilot Pages após atualização de 13/10/2026
Gostaria de registrar atualizações e detalhes técnicos sobre o caso número 7110313362. Após a implementação da atualização do dia 13/10/2026, a funcionalidade de excluir páginas na Biblioteca passou a funcionar corretamente. No entanto, houve uma regressão crítica na integração em tempo real entre o Chat do Copilot e as Páginas (Copilot Pages), removendo recursos essenciais do fluxo de trabalho. Estou enfrentando os seguintes bugs simultâneos: 1. Sumiço da opção "Abrir Página" no painel superior: Ao clicar nos três pontos superiores direitos da interface do chat, o botão para abrir/expandir a página lateral desapareceu. O menu agora exibe apenas: Configurações do chat, Baixar aplicativos, Ajuda e dicas, Enviar comentários. 2. Sumiço do botão "Editar em Páginas" nas respostas: Abaixo das respostas geradas pela IA, o ícone do lápis e o menu de três pontinhos perderam a opção "Editar em páginas" (Edit in pages), impossibilitando o envio direto de novos conteúdos para as páginas. 3. Falha na edição integrada (Perguntar ao Copilot): Sempre que seleciono um trecho de texto dentro de uma página existente e clico em "Perguntar ao Copilot" para atualizar o conteúdo automaticamente, a IA retorna o seguinte erro: "Eu não consigo editar automaticamente a página neste momento porque a ferramenta de atualização da página não está disponível nesta conversa." Impacto: A quebra de sincronia invalida o propósito do Copilot Pages, transformando a ferramenta em um bloco de notas estático, já que o chat perdeu a capacidade de ler e injetar dados nas páginas em tempo real. Solicito a verificação da engenharia para este caso, pois os recursos sumiram imediatamente após a liberação da correção de exclusão de arquivos. Obrigado(a) e fico no aguardo de um retorno neste chamado. ANTES FICAVA ASSIM AO ABRIR UMA PÁGINA DURANTE CONVERSA NO CHAT AGORA NÃO TEM MAIS AS OPÇÕES DE ABRIR PÁGINA TAMBÉM SUMIU A OPÇÃO DE ADICIONAR EM UMA PÁGINA EXISTENTE
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.
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.Unable To Check Status of AI Limits & Credits
I am a Microsoft 365 Premium subscriber. This support page (https://support.microsoft.com/en-us/microsoft-365-copilot/ai-credits-and-limits-for-microsoft-365-subscriptions) states "You can check the status of your limits and AI credits by selecting Services & subscriptions in your Microsoft account." However, there is no information about limits or credits listed for my account or subscription. I've had two support chats (#7110092832 and #7110147952) about this over the weekend that lasted 2 HOURS. The technicians were not able to figure out why the information wasn't available for my account. They also were not able to tell me any more details about my limits, credits, or usage. The first chat ended by telling me to just try again in 24 hours, and the second ended by directing me to look for help in this forum. Where can I see my limits and used/remaining credits?
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.
