Manage Microsoft 365 Copilot agents with registry-first controls
Diesen Beitrag auf Deutsch lesen
Use the Microsoft 365 admin center registry to review, block, scope and govern Copilot agents across the tenant.
TL;DR
In the Microsoft 365 admin center, Agents > All agents lists tenant agents by status, platform and publisher. Review each agent's data access and permissions, block unwanted agents with a recorded reason, or scope installation to groups. Use Agent Management Rules to transfer ownerless Agent Builder agents to the previous owner's manager.
Original by Anders Jensen, on andersjensenorg. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Admins/CoE: Start with the All agents registry, filter by publisher, platform and status, then review agent data access and permissions before rollout.
- Security/Compliance: Block unsuitable agents and record the reason; blocking removes the agent from users who already installed it.
- Admins/CoE: Use Specific users or groups for pilot rollout, and verify outside-pilot users cannot see scoped agents.
- Leadership/Business: Schedule quarterly reviews because Frontier-labelled controls, Agent 365 features and interface details change frequently.
Frequently asked questions
Where can admins see every agent in a Microsoft 365 tenant?
In the Microsoft 365 admin center, open Agents, then All agents and the Registry tab.
What happens when an admin blocks an agent in the Microsoft 365 registry?
Nobody in the organization can install or use the agent any more, and it is also removed from users who already installed it.
How do I limit a Microsoft 365 Copilot agent to a pilot group?
Open the agent in the registry, go to the Users tab and choose Available to. The options are All users, No users or Specific users or groups.