Two admin centers, one for each kind of agent
There is no “Copilot Studio admin center”. Agents are governed in two places, depending on how they were built:
| Agent built in | Managed in |
|---|---|
| Copilot Studio | Power Platform admin center (PPAC) |
| Agent Builder inside Microsoft 365 Copilot | Microsoft 365 admin center |
Agents published from Copilot Studio into Microsoft 365 Copilot also show up in the Microsoft 365 admin center, where you govern their availability to users. Building and running them is governed in PPAC.
The controls, grouped by question
Microsoft’s security and governance overview (November 2026) lists many controls. Grouped by the question an admin asks:
Who may build?
- The Copilot Studio authors security group in Microsoft Entra, for pay-as-you-go makers.
- Licenses: removing a person’s per-user, trial and Microsoft 365 Copilot licenses takes away build access along with the group.
- Environment routing, so new makers land in an environment you chose instead of the default one, and a maker welcome message.
What may agents use?
- Data policies in PPAC on authentication, knowledge sources, actions and connectors, HTTP requests, channels, Application Insights and triggers.
- A switch to disable publishing of generative AI agents.
- Connector dependency insights, to see which agents rely on which connectors.
What is happening?
- The Copilot Hub (PPAC > Copilot). Its Copilot Studio page shows consumption, active agents over the last 28 days, session success rate and the top 10 agents. Agent Builder agents are not included.
- Maker audit logs in Microsoft Purview and monitoring in Microsoft Sentinel.
- A security warning for makers and real-time risk assessment of agents.
What does it cost?
- Usage in the Copilot Hub and credit caps for pay-as-you-go.
Where does data go?
- Customer-managed keys, Customer Lockbox (with exclusions), and network controls in Microsoft Entra via Agent 365.
- Deploying agents from Git, for teams that want source control and review before release.
Agent 365 as the control plane
Microsoft positions Agent 365 as the layer above all this: agents become identities in Microsoft Entra, so they can be governed like users and apps, with network controls and access policies. For organizations with many agents, that is where inventory and identity come together.
The common mistake: governing the license, not the environment
Many admins stop at assigning licenses. But a license only decides who builds; data policies and environments decide what a finished agent can reach. A sensible order:
- Set data policies on the default environment first, restrictive.
- Create a separate environment for production agents with its own policies.
- Turn on environment routing so new makers don’t build in the default environment.
- Set a pay-as-you-go cap so an autonomous agent can’t run up the bill.
- Check the Copilot Hub monthly for agents nobody owns.
Licenses for makers are on What license do you need for Copilot Studio?, and the toolbox for testing and inventory at scale is the Copilot Studio Kit.
What this means for a team
Governance in Copilot Studio controls what agents may touch and who builds them. It does not decide what agents know, and it can’t make two agents agree: each still has its own instructions and knowledge. The admin’s view stops at the Microsoft boundary as well, while the same team also uses Claude, ChatGPT or Cursor.
Where Bombos fits
Admin controls govern access; they don’t give agents the same knowledge. Bombos is a plugin that gives Copilot, your Studio agents and the other AI tools your team uses (Claude, ChatGPT, Codex, Cursor, your own agents) one shared memory of team knowledge, learned rules, mail and documents. Every entry is traceable, and it runs in the cloud or on your own server. One person can try it first with their own agents.
Related questions
Is there a separate Copilot Studio admin center?
No. Copilot Studio is managed in the Power Platform admin center, where the Copilot section holds the Copilot Hub. Agent Builder agents and agents inside Microsoft 365 Copilot are managed in the Microsoft 365 admin center.
Can I stop makers from publishing generative AI agents?
Yes. Microsoft lists a setting in the Power Platform admin center to disable publishing of agents with generative AI features.
Does the Copilot Hub show Agent Builder agents?
No. The Copilot Studio page in the Copilot Hub excludes agents built with Agent Builder.
Can I see what makers change in agents?
Yes. Maker activity is written to audit logs in Microsoft Purview, and Microsoft Sentinel can monitor it.
