Microsoft Agent Framework
VeriProof provides Agent Framework packages for .NET and Python. Install the core SDK first, then check the adapter matrix for the capabilities available in your language. To enforce policy, use a supported hook that runs before the action executes.
| Language | Package | Boundary |
|---|---|---|
| .NET | Veriproof.Sdk.Adapter.AgentFramework | Owns supported agent input, buffered output, governed function calls, review resume, and scoped cancellation. |
| Python | veriproof-sdk-adapter-agent-framework | Maps supported Agent Framework middleware and serializable session state to the same contract. |
Use the adapter’s identifiers to connect an invocation with its recorded calls, branches, checkpoints, and results. Coverage depends on the hooks your application supplies.
A correlated event is not necessarily a controlled action. Check the operation’s enforcement status before relying on it.
Microsoft service prerequisites
Confirm which Microsoft services your organization can use. Microsoft 365 or Office 365 E5 alone does not establish access to Microsoft 365 Copilot or Copilot Studio capacity. Check Microsoft Foundry and Azure OpenAI access separately.
Use Microsoft Agent Framework for code-based agent orchestration. Use the official Foundry SDK for Foundry resources and Azure model access. VeriProof adds the policy, evidence, review, and control boundary; it does not replace either Microsoft owner.
For Azure-hosted workloads, keep the application key in Key Vault and grant the workload identity read access to that one secret. Do not place the key in deployment files, shell profiles, source control, or model prompts.
- A hook before execution can enforce the returned policy verdict.
- A hook after execution can record activity but cannot undo released output or side effects.
- The .NET adapter buffers streaming output and evaluates the complete output before release. Defaults stop after 4,096 updates, 1,048,576 characters, or two minutes. Other packages must follow their recorded stream capability.
- Side-effecting tools need stable invocation IDs, idempotency, and governed cancellation.
Agent Framework owns orchestration, session state, and framework checkpoints. VeriProof owns its governance checkpoint data, policy decision, review binding, action identity, and evidence references. The adapter does not replace the host tracer provider or duplicate Microsoft.Extensions.AI telemetry.
VeriProof preserves Microsoft identifiers for correlation. It does not create replacement Foundry resource types.
Foundry evaluations and OpenTelemetry traces remain separate from runtime policy. They can be linked to VeriProof evidence, but a passing evaluation score does not authorize a runtime action or increase an agent’s autonomy.
Keep one telemetry owner
Let the application own its OpenTelemetry providers. The VeriProof adapters emit content-free activity tags through that provider. Do not create a second provider or export the same span twice.
Keep content capture off unless the tenant has approved the exact data and retention path. VeriProof needs policy, review, application outcome, and integrity evidence. It does not need prompts, model responses, or tool values.
Use the adapter’s maintained setup for your language:
- .NET SDK and Agent Framework setup
- Python SDK and Agent Framework setup
- Package boundaries and requirements
Use the core SDK around application-owned work when a framework has no released Enforce adapter.
Run Govern your first action to prove one allowed function call, one denied function call, and the absent denied side effect.