SharePoint 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?Power 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-ea9141908346Microsoft 365 & Power Platform Community call
💡 Microsoft 365 & Power Platform Development bi-weekly community call focuses on different use cases and features within the Microsoft 365 and Power Platform - across Microsoft 365 Copilot, Copilot Studio, SharePoint, Power Apps and more. 👏 Looking to catch up on the latest news and updates, including cool community demos, this call is for you! 📅 On 23rd of April we'll have following agenda: Copilot prompt of the week CommunityDays.org update Microsoft 365 Maturity model Latest on PnP Framework and Core SDK extension Latest on PnP PowerShell Latest on script samples Latest Copilot pro dev samples Latest on Power Platform samples Picture time with the Together Mode! Carl Cookson (LinkeD365) – An Intro to the Power Platform ToolBox Ritu Hooda (First Bank & Trust) – AI‑Powered Azure DevOps Work Items with Power Automate Franck Cornu (PWC Canada) – Build a multi-agent system using Microsoft Foundry Agent Service, Microsoft 365 Copilot, Microsoft 365 Agents SDK, and MCP server 📅 Download recurrent invite from https://aka.ms/community/m365-powerplat-dev-call-invite 📞 & 📺 Join the Microsoft Teams meeting live at https://aka.ms/community/m365-powerplat-dev-call-join 👋 See you in the call! 💡 Building something cool for Microsoft 365 or Power Platform (Copilot, SharePoint, Power Apps, etc)? We are always looking for presenters - Volunteer for a community call demo at https://aka.ms/community/request/demo 📖 Resources: Previous community call recordings and demos from the Microsoft Community Learning YouTube channel at https://aka.ms/community/youtube Microsoft 365 & Power Platform samples from Microsoft and community - https://aka.ms/community/samples Microsoft 365 & Power Platform community details - https://aka.ms/community/home 🧡 Sharing is caring!Microsoft 365 & Power Platform product updates call
💡Microsoft 365 & Power Platform product updates call concentrates on the different use cases and features within the Microsoft 365 and in Power Platform. Call includes topics like Microsoft 365 Copilot, Copilot Studio, Microsoft Teams, Power Platform, Microsoft Graph, Microsoft Viva, Microsoft Search, Microsoft Lists, SharePoint, Power Automate, Power Apps and more. 👏 Weekly Tuesday call is for all community members to see Microsoft PMs, engineering and Cloud Advocates showcasing the art of possible with Microsoft 365 and Power Platform. 📅 On the 21st of April we'll have following agenda: News and updates from Microsoft Together mode group photo Paolo Pialorsi – Connected Declarative Agents for Microsoft 365 Copilot Sébastien Levert – Copilot Chat declarative agents - publishing, governance & real-world patterns Vesa Juvonen – Introduction to SPFx CLI for scaffolding your SPFx solutions 📞 & 📺 Join the Microsoft Teams meeting live at https://aka.ms/community/ms-speakers-call-join 🗓️ Download recurrent invite for this weekly call from https://aka.ms/community/ms-speakers-call-invite 👋 See you in the call! 💡 Building something cool for Microsoft 365 or Power Platform (Copilot, SharePoint, Power Apps, etc)? We are always looking for presenters - Volunteer for a community call demo at https://aka.ms/community/request/demo 📖 Resources: Previous community call recordings and demos from the Microsoft Community Learning YouTube channel at https://aka.ms/community/youtube Microsoft 365 & Power Platform samples from Microsoft and community - https://aka.ms/community/samples Microsoft 365 & Power Platform community details - https://aka.ms/community/home 🧡 Sharing is caring!
Suggestion: 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.
