Forum Widgets
Latest Discussions
Is "uncertainty" the feedback signal Copilot Studio agents are actually missing?
At today's M365 Platform Weekly session, we were asked for our input on what feedback we wish we could pull beyond thumbs up/down and verbatims. Is it trends over time, sentiment themes, the response-to-triage loop, etc. Here's an angle: What if the primitive itself is wrong? Thumbs up/down measures satisfaction after the fact. What if we measured confidence instead? How often an agent actually knows it's on shaky ground, and whether the user's reaction matches that? If an agent flags its own uncertainty at the point of response instead of a static thumbs up/down, a feedback prompt gets generated from whatever's trending in that uncertainty instead of the same generic question every time, and "trends over time" becomes "did this agent get more confident or less confident since the last update" rather than a flat satisfaction line. It might also solve the silence problem that most users rarely click anything. A reaction that's actually specific ("you caught something the agent flagged as shaky") seems easier to engage with than a binary good or bad. To be clear, confidence signals already exist in adjacent forms. Copilot Studio and most conversational AI platforms already use a confidence score internally to decide whether to answer directly, ask a clarifying question, or escalate to a human. GitHub Copilot has used a confidence score since its earliest versions too, ranking code suggestions and defaulting to the highest-scoring one. None of that is new. So rather than "add a percentage next to the answer", what if there is a specific flag pointing at the exact claim or step the agent is unsure about, feeding into the feedback loop? Curious if anyone else building in Copilot Studio has run into this: Do you ever wish your agent had hedged when it didn't? What would you actually do with an uncertainty score if you had one? And would just love others thoughts on this :)
how to create a globally Shared ServiceNow Connector Connection in Copilot Studio
Hello, I have configured Microsoft entra ID oauth using certificate and shared this connection with everyone in my company since this is the only shared connection on the platform. https://learn.microsoft.com/en-us/connectors/service-now/#microsoft-entra-id-oauth-using-certificate. But, whey user's ( end users, agent maker, environment maker basically any user in copilot environment) are trying to use any servicenow tools ( e.g create record) which is using this shared connection in copilot studio/ teams, they are getting below error. https://learn.microsoft.com/en-us/connectors/service-now/ How to create a shared connection which can be shared across all enterprise users in my org for copilot AI agents which are using servicenow connector? Regards, SachinError Connecting Whatsapp Number (Copilot Studio to Azure ACS)
Please help. I created an AI Agent in Copilot Studio for connecting to WhatsApp. I created an Azure Communication Services (ACS) and connected my personal Facebook page to it. I created a WhatsApp Business number, I got the code, and it connected. However, when I return to Copilot studio to connect using my Azure Subscription and Resource, it says- Error connecting to WhatsApp phone number. Please try again. How do I resolve this?Update: Root Cause Identified
Hi everyone, I would like to share the root cause and solution in case someone else encounters the same issue. The Problem I created several agent flows directly in Power Automate using: https://make.powerautomate.com The flows were configured correctly: The flow starts with When an agent calls the flow The flow ends with Respond to the agent The flow and agent are in the same environment The flow is included in a solution The flow is published and fully functional The flows could be added to an agent and executed successfully. However, unlike flows created directly from Copilot Studio, they did not appear in the Global Tools directory. What I Investigated I verified: Trigger configuration Respond to the agent action Environment consistency Solution membership Publish all customizations Asynchronous response settings Synchronization delays between Power Automate and Copilot Studio None of these were the root cause. Root Cause The issue was related to the workflow Plan. I discovered that: Flows created directly in Power Automate were assigned: Plan = The user running the flow Flows created directly in Copilot Studio were assigned: Plan = Copilot Studio Although the Power Automate flow was fully functional and could be used by the agent, it was not visible in the Global Tools directory. Solution After changing the workflow Plan to: Plan = Copilot Studio the flow immediately appeared in the Global Tools directory. Configuration Location The setting can be found in the workflow properties under: Primary owner → Plan Important Note Based on my testing, changing the Plan to Copilot Studio appears to be a one-way operation and may not be reversible. It may be a good idea to export or save the flow before making the change. Acknowledgements Special thanks to sohnash for reproducing the scenario and providing troubleshooting suggestions, and to Patty_Velasquez for sharing similar observations that helped confirm the behavior. Hopefully this helps others who encounter the same issue. Best regards, Adhonaï KOUKAPattern for governing Copilot Studio agents before they reach production
I keep seeing the same gap across Copilot Studio deployments: agents get built and shared before anyone has answered three basic governance questions. Before I call an agent production-ready, I check: -> Who's the sponsor? Not just who built it, who's accountable for it existing. -> What's it grounded on, and who can actually read that data? A knowledge source that's technically "in scope" isn't the same as verified content people should be answering from. -> Is there an audit trail for what the agent said and to whom, if someone asks later? None of this shows up in a demo. It only shows up a few months in, when the agent's still running and nobody remembers why. I wrote a longer breakdown of this governance model, including how Microsoft Agent 365 fits into it, here: https://jpmarquez.com/blog/microsoft-agent-365-licensing-what-you-actually-buy/ Curious what pattern others are using here, especially for the sponsor/ownership question, since that's the one I see skipped most.
New experience workflow can't use dynamic value in Business central connector bool
Hi all As the title states I have run into an issue when trying to use the Business central connector in a new experience workflow to create a record in my sales invoice lines. I am trying to create a prototype for an agent that can create invoices in my Business central environment based on certain criteria given by my customers. To let the agent do things in Business central I am trying to create workflows for it to use as tools, but when trying to add sales lines to the invoice, I can't seem to use dynamic values in two boolean fields, it only shows a dropdown with true/false. I know I could use a condition and use the create record four times depending on the combination of the two fields, but that seems messy, especially when this was possible back in power automate flows. Has anyone experienced this and do we know if this is considered a bug or won't it get fixed?
Copilot Studio Agent for Excel Macro Modernization — Anyone Tried This?
Anyone built a Copilot Studio agent to analyze macro-enabled Excel workbooks (.xlsm) and recommend a modernization path — e.g., migrating logic to Power Automate or rebuilding as Power BI dashboards? Curious about real-world attempts: what worked, what didn’t, and where the ROI actually showed up. Would love to compare notes before diving in myself. #CopilotStudio #Excel #PowerAutomate #PowerBI #PowerPlatformLooking for ideas: Reducing "Allow" prompts when using SharePoint Knowledge
Hello community members! I'm hoping to get some advice from people who may have come across a similar challenge with their Copilot Studio "SharePoint knowledge retrieval" agents 🤞 Current setup Agent set up in Copilot Studio and published to channels - M365 Copilot and Teams Agent is connected to 4 SharePoint folders (I'm using Method#1 - see below screenshot for reference). This is essential because the documents inside the folders contain both text and image-based content. This is the only method that brings results Users have permissions to access the content in these folders Problem We are currently preparing to roll out this agent but we've hit a user experience issue that is becoming a blocker for moving forward. When a user interacts with the agent for the first time, they are asked to click "Allow" ... 4 times .. one for each of the folder that the agent is connected to This experience feels heavy for users (based on our pilot feedback) and people give up after the first or second time because they think it is not working. In spite of comms and a video about having to repeat this action until done. We want the first time experience to be as smooth as possible to drive adoption. Also, we are going to expand the solution to include more folders soon - so there is also a concern that number of consent prompts could grow further. What I've tried Used Method#2 to connect to SharePoint folders. While this didn't pop up the "Allow" prompts, as indicated earlier, this approach doesn't work because it doesn't return any results from documents as they contain both text and image content. Tried Method#1 to connect to the library (and use instructions to indicate necessary folders) - this didn't work because the method doesn't allow to connect to libraries. Note - I cannot restructure the library and put all the documents into one folder because that's the way the documents have been maintained for a long time & direct links to the folders are being used across the organization via. emails, decks etc. Looking for advice Has anyone found a way to reduce or eliminate these consent prompts? Are there any other recommendations on using SharePoint as a knowledge source that respects user permissions without these consent prompts? Does anyone know why Method#1 and Method#2 have different user experiences where the first one prompts for consent and the second doesn't?
Deterministic way to mark generative answer output as AI-generated - AI Act
Hi all, We have a text-based RAG agent in Copilot Studio using the Azure AI Search connector as the knowledge source. It's customer-facing. We need every generated turn to carry a machine-readable marker identifying it as AI-generated, not just a visible disclaimer line. Instructing the model to append something isn't acceptable for us, because it's non-deterministic and can be prompt-injected away. Has anyone found a cleaner pattern? Like how to do it?
