Copilot Cowork and Copilot Studio now share the same app-building engine: describe the outcome you want — the users, the data, the actions — and agentic coding turns that description into a working app scaffold. No canvas, no boilerplate, just a conversation that produces real, running software.

In this session I'll build an app live, starting from a plain-language prompt, and show what happens next: connecting it to organizational data through connectors and Work IQ, refining it iteratively through natural conversation, and inspecting the generated code the moment you need more control than prompting alone gives you.

Then we go past the demo and spend real time on the question every IT team asks about tools like this: who governs what gets built? I'll cover how identity flows through Microsoft Entra, how apps fit enterprise architecture with Git-backed source control, deployment stages, and version isolation, and how centralized discovery and oversight — via the Microsoft 365 admin center and the managed apps portal — give IT a single control plane over apps that citizen makers and developers are both producing. The goal is a concrete answer to "how do we let people build this fast without losing governance," not just a feature tour.

You'll leave knowing when to reach for Copilot Cowork versus Copilot Studio, how the maker-to-developer handoff actually works when you need to drop into code, what guardrails to put in place before you turn this on for your organization, and how to apply this to real scenarios — like an employee onboarding tracker or a field service app — in your own environment.