Forum Widgets
Latest Discussions
Copilot Studio Knowledge Source Limitation When Iterating Over Multiple SharePoint Documents
Hi, I’m looking for clarification on a limitation we’re currently encountering in Copilot Studio that is blocking some of our use case. Example Scenario (Policy Agent) We have a SharePoint document library containing ~100 policy documents. A Copilot Studio agent is configured with this library as a knowledge source. The agent performs well for typical question-answering scenarios where responses can be derived from a subset of documents. For example: “How much annual leave can I take?” correctly returns answers sourced from multiple relevant policies. Issue When the question requires the agent to evaluate all documents individually, the results are incomplete. Example prompt: “Review each policy document and return the review date.” In this scenario: The agent only processes the first ~10 documents. It then stops, without indicating that the response is partial or that a limit has been reached. The remaining documents in the library are not evaluated. During a recent Microsoft-led course, we were advised that this behaviour is expected due to platform limitations. Specifically: While it will reside over all documents to genereate the most suitable response, the agent is not designed to self‑iterate across all items in a large knowledge source for individual document responses. Asking it to “review each document” effectively requires iteration, which is constrained. The suggested workaround was to: Create a trigger-based flow Implement a loop to process the documents in batches We were able to make this approach work, but it feels like a heavy and brittle workaround for what seems like a common enterprise requirement. We’ve Tried Both available SharePoint knowledge source connection methods Allowing sufficient time for indexing and refresh Rephrasing prompts to encourage broader coverage None of these approaches changed the outcome, the agent consistently returns results for only the first subset of documents. Is this behaviour a documented or known limitation of Copilot Studio knowledge sources? Are there recommended design patterns for scenarios that require document-by-document evaluation at scale? Is there a more native or supported approach planned to avoid custom looping logic for this kind of use case? Any guidance or confirmation would be appreciated. Thanks.
Cannot access admin.microsoft.com – need Global Admin role assignment
Buongiorno, ho acquistato una licenza Microsoft 365 Premium, ma il mio account non risulta amministratore del tenant. Non posso accedere al portale https://admin.microsoft.com/?utm_source=copilot.com (errore: “non hai accesso”) e non ho alcun altro account amministratore disponibile. Ho necessità di diventare Global Administrator del tenant per abilitare funzionalità avanzate come Copilot Studio. Il supporto Microsoft mi ha indirizzato qui per avviare la procedura di verifica e recupero del ruolo amministrativo del tenant (“tenant admin recovery”). Chiedo assistenza per: identificare il tenant associato alla mia licenza, verificare l’assenza di un amministratore globale, assegnare il ruolo Global Admin al mio account. Grazie per il supporto. Cordiali saluti,📣 Microsoft Copilot Studio and Agent Roadmaps Have a New Home
Microsoft Copilot Studio and Agent Roadmaps Have a New Home Starting July 2, 2026, feature updates for Microsoft Copilot Studio, Sales Agent, Finance Agent, and Service Agent, will be published on the Microsoft 365 Roadmap. This creates a single destination to discover what capabilities are coming next across Microsoft 365 core apps, Copilot, agents, and more. As part of this transition, Release Planner will no longer be a source for feature information for these products. Future updates will be available through the Microsoft 365 Roadmap, making it easier to stay informed, plan ahead, and leverage AI-powered experiences that can discover and consume information more effectively. What you need to know No immediate action is required Update any saved Release Planner bookmarks to the Microsoft 365 Roadmap Begin using the Microsoft 365 Roadmap as your primary source for feature updates Share this change with stakeholders who currently rely on Release Planner Resources: Stay up to date on what’s new and what’s next: Microsoft 365 Roadmap Microsoft 365 Copilot release notes Microsoft 365 Copilot Roadmap Webinar - Register today Get started with AI-powered change insights: Microsoft MCP Server for Enterprise - Gives MCP-compatible AI tools secure, read-only access to your organization’s Message Center and Service Health data, enabling personalized summaries, impact analysis, and stakeholder communications based on your existing permissions and security controls. Microsoft Release Communications MCP Server - Provides free, natural-language access to official Microsoft 365 Roadmap and Azure Updates information, enabling AI agents to answer questions about upcoming features, rollout timelines, and product changes. We're excited to bring roadmap information together in one place to deliver a more consistent, accessible, and AI-ready experience for planning what's next.
Copilot Studio + SharePoint: Markdown (.md) Files in Doc Libraries Supported as Knowledge Sources?
Hi all, We’ve been doing some deeper testing with Copilot Studio agents grounded in SharePoint knowledge sources, and I’m hoping to clarify whether what we’re seeing is a known limitation or an undocumented gap. Scenario A Copilot Studio agent uses SharePoint document libraries as a knowledge source The library contains Markdown (.md) files that are intentionally used as canonical design references The same .md files: ✅ Work well when uploaded directly to the agent ❌ Are not retrievable or citable when stored in a SharePoint library and added as a SharePoint knowledge source To help with grounding, we created modern SharePoint index pages that: Explain what the markdown collections are (Patterns, ADRs, Guardrails) Link directly to the canonical folders and files Explicitly state that the .md files are the source of truth The agent can: Discover and summarize the index pages correctly Understand that .md artifacts exist and where they live But it cannot: Read the content of the individual .md files Apply a specific pattern or ADR from those files in a design conversation Cite them as sources, even when permissions and search indexing are confirmed What We’ve Checked Permissions (agent user has access) Folder depth (kept shallow) Search results (markdown files appear in SharePoint search) SharePoint indexing status Work IQ enabled Same content works when attached directly to the agent This behavior also seems consistent with what others have reported here: Markdown works when uploaded directly Markdown retrieval degrades when hosted in SharePoint libraries Questions for the Product Team / Community Are Markdown (.md) files in SharePoint document libraries officially supported as Copilot Studio knowledge sources today? If yes, are there specific constraints (file size, rendering, parsing, indexing) that differ from Word/PDF? If no (or “not yet”), is this a known limitation on the roadmap? Is the recommended pattern to: Convert important markdown files into .aspx pages, or Use thin “index / summary” pages and keep markdown canonical until retrieval improves? We’re happy to adapt our information architecture — just trying to align with the intended platform direction rather than work against it. Thanks in advance for any guidance or clarification. This capability is extremely powerful, and clearer expectations here would help a lot of teams make the right design tradeoffs.Welcome let's get started
Welcome to the Copilot Studio Community on Microsoft Tech Community! We're thrilled to announce that Copilot Studio now has a dedicated home on the Microsoft Tech Community, and we'd love for you to be part of it from day one. Whether you're just getting started with building Agents in Agent Builder or you are a pro building agents and automations with Copilot Studio, this is your space to: Ask questions and get answers from the community and Microsoft experts Share what you've built — show off your agents, flows, and use cases Stay up to date on the latest features, releases, and best practices Connect with peers across industries who are shaping the future of AI-powered work The community is open to everyone, from first-time explorers to seasoned pros. Every question asked and every insight shared makes this a better resource for all of us. We can't wait to see what you build. Welcome!
SystemError in Teams Group Chat for Copilot Studio Agent
Hi, I'm seeing what appears to be a Teams group chat issue with a Copilot Studio agent created using the new Copilot Studio UI. Scenario: - Agent is published and available in Teams. - Other users can chat with the agent successfully in 1:1 conversations. - The agent does not use SharePoint knowledge, authenticated knowledge sources, or external actions/connectors. - The agent works correctly for me in a Teams group chat. - However, when other participants in the same group chat mention or interact with the agent, they receive: "Sorry, an unexpected error occurred. Reference code: MCS-4041 Error code: SystemError" Additional details: - The agent was created recently using the new Copilot Studio experience, so this does not appear to be related to an older migrated bot. Has anyone experienced the same MCS-4041 / SystemError behavior in Teams group chats? Is this a known issue, limitation, or registration/caching bug between Copilot Studio and Teams? Thanks!Archivos bloqueados por Copilot al usarlos como fuentes en OneDrive personal
Hola comunidad, Quisiera compartir un problema que he estado enfrentando al trabajar con Copilot y documentos almacenados en mi OneDrive personal. Al intentar usar ciertos archivos como fuentes para proyectos, Copilot muestra el mensaje “The document is blocked by its content”, impidiendo que el archivo sea procesado. Los documentos afectados incluyen: Proyecto Educativo Institucional (PEI) Reglamento Interno Escolar Plan Anual de Gestión Otros documentos PDF y Excel con contenido normativo o institucional Aunque los archivos fueron creados por mí como persona natural y están en OneDrive personal, Copilot los clasifica como contenido altamente sensible, probablemente debido a: Lenguaje normativo o jurídico Estructura de reglamentos y protocolos Información institucional o disciplinaria Palabras clave asociadas a documentación oficial Formatos PDF/Excel con tablas, artículos o indicadores Entiendo que Copilot aplica filtros de seguridad para evitar procesar documentos que puedan contener información crítica o normativa, pero en este caso se trata de archivos destinados a publicación pública en la web de la escuela. Me gustaría saber: Si existe una forma de marcar estos documentos como seguros desde OneDrive personal. Si hay configuraciones específicas que permitan a Copilot procesar documentos normativos creados por el usuario. Si otros usuarios han enfrentado este tipo de bloqueo con contenido institucional no confidencial. Agradezco cualquier orientación o experiencia que puedan compartir. Saludos, Alex
You don't have access to talk to this bot, contact the owner. copilot studio
I created a copilot studio agent and then embedded it inside a code app. It works fine but i am facing the below error. You don't have access to talk to this bot, contact the owner. copilot studio I have provided Microsoft based authentication and am an owner so will have access to the bot. Yet facing the above issue. Is there something i am missing
Copilot agent sending emails to incomplete tasks
Hi Folks, I am new to this forum but want to share an interesting thing which I did with my first copilot agent. I have built an agent which can read incomplete number of "time-reported hours" from timesheet report and send individual emails to all those with "missing hours" in the body of email. This acts as a reminder for all the folks who missed filling their timesheets. The agent has worked well so far.
