Handle Copilot Studio connector consent cards with the Agents SDK
Diesen Beitrag auf Deutsch lesen
Detect consent Adaptive Cards, present their security details, and return the user's Allow or Cancel choice through the Agents SDK.
TL;DR
Copilot Studio requires end user consent before invoking connectors with end user authentication. In custom Agents SDK interfaces, detect cards using the Connect to continue text and Allow and Cancel buttons, then return a message activity with postBack true and the selected action.
Original by Adi Leibowitz, on The Custom Engine. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Render the consent Adaptive Card in custom interfaces and capture the user's Allow or Cancel choice, because end user authentication blocks connector invocation without consent.
- Admins/CoE: Treat native Entra ID connector consent separately from connection manager behavior, because custom connectors and other unsupported connectors use the more disruptive connection manager experience.
- Security/Compliance: Preserve the capability lines and privacy warning when presenting consent, because the card explains credential use and potential data exposure risks.
Frequently asked questions
How can an Agents SDK client identify a Copilot Studio connector consent card?
Check for a TextBlock containing Connect to continue and Action.Submit buttons titled Allow and Cancel. This heuristic identifies the consent payload without a dedicated event type.
What payload does Copilot Studio expect after an Allow or Cancel choice?
Send a message activity with channelData.postBack set to true and value containing the selected action, id submit, and shouldAwaitUserInput true.
Which connectors show the Copilot Studio consent card instead of connection manager?
Connectors that natively support Entra ID authentication can show it, while custom connectors and other connectors use the more disruptive connection manager experience.