microsoft 365 copilot
451 TopicsCowork (Frontier) OneDrive/SharePoint document read errors
We've recently managed to start using the Cowork (Frontier) agent in M365 Copilot and some of the fantastic capabilities it provides. We're seeing an issue where right now the agent it failing to read data from withing documents such as Word documents in SharePoint and OneDrive. We see errors in the detail such as "ReadFileContent tool keeps failing with auth expired" and "Auth expired. Let me retry - the system should have refreshed the token.". Other agents appear to be able to access SharePoint/OneDrive content without error and people trying to access those documents definitely have full permissions (their own OneDrive as an example). Works when files are manually attached to the prompt. We've enabled model sub-processing which is the only dependency I can see for Cowork. Wondering if a widespread known issue or something specific to my environment?Solved105Views3likes2CommentsCowork can't send emails?
Hi, all. I've been playing around with Copilot Cowork and really loving it, but with one problem. When it tries to send an email to anyone but myself, it can't. It tells me to approve, but I never get the approval prompt. I get errors like this: "Good question. The approval step typically appears as a confirmation dialog right here in our conversation before an email is sent. It worked fine for the test email to your own address, but when I tried sending to [otherperson], the system blocked it before the approval dialog could reach you" and "The platform is blocking the send to an external recipient and the approval dialog isn't surfacing properly." and "All three return the same error: the platform requires an approval step before executing any outbound send action, but that approval dialog isn't rendering in your session. The test email to yourself worked because self-sends appear to be auto-approved. This is a platform-level issue — not something I can fix from my side." Any thoughts? I'm not even sure where to start troubleshooting this.Solved79Views0likes4CommentsSharePoint lists with Copilot Studio error
I’m seeing a persistent issue when integrating SharePoint lists with Copilot Studio agents. Any SharePoint list I add to an agent results in an error being shown in the Copilot Studio UI, but no error message, diagnostic detail, or failure reason is surfaced. I’ve removed and re-added the list connections multiple times and reproduced the issue across multiple agents, with the same outcome each time. Has anyone encountered this behaviour, or are there known issues or prerequisites (e.g. permissions, connector state, tenant configuration, or recent service changes) that could cause silent failures when integrating SharePoint lists?44Views0likes1CommentPower Apps Vibe + Copilot: Are we moving from coding to just describing apps?
With the new Power Apps Vibe experience, Copilot is making app development feel very different. What used to take hours - planning, data modeling, and UI setup - can now start with just a simple prompt. I recently tried building a non-profit management app, and Copilot generated the full structure (data, roles, UI) in minutes. From there, I refined everything using natural language. It really feels like we’re moving from building apps to describing ideas, and Copilot is doing a lot of the heavy lifting. Curious to hear your thoughts: Is this the future of app development? Or mainly a powerful prototyping tool? I shared a quick walkthrough here if you’re interested: https://medium.com/@sajeda27/power-apps-vibe-coding-build-an-app-from-an-idea-in-minutes-ea914190834621Views0likes0CommentsSuggestion: Allow users to customize the UI name of MS Copilot (with “Powered by Microsoft 365”)
Background Microsoft Copilot is an extremely capable assistant, but its current visual identity is completely fixed (the name “Copilot” is always shown), even though users interact with it daily as a personal or team assistant. From a user experience perspective, this creates a small but important gap between using a tool and working with an assistant. Proposal Allow users to customize the visible name of their Copilot assistant, while maintaining a clear and consistent Microsoft branding indicator, for example: Holiday (name that the user creates for calling Microsoft Copilot 365 IA) Powered by Microsoft 365 Copilot (Text that Microsoft uses to reflect that it's already Microsoft Copilot). This proposal does not aim to change the underlying model, security, governance, or responsibility. It only affects the identity/presentation layer of the assistant. Why this matters (UX & adoption) Allowing users to name their assistant creates: Psychological ownership (“my assistant” instead of “the assistant”) Higher trust and willingness to delegate complex tasks Stronger long-term adoption and recurring usage In daily work, users naturally refer to assistants by name (“Ask Friday to review this document”), which helps integrate Copilot into real workflows instead of keeping it as an external tool. Enterprise perspective In organizational environments, a named assistant feels like part of the team rather than a generic external service. This improves internal communication, clarity, and acceptance of AI-assisted workflows. Importantly, the “Powered by Microsoft 365 Copilot” label keeps: brand visibility transparency technical and legal responsibility clearly with Microsoft This follows well-established patterns such as “Powered by Azure” or “Powered by Microsoft Security”. Strategic fit Microsoft already enables named and branded assistants through Copilot Studio. Extending this concept to the core Copilot experience feels like a natural next step with: Low technical risk (presentation-level feature) High UX impact No compromise on governance or brand integrity Closing Naming the assistant transforms the relationship from using AI to collaborating with AI. This small change could have a disproportionally positive effect on trust, adoption, and everyday productivity. Thanks for considering this feedback.49Views0likes3CommentsWelcome 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!76Views1like1Comment