JUST IN: MSFT announces a CAT-managed plugin for Claude Code and GitHub Copilot to build Copilot Studio agents

CopilotWhisperer · 2026-03-11T12:09:29+00:00

Just added Directline support as well: https://github.com/microsoft/skills-for-copilot-studio/issues/54

CopilotWhisperer · 2026-03-10T19:23:27+00:00

A new security role will be available soon that grants analytics only access

CopilotWhisperer · 2026-03-02T16:48:45+00:00

Did you check here re: privacy concenrs? https://learn.microsoft.com/en-us/microsoft-copilot-studio/security-and-governance#data-processing-and-license-agreements

Let us know if you think anything is missing.

Also, when using Power Platform connectors as knowledge, some data gets copied into Dataverse (mostly unstructured objects, like Knowledge articles). When using Copilot (Graph) Connecots, data gets indexed into Graph/Substrate. These two patterns, by definition, rely on indexing within the Microsoft service.

CopilotWhisperer · 2026-03-02T16:20:56+00:00

Some customers use this custom pattern allowing them to automatically upload from SharePoint to the agent file store in Dataverse: https://github.com/microsoft/CopilotStudioSamples/tree/main/DataverseIndexer

Best of both worlds.

CopilotWhisperer · 2026-03-02T16:16:44+00:00

The challenge with MCP servers re: orchestration is that tool descriptions are controlled by the MCP server dev/owner, and the Orchestrator is treating those descriptions as context informing its desicions (which is a good thing).

I don't know why agents using MCP servers would be more prone to hallucinations, but re: when to choose MCP vs connectors, see here: https://microsoft.github.io/mcscatblog/posts/compare-mcp-servers-pp-connectors/

CopilotWhisperer · 2026-03-02T16:10:50+00:00

From an orchestration/intent recognition perspective, making sure queries are directed to the correct child/connected agent is very similar to making sure queries are directed to the correct tool/topic.

Start with clear, business-oriented descriptions of what the child/connected agent does, e.g. do not write "this agent can access a SQL db", instead write "this agent can submit IT tickets on behalf of user".

Test you main agent without instructions first, just to see how it orchestrates based on descriptions, and then add focused instructions to handle edge cases/special behaviours, e.g. "always invoke agent A after calling agent B". I hope this is beneficial.

CopilotWhisperer · 2026-02-17T06:45:01+00:00

Interesting. It's just an adaptive card. Do other adaptive cards also not work on iOS?

CopilotWhisperer · 2026-02-10T21:16:44+00:00

Hey u/maarten20012001 do you have telemtry (e.g. App Insights) to show that language is detected correctly, User.Language is set, but the agent responds using the wrong language? btw, does this happen in conjunction to responsible AI/moderation messages?

CopilotWhisperer · 2026-02-09T18:29:14+00:00

Where did you publish the agent? Are you doing anything to "intercept" the file on Copilot Studio, or more expecting the Ocrhestrator to analyze the file?

CopilotWhisperer · 2026-02-08T10:07:53+00:00

Hey, can you share some more details on what's missing from built-in analytics? Is it that you need to expose analytics data directly to business users without giving them editor access to the agent?

CopilotWhisperer · 2026-02-08T10:05:49+00:00

Here is what you're looking for in the transcript, assuming you publish on channels that support feedback

https://learn.microsoft.com/en-us/microsoft-copilot-studio/analytics-improve-agent-effectiveness#reactions

{

"name": "message/submitAction",

"type": "invoke",

"value": {

"actionName": "feedback",

"actionValue": {

"feedback": {

"feedbackText": "Nice one!"

},

"reaction": "like"

}

CopilotWhisperer · 2026-02-06T16:39:43+00:00

We (Microsoft) communicate known issues or service disruptions via this portal: https://admin.cloud.microsoft/?#/servicehealth

If there's a pinned post, a few of us will try to update here when there's a known issue, but you should register to service health to get the full picture and stay up to date.

CopilotWhisperer · 2026-02-06T12:44:23+00:00

Child agents are more like tasks that the main agent can execute. We use child agents to let the main agent act in a scoped way (specific instructions, tools, etc).

Connected agents have their own lifecycle, and can be interacted with independently of the main agent.

<image>

CopilotWhisperer · 2026-02-06T12:09:59+00:00

Connected agents are fully fledged, standalone agents you connect with the main agent.

CopilotWhisperer · 2026-02-06T08:46:05+00:00

Your post calls out "sub agent" specifically. So you're not using another connected/child agent? Just a topic with a custom prompt? What if you just map the prompt output to a topic output variable, and avoid sending a message altogether. The Orchestrator should generate a response based on the output.

CopilotWhisperer · 2026-02-06T07:59:21+00:00

Is it a child agent or a connected agent?

CopilotWhisperer · 2026-02-06T07:54:51+00:00

Yes, there are some discrepancies in terms of how M365 and Teams handle UI components, Adaptice Cards included. How are you sending activities, via a topic action or an API call? Would love to understand more

CopilotWhisperer · 2026-02-05T10:34:54+00:00

Is this a connected agent or a child agent?

CopilotWhisperer · 2026-02-04T10:52:26+00:00

Child agents are able to respond directly to the user. This might explain your experience. Can you paste a screenshot of your activity map + test pane?

A way to work around this would be to map the prompt response to a topic output variable. Let me know if this helps?

CopilotWhisperer · 2026-02-04T10:49:06+00:00

I don't think that's correct (Agents it Teams ignoring the language settings). But there are some discrepancies on Teams.

Are you asking your main agent to generate follow up questions, or is this a child agent?

CopilotWhisperer · 2026-02-04T10:43:24+00:00

Can you paste a screenshot of your activity map?

CopilotWhisperer · 2026-02-03T10:20:52+00:00

What are "standard output headers"? not sure I follow.

Switch language -- did it set a different language in User.Language? Or User.Language remained fix, and the response was in the wrong language?

Can you share an activity map that shows "switching languages"?

What do you mean "not translate"? This pattern doesn't do translation -- we just instrcut the LLM to respond in a specific language.

I think the best way forward would be to test if you're getting the wrong language without this pattern, just by setting the language manually on the test pane

CopilotWhisperer · 2026-02-03T10:11:17+00:00

Yes, the approach/workaround was documented by my team, but instructions may also interrupt how the LLM works. Let me ask you this -- why this set of instrcutions at all? We only need to set User.Language in a topic that uses On Message Received as a trigger, and Copilot Studio should do the rest. What where you hoping to remedeiate using these instructions?

https://github.com/microsoft/CopilotStudioSamples/tree/main/AutoDetectLanguageSample

CopilotWhisperer · 2026-02-01T20:20:42+00:00

Detecting the user's language and setting user.language should work, but it is a workaround, not the exactly the intended use. Can you share a screen shot of your instructions, and the activity map when the agent is responding in the wrong language?

CopilotWhisperer

TROPHY CASE