Session
From Agent Sprawl to Agent Control: Governing Copilot Studio Access, Costs and Production Readines
AI agents are moving from experiments to operational systems, but governance is often lagging behind deployment. In Microsoft environments, Chief AI Officers and AI Architects increasingly have to answer practical questions that traditional AI governance frameworks do not solve: Who can access an agent and its connectors? What data can the agent reach? Who owns it when the original maker leaves? How much does experimentation cost? When is an agent actually ready for production?
This session provides a practical governance model for Microsoft Copilot Studio and Agent Builder, focused on the controls that matter after an agent has been built.
We will examine four governance problems that are becoming critical in 2027: fragmented administration across Microsoft 365 and Power Platform, uncontrolled connector and knowledge-source access, agent sprawl and underused or ownerless agents, and poorly controlled Copilot Credit consumption. Microsoft’s current guidance confirms that credit consumption can begin during building, preview and evaluation, making governance necessary before production. It also recommends controls at tenant, environment, agent and operating-process levels.
The session will then turn these problems into practical controls. Participants will learn how to establish least-privilege access to external connectors and tools, distinguish environment-level governance from agent-level controls, assign accountable ownership, administer user and group access, monitor agent usage and consumption, and design a controlled path from development to testing and production.
A major focus will be publishing validation. An approval to publish does not by itself demonstrate that an agent is safe, useful or production-ready. We will examine a practical validation gate covering identity and access, data sources, connector permissions, expected behavior, evaluation results, failure modes, cost, logging, ownership, business accountability and rollback or retirement criteria.
The session will also cover common administration traps in Agent Builder, including the difference between owners and chat users, group-based access, organizational sharing and the relationship between an agent's access and the underlying SharePoint data. Microsoft currently supports multiple individual owners for Agent Builder agents, while groups cannot be assigned as owners.
Finally, we will address cost governance. Participants will see how to combine environment-level capacity controls with agent-level limits, notifications and hard stops, and why monitoring consumption only after deployment is too late. Microsoft currently provides agent-level monthly limits and hard-stop controls through the Power Platform admin center.
The session is delivered by Prof. Hernan Huwyler, AI Governance, Risk & Compliance specialist and Claude Certified Architect – Professional (CCAR-P), issued by Anthropic. The CCAR-P credential is Anthropic's professional-level architect certification, covering enterprise-scale Claude deployments, integration architecture, evaluation, governance and responsible deployment.
The emphasis throughout is practical: what to configure, what to monitor, what to validate, who should own each control, and which governance failures are likely to appear when organizations scale from a handful of agents to hundreds.
Hernan Huwyler
AI Risk & Compliance Leader| Academic Director IE | Decision-Making | AI Threats and Controls | Responsible Technology | Quantitative Risk | Compliance | Certified AI Architect
Copenhagen, Denmark
Links
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top