One SDK Client for Both Copilot Studio Harnesses
Diesen Beitrag auf Deutsch lesen
The JavaScript and .NET Copilot Studio clients can connect custom apps to standard and GitHub Copilot harnesses with Entra ID.
TL;DR
The Copilot Studio client uses the same conversation methods for standard and GitHub Copilot harnesses when given an environment ID and agent schema name. JavaScript and .NET support is available, while Python support is planned. GitHub Copilot harness support remains preview, with endpoints rolling out across regions.
Original by Adi Leibowitz, on The Custom Engine. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Admins/CoE: Test the client in an early release environment because GitHub Copilot harness endpoints are still rolling out across regions.
- Security/Compliance: Configure an Entra app registration with the CopilotStudio.Copilots.Invoke delegated permission and avoid storing a client secret in the browser.
- Makers: Use the environment ID and correct agent schema name, then keep the agent published with Authenticate with Microsoft enabled.
Frequently asked questions
How does CopilotStudioClient connect to both Copilot Studio harnesses?
The client uses the environment ID and agent schema name, then applies the same conversation methods to either harness.
Which Microsoft Entra permission does the Copilot Studio React WebChat sample require?
The app registration requires the Power Platform API delegated permission CopilotStudio.Copilots.Invoke, with organizational consent as needed.
Does showReasoning enable reasoning in a Copilot Studio agent?
No. showReasoning displays reasoning already sent by the service, while the harness and model determine what the client receives.