Embed Copilot Studio agents in Canvas Apps with a PCF control
Diesen Beitrag auf Deutsch lesen
The ChatControl PCF component replaces the deprecated Canvas Apps Copilot control and adds SSO, custom styling and two-way agent communication.
TL;DR
The built-in Copilot control cannot be added to new Canvas Apps from February 2, 2026. The ChatControl PCF component embeds a published Copilot Studio agent using WebChat and the Microsoft 365 Agents SDK, but requires PCF enablement, System Administrator rights, Microsoft authentication and an Azure app registration for SSO.
Original by Dieter De Cock, on The Custom Engine. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Use the ChatControl PCF component when a Canvas App needs an embedded Copilot Studio agent, custom styling or app-to-agent context.
- Admins/CoE: Enable PCF components in the target environment and confirm System Administrator access before importing the solution.
- Security/Compliance: Configure Microsoft authentication and the Azure app registration required for SSO in both Azure and Copilot Studio.
- Leadership/Business: Account for the deprecated built-in control and assess whether the recommended Microsoft 365 Copilot replacement is available in your environment.
Frequently asked questions
How do I embed a Copilot Studio agent in a Canvas App after the built-in Copilot control was deprecated?
Use the ChatControl PCF component from the Copilot Studio Samples repository and import its Power Platform solution into the environment.
What must be enabled in Power Platform before adding the ChatControl PCF control to a Canvas App?
PCF components must be enabled in the target Power Platform environment, and the setup requires System Administrator rights there.
How does SSO work for a Copilot Studio agent embedded through ChatControl?
ChatControl uses the Microsoft 365 Agents SDK for SSO, with an Azure app registration and configuration in Azure and Copilot Studio.