Microsoft

Microsoft Copilot Audit Trail & Evidence

Evidence for Copilot, Studio, and Azure OpenAI stacks

Microsoft deployments often combine Azure OpenAI, Copilot Studio agents, and M365 surfaces. Sigigo certifies decisions at API and workflow boundaries across that stack.

Where Sigigo sits

Three practical attachment points for Microsoft-heavy estates:

  • Azure OpenAI — same provider wrapper pattern as direct OpenAI
  • Copilot Studio / Power Platform — workflow hooks at tool and handoff boundaries
  • OpenTelemetry — GenAI spans from Azure Monitor or custom collectors mapped to ai_act events

EU and sovereign cloud buyers

Many Copilot rollouts land in EU regions with GDPR and DORA expectations. Sigigo defaults EU tenants to commitment mode and disabled public anchors — crypto-enforceable evidence without publishing payloads.

Framework integrations

Semantic Kernel and Microsoft Agent Framework paths support .NET and public-sector buyers who need human-in-the-loop gates with origin signatures on overrides.

Evidence events

Canonical event types emitted through this integration path:

  • ai_act.* via Azure OpenAI wrapper
  • ai_act.action_executed (Copilot Studio tools)
  • ai_act.human_review_* (approval gates)
  • Certified spans via OpenTelemetry GenAI semconv

Related

Integration availability may vary by tenant, region, and deployment model. This page describes product architecture — not a guarantee of feature availability. See compliance disclaimers and contact us for early access.