Agent Flows and Computer Use are the two automation engines inside Copilot Studio, and they solve different halves of the same problem. Agent Flows give you deterministic, connector-driven automation across the systems that expose APIs. Computer Use lets an agent drive any application through its interface - clicking, typing, and reading the screen - for the systems that never did. The real skill is not picking a side; it is knowing which engine fits which part of a process, and how to combine both inside one agent.
Most practitioners have reached for one and worked around the other. This workshop closes that gap. You will build a single real-world automation the way it is actually shipped in production: structured, API-driven steps handled by Agent Flows, UI-only steps handled by Computer Use, and human-in-the-loop where governance demands it. Then you will harden it and learn a repeatable framework for making the same calls on your own projects.
You leave with hands-on experience across both engines, a decision framework for matching any requirement to the right approach, and a clear view of where each one breaks in production and how to design around it.
Is this you?
- Power Platform developer or RPA specialist - You have built with one automation style and want to see where the other fits, and how the two work together.
- Automation architect - You need to know which engine to reach for, and when combining both is the right call, grounded in real behavior rather than vendor slides.
- Enterprise consultant - You want a repeatable framework for matching each requirement to the right approach, every time.
What you'll take away
- Hands-on experience with both engines, built on one real-world scenario.
- A decision framework covering technical fit, governance risk, maintainability, and scalability.
- A clear pattern for combining Agent Flows and Computer Use inside a single agent.
- A clear map of where each approach fails in production, and how to design around it.
How the day looks
| # | Block | Topic |
|---|
| 1 | Morning | Readiness check & environment setup - confirm your tenant, Copilot Studio trial, and Dataverse environment, enable generative orchestration, and run a quick smoke test so everyone starts on a working setup |
| 2 | Morning | Foundations - the Copilot Studio automation toolkit: what Agent Flows and Computer Use each do best, and where they overlap |
| 3 | Morning | Building with Agent Flows - triggers, connectors, conditions, and error handling on a real scenario |
| 4 | Morning | Going deeper with Agent Flows - parallel branches, loops, approvals, and human-in-the-loop |
| 5 | Afternoon | Adding Computer Use - driving apps and portals that have no API: element reasoning, resilience, and fallbacks |
| 6 | Afternoon | Combining both, then hardening for production - orchestrating Agent Flows and Computer Use in one agent: performance, failure modes, and governance |
| 7 | Closing | Choosing the right approach - a decision-framework workshop applied to attendees' real scenarios |
What to bring & prepare in advance
This is a hands-on lab. Please arrive with everything below already set up and tested - not configured on the morning of the workshop.
Your device
- Your own personal laptop - not a company or work-issued device. Corporate laptops carry device management, conditional access, VPN or proxy, and firewall or DLP restrictions that repeatedly block the sign-ins and connectivity the lab needs. Bring a personal machine on which you have local administrator rights (Windows 10/11 or macOS 10.14 or later).
- Microsoft Edge or Google Chrome, installed and up to date (Edge is recommended for the Computer Use exercises).
- Your phone with the Microsoft Authenticator app, for multi-factor sign-in to your own tenant.
Your tenant and licensing
- Your own Microsoft 365 tenant, on which you are the Global Administrator - not your employer's corporate tenant. Corporate tenants block self-service sign-up, apply DLP and connector governance, and restrict environment creation, all of which will stop you from building agents, Agent Flows, and Computer Use.
- Build a personal tenant now if you do not have one. The free Microsoft 365 Developer Program tenant is now restricted and generally requires a qualifying Visual Studio subscription, so the reliable route for most people is a Microsoft 365 Business or Enterprise trial (or a low-cost paid plan) on which you are the administrator.
- A Copilot Studio trial, activated in advance on that tenant. You cannot start a Copilot Studio trial with a personal email address such as Outlook.com or Gmail - it requires the work or school account from your own tenant. The trial runs for 30 days and can be extended.
- A Power Platform environment with Dataverse enabled in that tenant, since agents require Dataverse.
- Activate everything a few days before the workshop, then confirm it works. Tenant, environment, and Dataverse provisioning can take time, so set everything up and run a quick test ahead of the day rather than on the morning of the workshop.
Your knowledge
- Solid working knowledge of Copilot Studio (prerequisite).
- Familiarity with Power Automate cloud flows (prerequisite).
- Basic understanding of UI automation - helpful, but not mandatory.
Official Microsoft links to get set up
No personal tenant or Copilot Studio license? Tell us at registration.
If you are unable to arrange your own tenant or a Copilot Studio license, let the organizers know while you register - not on the day. With enough notice, we will try to provision a lab environment for you to use on your personal laptop. We cannot set this up at the last minute, so please give us the heads-up as early as possible.
🎯 Level 300-400 - Experienced / Advanced
📅 December 2, 2026
🕘 9:00 - 17:00
📍 Clarion Congress Hotel Prague
Reserve your spot
Gold partner
Power Apps
Copilot Studio
Microsoft Fabric
Power Apps
Copilot Studio
Microsoft Fabric
Power Automate
