From Copilot inspiration to a team that builds its own agents

The team lead was considering giving everyone in his team a Copilot licence, but wondered what it actually adds. The question: show concretely what copilots and agents mean for our work, and which steps it takes to go from experimenting to daily use and building our own.

Three sessions, each a step further. One: an inspiration session on Microsoft Copilot, with the distinction between assistants, copilots, automations and agents, translated to their own work, so the value of a licence becomes visible per role. Two: agents and automations, with a hands-on introduction to Microsoft Copilot Studio. Three: a knowledge transfer session, so the team can build, manage and maintain agents independently.

The team now knows which question a copilot solves and which one an agent does, has had the build platform in its hands and has a better overview of how to build and manage agents itself. The licence decision can be made per role, based on what was shown and tried.