copilot in teams
75 TopicsWork IQ or individual M365 tools for a company-wide agent: cost vs. future-proofing?
I'm Head of Project Management at Contica, a Swedish integration consultancy. I've built a task organizer agent in Copilot Studio that reads my Outlook, Teams chats and calendar, finds real commitments (things I promised, questions waiting for my answer) and organizes them in Microsoft To Do. It works well for me, and colleagues are asking for it. Before a broader rollout I'm stuck on an architecture choice. One run consumes roughly 300-400 Copilot Credits, about 3.5 USD at pay-as-you-go rates. Run daily, that’s around 70 USD per user per month. Here's how I understand the billing from the docs: - Work IQ runs on the Microsoft Copilot harness and is billed in Copilot Credits, including for users with an M365 Copilot license when it's used in a custom agent. - The workload-specific tools (Mail, Teams, Calendar etc.) run on the standard harness. For a standalone Copilot Studio agent in Teams, usage by M365 Copilot licensed users isn't billed. - But Microsoft describes those tools as legacy, kept for testing and backward compatibility, and recommends not choosing them over Work IQ. So the trade-off as I see it: 1. Stay on Work IQ: simpler and future-proof, but every run costs credits for every user. 2. Rebuild with the individual tools: potentially much cheaper for licensed users and more control over exactly what's read, but built on something Microsoft calls legacy. My questions: 1. Has anyone made this choice for a broad rollout? Which way did you go, and why? 2. What has worked for bringing Work IQ cost down - fewer workloads, narrower time windows, reading metadata first? 3. Have I got the billing model right? The licensing pages aren't the easiest read. Thanks!48Views0likes2CommentsMicrosoft Ignite "Book of News"
Since Microsoft is not going to create a "Book of News" for Ignite this year, and since things are changing so rapidly in the Microsoft Copilot sets of solutions (e.g., the old M365 Copilot, now 'Microsoft Copilot'; Copilot Code; Copilot Cowork, the countless Power Platform changes related to the management, governance, and security of Copilot AI solutions, etc.), how about we as a community join together to put together what Microsoft will not?365Views0likes0CommentsPlease 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.636Views6likes2CommentsFix 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 friendly503Views1like2CommentsCopilot 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.137Views0likes0CommentsCopilot Access not working for only 1 user
Hello, I am facing an issue where I have 1 user that is unable to get answers out of the chatbot on teams. The user is opening the chatbot using the 'open with copilot' option like the rest of the team members, but when they ask a questions, the chatbot returns that it has not found information on the topic, even when the information is in the training documents the chatbot reads off of. Other users can ask the same questions and get valid answers, it is only not working for this specific user. Any suggestions on how to resolve this?379Views0likes1CommentAccess to Office App Context and Setting CEA as Default in Microsoft 365 Copilot
Hello everyone, I’m exploring Custom Engine Agents (CEA) in Microsoft 365 Copilot and have two questions regarding their integration with Microsoft 365 applications. Can a Custom Engine Agent access the current Office application context? When a CEA is added to Microsoft 365 Copilot, is there a supported way for the CEA to access the content of the Microsoft 365 application where Copilot is currently being used? For example: Word: Can the CEA read and/or modify the document currently open in Word? Outlook: Can the CEA access the current email/thread and perform write operations such as drafting or modifying content? PowerPoint: Can the CEA access and modify the presentation currently open? Other Microsoft 365 applications: Are similar capabilities available in other applications where Microsoft 365 Copilot is supported? Essentially, I’m trying to understand whether a Custom Engine Agent can leverage the same application context and read/write capabilities that the native Microsoft 365 Copilot has within these applications. If this is supported, what APIs, SDKs, or integration patterns should be used? Can a Custom Engine Agent be configured as the default mode? Is there a supported way to: Disable or bypass the default Microsoft 365 Copilot experience/mode, and Configure a Custom Engine Agent as the default agent/mode that users interact with when they open Copilot? For example, if an organization has a custom agent that should handle the majority of Copilot interactions, can that agent be configured as the default instead of the standard Microsoft 365 Copilot? I’d appreciate any clarification on the current capabilities, limitations, and recommended architecture for these scenarios. Thanks177Views0likes0Comments