Power Platform French Summit 2026

08/12/2026, EFREI
Villejuif, France

Governing Computer-Using Agents (CUA): A KYC Automation Case Study in Copilot Studio

Many organisations struggle to automate KYC processes because the information they need is scattered across identity documents, emails, web portals, and legacy applications that don't expose APIs. While traditional automation works well for structured systems, real-world compliance workflows often require navigating fragmented information, interpreting documents, and making risk-based decisions. This is where Computer-Using Agents (CUA) come in. In this session, we'll explore how to architect, implement, and govern CUA-powered automation in Microsoft Copilot Studio using a real-world KYC onboarding scenario. Rather than positioning CUA as simply the next generation of RPA, we'll examine where it fits within an enterprise architecture, when it adds value beyond APIs, and what governance controls are required to operate safely in regulated environments. You'll learn: • When to use CUA versus traditional integrations and automation approaches • How CUA can automate KYC workflows involving identity documents, external registries, legacy systems, and fragmented data sources • How to establish governance through confidence thresholds, human-in-the-loop escalation, audit trails, and decision traceability • How to implement a governed solution using Copilot Studio, Power Automate, Dataverse, Microsoft Entra, and Microsoft Purview Through a live demonstration of a KYC triage agent, we'll walk through the complete journey from document intake and verification to risk assessment and escalation—showing how organisations can automate complex compliance workflows while maintaining transparency, accountability, and regulatory alignment. Key Takeaways 1. Understand the scenarios where CUA delivers value beyond APIs and traditional RPA. 2. Learn why KYC and compliance workloads are ideal candidates for CUA-driven automation. 3. Translate regulatory and governance requirements into practical Copilot Studio architecture patterns. 4. Implement an end-to-end pattern for document processing, verification, risk scoring, auditability, and human oversight. Comme on dit : “L’automatisation sans gouvernance, c’est juste du chaos plus rapide