From tool to teammate: Persistent agents for shared processes in Copilot Studio | BRK261

Evan Lew and Matt Hidinger present a practical look at setting up Copilot Studio agents for ongoing team workflows, with demonstrations of enterprise collaboration, process memory, and administrative controls.

Setting up agents for recurring work

The session compares configuring an AI agent with onboarding an employee: both need an identity, context, skills, and guardrails. The focus is on agents that participate in shared business processes over time, rather than only responding to individual requests.

The presenters cover four building blocks:

Collaboration across enterprise applications

A live demonstration follows the Gopher Launch agent as it collaborates across Teams, Outlook, SharePoint, and Dataverse. The scenario covers document collaboration, automated launch coordination, and workflow updates.

The session also explores capabilities that extend how agents participate in workflows:

A separate memory demonstration covers shared team memories, preferences, and learning used to optimize the process.

Identity, governance, and cost controls

The administrative demonstration covers security roles, tenant controls, Microsoft Purview, and conditional access. These controls accompany the agent-account model and help administrators govern agents participating in enterprise work.

Lew and Hidinger also distinguish Copilot Studio agents from personal autopilots and discuss cost management controls. The session closes with a Lumen customer case study and guidance for getting started.

Session chapters

Resource

This is an intermediate-level Agent Platform breakout session from Microsoft Ignite 2026, presented in English (US).