Integrations, Microsoft Copilot Studio
The agents your business builds in Copilot Studio never go through your developers, and they still touch loans, accounts, and customers. Give them the same rules, the same reviewers, and the same record as your other connected agents, without leaving the conversation.
Ask for the evidence behind a decision and get exactly what your VeriProof access allows. Policy authors can draft and test a rule from the same conversation. Shadow, enforcement, and any approvals your organization requires happen in VeriProof.
A conversation ends in a business change more often than anyone plans for. The confirmed action gets checked against your rules first, and what happened is kept on record.
A person picks an action for a loan shown in Copilot Studio. Before the record changes, the lending service checks the current facts against policy.
The approval does not go through. The loan is recorded as denied under the lending policy, and the agent says so, with a link to the evidence that explains why.
Decisions use the current record in the business system, rather than treating conversation text as the source of truth.
Microsoft sign-in identifies the person. Their existing access in VeriProof and the business system determines what they can do.
The connected action service checks the rules before changing the record and reports the result for review.
The loan example is a starting point. Apply the same approach to the business actions you connect.
A case decision needs more than a conversation. Current records and the person's assigned role inform whether an action can proceed.
Policy checks come before the account update or payment instruction, giving your team control at the point of change.
Keep sensitive messages within your rules. The sending service can check the recipient, purpose, and content before release.
Connection instructions and examples cover evidence access, policy drafting, and business actions. Your developers can choose the path that fits.
Start with the working loan example, then connect the record and business action from your own system.
The decision history connects the request to its recorded result, including human review when the workflow requires it.
Create a free Developer account, add VeriProof to one Copilot Studio agent with the setup guide, and see what your compliance team sees afterward.