Integration · Microsoft Copilot Studio

Microsoft Copilot Studio.

Copilot Studio supports MCP servers natively. Connect Agent Cert as an MCP tool and every meaningful agent response can produce a signed, anchored Decision Receipt — no custom Power Automate flow required.

Prerequisites

A Copilot Studio agent (any topic, any channel).
An Agent Cert API key — get one at /welcome.
Your Agent Cert backend URL.

1. Add the MCP server connector

Open your Copilot Studio agent.
Go to Tools → Add a tool.
Select Model Context Protocol.
Server URL: https://YOUR-BACKEND/mcp/sse
Authentication: API key
Header name: X-API-Key
Header value: your Agent Cert key from /welcome
Save. Copilot Studio auto-discovers all six tools.

2. Wire the certify tool into a topic

In your topic, after the message that produces the agent's decision/answer, add an Action node calling certify_decision. Pass:

agent_id — a stable name for your agent (e.g. copilot_invoice_bot)
platform — "copilot"
user_intent — the user's original question (use Topic.UserInput)
agent_output — your generated answer
tools_used — the connectors / actions the topic invoked
retrieval_summary — summary of any knowledge base / Dataverse / SharePoint reads (optional)
policy_rules — ad-hoc rules to enforce on this answer, OR pre-bind a policy on /agents

3. Surface the verify URL back to the user

The tool returns a verify_url. Add it to your topic's final response so customers / auditors can independently verify the answer they got. Pattern:

{your generated answer}

This response is certified — verify at: {action.verify_url}

4. (Optional) Add risk gating

The tool also returns risk_level. You can branch on it in Copilot Studio:

low — send the agent's answer to the user.
medium — append a caveat or escalate to human review.
high — block the answer entirely; respond with a fallback.

Known notes

Copilot Studio caches tool definitions. If you update tools server-side, re-open the MCP connector dialog to refresh.
The certify_decision tool consumes 3 credits per call.
Other connectors (Office 365 Outlook, Teams, etc.) work alongside the Agent Cert MCP server — they don't conflict.