Connect Copilot Studio

Choose the connection based on the work the agent will perform. Reading VeriProof evidence and changing a business record use different paths.

The agent needs to…	Start with
Find or explain VeriProof applications, sessions, decisions, reviews, or evidence	Direct MCP connection
Prepare and save a policy draft for portal review	Direct MCP connection
Change a customer record or start a protected operation	Governed business action

MCP is not an evidence-ingestion path or a shortcut around the system that owns a business action. Send application evidence through a VeriProof SDK or supported ingest endpoint.

Connect VeriProof directly

This path needs no customer-hosted Azure Function, managed solution, or custom connector.

An Administrator confirms the author’s license, environment capacity, publishing access, supported channel, and Power Platform data policy.
In VeriProof, open More tools → Agent tools → Connect and copy the public MCP address.
In Copilot Studio, add an existing MCP server. Select OAuth 2.0, dynamic discovery, and User authentication.
Sign in to VeriProof. Ask, “Which VeriProof applications can I access?” Confirm that the answer matches the portal.
Turn off any discovered tools the agent does not need.

Each person retains their VeriProof role, application access, and audit scope. Policy drafting may save an inactive draft, but it cannot activate, enforce, approve, delete, or create Developer work.

Govern a business action

Use the service that already owns the action. Add the registered-action adapter where that service checks and writes the business record.

An Administrator runs Test-VeriproofCopilotStudioPrerequisites.ps1 before importing a solution. Resolve every Action required result.
An Administrator reviews each Could not verify result for user licensing, capacity, publishing access, import permission, data policy, and tenant consent.
A Developer connects the action-owning service to VeriProof. The service must re-read the current record, check the rules, execute once, and retain the target receipt.
A Copilot maker adds the bounded action with User authentication. Remove any other tool that can perform the same write.
Test one request that VeriProof stops and one request that it allows. Confirm the business record changes only for the allowed request.
Open each returned evidence link. Compare the person, application, record reference, policy result, business message, target receipt, and client conversation reference.
In Agent portfolio, record the deployment and review the remaining production-qualification requirements.

Use the complete Copilot Studio guide for agent flows, custom connectors, Microsoft Entra setup, environment promotion, rollback, and removal.

Work by role

Role	Owns	Does not own
Administrator	Licenses, capacity, tenant publishing, environment access, data policy, consent, package checks, and deployment records	Business-rule behavior or target-system implementation
Copilot maker	Agent instructions, required tools, user authentication, conversation design, testing, and publishing	VeriProof permissions, policy approval, or target-system authority
Developer	SDK integration, current business facts, action-owner adapter, record version, idempotency, execution, and receipt	Policy meaning or deployment approval
Governance Engineer	Policy intent, logic, examples, deterministic tests, impact review, and permitted activation steps	Application field mappings or protected business writes
Publisher or approver	The exact policy version and deployment decision allowed by the organization’s change-control profile	Editing the application integration
Reviewer	Assigned human-review decisions and required rationale	Directly bypassing or rewriting a policy result
Auditor	Read-only evidence, scope, versions, approvals, integrity records, and qualification files	Configuration, publishing, or operational decisions
Support	Redacted diagnostics, package identity, connection state, and recovery guidance	Customer credentials, consent, role grants, or business decisions

Small organizations may assign policy author and publisher responsibilities to one authorized Governance Engineer. Controlled and Regulated profiles still require their configured independent approvals.

Know when the path is proven

Connected means the intended user can reach the required tool with the correct scope. It does not prove enforcement.

First governed action requires both a stopped request and an allowed request from the current package. Each needs a matching evidence link. The allowed request also needs a business-system receipt; the stopped request must leave the business record unchanged.

Production qualified requires current package, identity, rule, connection, action-owner, receipt, lifecycle, and cleanup evidence for the target environment.

Do not reuse development evidence as production proof. Repeat the stopped and allowed checks after changing the agent, tool, connector, flow, action owner, identity, rule, or data policy.