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!Performance Optimization Tips for Microsoft 365 Agents
A Microsoft 365 agent can answer questions, summarize documents, retrieve business information, and automate everyday tasks. But when responses take too long, integrations fail, or answers become inconsistent under load, users quickly lose confidence in the experience. link to the post
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.Real-world use case: how a sales team runs every account from a Copilot Notebook (2-min video)
Hi everyone, I'm a PM on the Copilot Notebooks team at Microsoft. A pattern we see with enterprise sales teams: one notebook per customer, with CRM notes, decks, workshop notes and emails added as references; the whole account team working from the same context; and customer meetings recorded with Capture in OneNote, so the notes and actions go straight back into the notebook. We turned one of these workflows into a two-minute story: https://youtu.be/Al2VddNfC-o The story and companies are fictional (inspired by real workflows), some features may be in preview, and the illustrations and narration were made with AI tools. For those rolling out Copilot in your organizations: How are your teams setting up notebooks: per customer, per project or per team? What has helped adoption, and what's getting in the way? Getting started with Copilot Notebooks: https://support.microsoft.com/en-us/microsoft-365-copilot/get-started-with-microsoft-365-copilot-notebooksFix all annoying Copilot bugs
I’m experiencing an issue with Microsoft Edge on Android. Starting today (September 22, 2026), whenever I try to visit copilot.microsoft.com, Edge automatically redirects me to the Google Play Store to install the Copilot app. I prefer using Copilot in the browser and do not want to install the app. And even when i try to install the copilot app it does not let me do anything and thinks I need a license or subscription to access it like copilot is litterly supposed to be free and also even when i try to get rid of the app redirection it for some dumb reason it redirects me to from copilot.microsoft.com to copilot.com and they put in restrictions like after a lot of chats you must wait for a specific time period and a couple months ago you guys removed the ability to use copilot without registration like come on that is so dumb I want Microsoft Copilot to be fixed revert how copilot was before how is this consumer friendly🚀 It's a bird! It's a plane! It's HTML! -No workarounds
Or maybe it's SharePoint... 🤔 - Now Available - Frontier tenants !!!! For years, bringing HTML pages into SharePoint usually meant dealing with iframes, extra scrollbars, broken navigation, or custom solutions that never felt quite right. Now we finally have a much cleaner experience. You can upload existing HTML pages or create entirely new ones, while still keeping the familiar SharePoint header, navigation, and overall site experience. What I like most is that users stay in SharePoint. No awkward embedded pages. No jumping between different experiences. Just a modern web page that feels like part of the site. 🎥 I have created a video is a MUST for any Sharepoint Experts https://www.youtube.com/watch?v=_0JphDIUwTI I'll show you: ✅ Where to upload existing HTML pages ✅ How to create brand-new HTML pages ✅ How to edit and update them ✅ How to keep the SharePoint menus and headers ✅ How to avoid iframes and those annoying double scrollbars ✅ How to enable upload HTML is Site Pages As someone who has worked with SharePoint for many years, this feels like one of those features that should have existed a long time ago. Take a look at the video and let me know what you would build first with HTML in SharePoint.
Troubleshooting Microsoft 365 Agent Builder
A Microsoft 365 Agent Builder agent can look perfectly configured and still fail when a real user tries it. The symptoms are often deceptively simple: the agent returns poor answers, ignores a SharePoint document, refuses to share, fails to publish, or works for the author but not for everyone else. Link to the postHow to Reduce AI Hallucinations in Microsoft 365 Agents
An AI agent can produce a polished, confident answer and still get the underlying fact wrong. In a Microsoft 365 environment, that can mean inventing a policy requirement, citing an outdated procedure, misreading a project document, or answering a question that should have triggered a search of enterprise data. Link to the post
Copilot Agent not consistently Respecting SharePoint Document Permission
Hi everyone, I have created a Copilot agent that answers questions based on documents stored in SharePoint, and I want the agent to respect the user's SharePoint permissions. For example: I have two documents: Document A and Document B. User A has access to Document A but does not have access to Document B. When User A asks a question related to Document A, the agent should provide an answer. When User A asks a question related to Document B, the agent should not provide any information because User A does not have permission to access that document in SharePoint. However, I am experiencing inconsistent behavior. Sometimes the Copilot agent correctly respects the SharePoint permissions, but at other times it provides an answer from a document that the user does not have access to in SharePoint. In some cases, even users who do have access to a document do not receive an answer from it. I am using Microsoft authentication and SharePoint as the knowledge source. Has anyone experienced this issue with Copilot Studio and SharePoint security trimming? Could this be related to indexing, caching, authentication, permissions propagation, or the way the agent retrieves documents? I would appreciate any guidance on how to ensure that the Copilot agent consistently respects the user's SharePoint permissions when retrieving and answering from documents.
