Integrations, Microsoft Agent 365
Agent 365 knows who your agents are. VeriProof decides what they're allowed to do.
If your organization runs on Microsoft 365, Agent 365 is probably where your agent inventory, identities, and security controls already live. VeriProof works alongside it on a different question: should this payment, claim, or order go through, and who decides when it shouldn't?
Who handles what
Microsoft describes Agent 365 as the control plane for agents, built to observe, govern, and secure them. It keeps a registry of your agents, gives each one an identity through Microsoft Entra Agent ID, applies access controls, extends Purview data protection and retention to agent interactions, and uses Defender to block risky actions it detects as threats.
VeriProof starts where the business rules start.
Scroll horizontally to see all columns.
| The question | Where it's answered |
|---|---|
| Which agents do we have, and who owns each one? | Agent 365 registry |
| Who is this agent, and what can it sign in to? | Microsoft Entra Agent ID and Conditional Access |
| Is sensitive data protected and retained correctly? | Microsoft Purview |
| Is this action a security threat? | Microsoft Defender |
| Is this $40,000 supplier payment allowed under our rules today? | VeriProof policy decision |
| Who has the authority to approve it if it isn't? | VeriProof routes it to that person and returns the answer to the agent |
| Can risk, compliance, and audit each work from the same record? | VeriProof role portals and decision records |
One refund, both products
A customer-service agent built in Copilot Studio proposes a $2,400 refund.
Agent 365 already knows this agent. It's registered, it has its own identity, and it can only reach the systems it has been granted. Nothing about the request looks like an attack, so Defender lets it through.
Then the refund reaches VeriProof. Your policy says refunds above $1,500 for accounts under a year old need a supervisor, so the action pauses and the request goes to the supervisor who holds that authority, with the account facts attached. She approves it. The agent completes the refund, and the record shows the rule version, her decision, and what the application did. Compliance sees the same record in its own view, and so does internal audit when it comes asking.
Running both
Agent 365 is licensed per user, at $15 per user per month on its own or included in Microsoft 365 E7. VeriProof is priced for your application portfolio, with published plans and a 30-day paid evaluation for one agent.
VeriProof runs as a managed service on Azure, or entirely in your own Azure subscription with Private Enterprise. Your Copilot Studio agents reach it through the Copilot Studio integration, and agents built in code reach it through the SDKs.
Questions from Microsoft shops
No. VeriProof works with or without it. If you run Agent 365, keep using it for inventory, identity, and security; VeriProof adds the business-rule decision and the record.
No. Purview protects and retains your data, and Defender watches for threats. VeriProof decides whether a business action follows your rules and records who approved the exceptions.
Yes. Private Enterprise, coming soon to Azure Marketplace, will run entirely in your Azure subscription, completely separate from VeriProof's managed service.