copilot studio
21 TopicsArchivos 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, Alex9Views0likes1Comment📣 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.159Views1like2CommentsFile Uploads Not Passed to Custom Engine Agent in Microsoft 365 Copilot Chat
Hi all, I'm working with a custom agent built in Copilot Studio (full authoring experience — topics, knowledge sources, agent flows) published to both the Microsoft Teams channel and the Microsoft 365 channel. I've noticed a significant UX discrepancy when it comes to file and image attachments, and I want to confirm my understanding and check whether any workaround or roadmap item exists. What works: ✅ File/image uploads work as expected in the Copilot Studio test pane ✅ File/image uploads work in Teams chat when interacting with the agent What doesn't work: ❌ File/image uploads do not reach the agent when interacting via the Microsoft 365 Copilot app (both the desktop app and the web experience at microsoft365.com) The UX problem: The M365 Copilot app presents a "+" button in the chat input area with options including "Upload" and "Take screenshot." Users naturally assume these options work. The file even appears as an attachment in the sent message — but the agent never receives it. There's no warning, error, or indication to the user that the attachment was silently dropped. This creates a misleading experience, particularly for end users who have no visibility into the channel behavior differences. What I've found so far: I'm aware this is documented as a known issue for custom engine agents in the Microsoft 365 Copilot Extensibility Known Issues page: "File attachments — Users can't upload files in agent chats and the agent can't return files for download." I also found a related GitHub issue (OfficeDev/microsoft-365-agents-toolkit #15325) where a Microsoft team member confirmed this is a "Copilot platform shortage" — not an Agents Toolkit issue — with no published ETA. My questions for the community and any Microsoft product team members: Is there any currently supported workaround to enable file/image input for a Copilot Studio agent running in the M365 Copilot app (desktop or web)? For example, any manifest configuration, agent settings, or alternate approach? Is this limitation being actively worked on? Is there a roadmap item or Microsoft 365 feature ID that can be tracked for when file attachment support is extended to custom engine agents in the M365 Copilot chat experience? Is the UI behavior (showing upload options that don't work) being addressed separately? Even if full file processing isn't ready, a visible warning or disabled state in the UI would significantly reduce user confusion. Any insight from others who have hit this — or from Microsoft PMs — is appreciated. Happy to share more configuration details if helpful. Thanks! Brian385Views3likes1CommentCannot 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,38Views0likes3CommentsYou 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 missing92Views0likes2CommentsNew workflow designer accessing environment variables
Hi, I really enjoy using the new workflow designer. I've a triggered workflow (Email arrives) that I added into a solution. I'd like to use environment variables from within the workflow. The variables and the workflow are in the same solution. Unfortunatly the environment variables are not visible like they were in the old designer. How can I access them ? Thanks in advance48Views0likes1CommentCopilot 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.44Views1like1CommentThe Employee Self-Service agent - how to find it
I see that Microsoft has put a lot of efforts to marketing the Copilot Employee Self-Service Agent but it seems it is not available for every tenant. I have already checked on several small and mid ones (5-2k users) and cannot find it in templates. As I understand from what I already red and saw, this is a template that should be available to you when you start building agents. Unfortunately when I enter Copilot Studio and enter in the search ESS (abbreviation from Employee Self-Service) I got only those two agents marked red filtered (see screenshot below). When I installed IT Helpdesk agent, I do not see topics related to HRSD in ServiceNow which I need. I found the Employee-Self-Service-Agent-Developer-Kit that contains same examples of the ServiceNow HRSD topics, but when I copy the YAML code of those topics to my agent I got some references to topics that I do not exists in my agents. Anyone has struggled with the same? Or maybe you have access to the Employee Self-Service agent and can share the basic solution/topics with me? Michal131Views0likes2CommentsCopilot Studio agent not visible in M365 mobile app without desktop access
Hi, I'm having an issue with a Copilot Studio agent not being discoverable in the Microsoft 365 mobile app for users without desktop access. **Setup:** - Agent created in Copilot Studio, published and shared with specific users - All users have the same Microsoft 365 Copilot license - Target channel is the Microsoft 365 app (not Teams) - The agent has been published to both the Teams and Microsoft 365 channels in Copilot Studio **The problem:** Users who have access to a desktop/browser can open the agent via a direct link, add it, and after that it appears correctly in the M365 mobile app. However, users who only have access to the M365 mobile app cannot find the agent there — even though it has been shared with them. **What I've tried:** - Verified the agent is published and shared directly with the affected users in Copilot Studio - Confirmed all users have the same license - Published the agent to both Teams and Microsoft 365 channels - Sending a direct link to the agent — works on desktop/browser but not actionable in the mobile app in a way that adds the agent - Logging out and back in to the M365 mobile app **What I'm looking for:** Is there a way for users to discover and add a shared Copilot Studio agent directly from the M365 mobile app, without needing desktop or browser access first? Any help or workarounds are appreciated!Solved172Views0likes4CommentsCopilot studio Agents published on Sharepoint
Hi everyone, I'm hoping someone can confirm or correct my understanding of a limitation we're experiencing. We have a Copilot Studio agent published to a SharePoint site. When users interact with the agent, they are unable to see their previous chat history — unlike the built-in SharePoint AI agents (e.g. SharePoint Agents / Copilot for SharePoint), which do appear to retain and display conversation history. Is it correct that Copilot Studio agents published to SharePoint do NOT support persistent chat history visible to the end user, while native/built-in SharePoint AI agents do support this out of the box?73Views0likes1Comment