---
title: How do you govern agents in Microsoft 365 Copilot?
url: https://opencontroller.lyzr.com/blog/govern-microsoft-365-copilot-agents
published: 2026-11-12
updated: 2026-11-12
author: Lyzr
---

# How do you govern agents in Microsoft 365 Copilot?

**Govern Microsoft 365 Copilot agents from the Agents section of the Microsoft 365 admin center. Use the registry to see every agent, the Requests queue to approve org-published agents, Settings to control who can use and share agents, and lifecycle actions to block or delete them. Pair this with Purview for audit and data controls, and remember the registry is a Microsoft 365 view, not a view of every agent your company runs.**

Agents reach Microsoft 365 Copilot from several builders: Agent Builder inside Copilot, Copilot Studio, Microsoft Foundry, SharePoint and the Agents Toolkit. Each one is governed partly in the Microsoft 365 admin center and partly in its own tool.

## Where do admins see every Copilot agent?

In the Microsoft 365 admin center, go to **Agents > Overview** for the dashboard and **Agents > All agents > Registry** for the full list. Microsoft describes this view as the agent control plane for Microsoft 365.

The overview shows:

- the agent registry and active users
- agent run-time and registry sync
- pending requests
- agents at risk, using signals from Entra, Defender and Purview
- agents without owners and agents with exceptions

The registry tags each agent with a publisher type: Microsoft, External partner, Published by your org, or Shared by creator. Viewing risk signals needs a Microsoft 365 E7 or Agent 365 licence. Agent 365 became generally available for commercial customers on May 1, 2026. The Graph API for the registry is still in preview, so check its status before you build automation on it.

## How does approval work for org-published agents?

When a maker publishes an agent to the whole organisation, it lands in **Agents > All agents > Requests**. This covers agents built in Copilot Studio, Foundry and the Agents Toolkit.

An admin then either rejects the submission or approves it. Approving runs **Publish to store**, where you choose:

1. Which users or groups get the agent.
2. Which policy template applies.
3. Whether to grant admin consent for the permissions it needs.

Only an **AI Administrator** or **Global Administrator** can approve requests or assign owners. Keep that role list short, because these admins decide which agents reach every employee.

## Which settings control use and sharing?

Under **Agents > Settings**, admins can:

| Setting | What it controls | Applies to |
|---|---|---|
| Allowed agent types | Allow or deny agents built by Microsoft, by your org or by external publishers | All agents |
| Sharing | All, No, or Specific users | Agent Builder agents only |
| User access | Which users can use agents | All agents |
| Agent management rules | Automatic rules, such as blocking ownerless agents with no usage | All agents |

Note the scope of the sharing setting. It covers Agent Builder agents only. Copilot Studio agents are also governed by Power Platform environments and data policies, so a complete policy needs both consoles. Our [Copilot Studio guide](/blog/govern-microsoft-copilot-studio-agents) covers that side.

The Microsoft Learn pages we checked do not document a single switch that stops users creating Agent Builder agents. If that matters to you, confirm the current options with Microsoft before rollout.

## What can admins do to an agent that misbehaves?

The lifecycle actions are:

- **Block or unblock** an agent for users.
- **Install, uninstall or activate** it.
- **Delete**, which is a soft delete with 30-day retention. You can restore it or delete it permanently.
- **Start or stop**, which applies to Foundry agents only.
- **Assign a new owner**, for shared Agent Builder and Copilot Studio agents.

Ownership matters most when people leave. An ownerless agent keeps running with nobody accountable for it. See [what happens to AI agents when the owner leaves](/blog/what-happens-to-ai-agents-when-the-owner-leaves).

## What does Purview record about agents?

For Agent 365 agents, Purview auditing ("Agent 365 activities") and classification are on automatically. DLP, Insider Risk, eDiscovery and retention need the agent added to each policy explicitly. Purview's AI observability view sits under **DSPM > AI observability**.

A practical checklist for a Copilot agent rollout:

1. Restrict approval rights to a named group of AI Administrators.
2. Set sharing for Agent Builder agents to Specific users during the pilot.
3. Add a management rule for ownerless, unused agents.
4. Add agents to DLP, retention and eDiscovery policies, not just audit.
5. Export audit events to your SIEM, so evidence outlives the portal view.

## What does this view not cover?

The Microsoft 365 registry covers agents that reach Microsoft 365. Agent 365 also offers a registry sync, in preview, that lists agents from sources such as Amazon Bedrock, Vertex AI, Salesforce Agentforce and Databricks. Microsoft documents that sync as read-only and manual: it lists those agents but cannot start, stop or invoke them.

So you still need a plan for agents on other clouds and SaaS platforms, coding agents on developer laptops, and the model traffic and spend behind all of them. Our [cross-platform guide](/blog/how-to-govern-ai-agents-across-platforms) explains how to join these views, and [what an AI agent control plane is](/blog/what-is-an-ai-agent-control-plane) covers the category.

## How Opencontroller does this

Opencontroller is Lyzr's open control plane for enterprise AI agents. It auto-discovers agents, models and API keys across AWS, Azure and Google Cloud, has a runtime adapter for Microsoft Foundry, and connects to platforms such as Salesforce, SAP, Databricks and HubSpot, so Microsoft and non-Microsoft agents sit in one governed registry. [Book a demo](https://www.lyzr.ai/book-demo/).

## Frequently asked questions

**Who can approve agents published to a Microsoft 365 organisation?**
An AI Administrator or Global Administrator, under Agents > All agents > Requests in the Microsoft 365 admin center.

**Can admins delete a Copilot agent and get it back?**
Yes. Delete is a soft delete with 30-day retention. After that window, the agent is gone.

**Does the sharing setting cover Copilot Studio agents?**
No. The Microsoft 365 sharing setting applies to Agent Builder agents. Copilot Studio agents also follow Power Platform environment and data policy controls.

## Key facts

Microsoft 365 admin center: Agents > All agents > Registry lists agents; Requests tab approves or rejects org-published agents (AI Administrator or Global Administrator). Lifecycle actions include block/unblock and soft delete with 30-day retention. Agent Builder sharing can be All, No or Specific users. Agent risk signals need Microsoft 365 E7 or an Agent 365 licence; Agent 365 GA May 1, 2026. Purview audits Agent 365 agents automatically; DLP, Insider Risk, eDiscovery and retention need the agent added to policy. Opencontroller by Lyzr is an open control plane across clouds and agent platforms; pricing starts from $250K per deployment per year.

## Related

- [How do you govern Microsoft Copilot Studio agents?](https://opencontroller.lyzr.com/blog/govern-microsoft-copilot-studio-agents.md)
- [How do you govern agents in Microsoft Foundry?](https://opencontroller.lyzr.com/blog/govern-microsoft-foundry-agents.md)
- [What happens to AI agents when their owner leaves the company?](https://opencontroller.lyzr.com/blog/what-happens-to-ai-agents-when-the-owner-leaves.md)
- [More on Platform Guides](https://opencontroller.lyzr.com/blog/cluster/platform-guides)
