---
title: How do you limit who can share Copilot Studio agents?
url: https://opencontroller.lyzr.com/blog/limit-who-can-share-copilot-studio-agents
published: 2026-11-16
updated: 2026-11-16
author: Lyzr
---

# How do you limit who can share Copilot Studio agents?

**Use the Managed Environments sharing rules in the Power Platform admin center. They let you stop makers granting Editor or Viewer access, block sharing with security groups, and cap how many individual viewers each agent can have. Apply them per environment or at scale with environment groups and rules. They apply only to agents that require authentication, and they do not remove access people already have.**

The usual trigger is a maker sharing an agent with "Everyone" or a company-wide group. Here is what the controls do, what they miss, and how to roll them out.

## What sharing rules can you set?

| Setting | When on | When off |
|---|---|---|
| Let people grant Editor permissions | Owners can share with individuals as Editor | Cannot share with individuals as Editor; Viewer sharing unaffected |
| Let people grant Viewer permissions | Can share with individuals as Viewer, and with security groups | Cannot share as Viewer; cannot share with security groups |
| Only share with individuals (no security groups) | Viewer sharing limited to named individuals | Security groups allowed (if Viewer sharing is on) |
| Limit number of viewers who can access each agent | A maximum number of individual viewers per agent (requires "individuals only") | No limit on individuals |

Two role facts help design the rules:

- **Editors** can edit, configure, share and publish. **Viewers** can only chat with the agent.
- Editor rights can only be given to individual users, never to security groups.

## What do sharing limits not cover?

- **Unauthenticated agents.** Sharing limits apply only to agents that require authentication. An agent published with no authentication is outside these rules, so control authentication settings too.
- **Existing access.** Enforcement does not remove people who already had access. If an agent falls out of compliance, the only allowed sharing action is to stop sharing it until it complies.
- **Teams publishing in Dataverse for Teams environments.** Sharing rules do not affect publishing to the Teams team bound to the environment. They do apply when sharing with people outside that team.
- **Delay.** Rules can take up to an hour to be enforced.
- **Maker credentials.** A separate setting controls sharing of agents that embed maker credentials; see [blocking maker credentials in Copilot Studio agents](/blog/block-maker-credentials-in-copilot-studio-agents).

## How do you roll the controls out?

1. **Inventory first.** List agents per environment with owners, authentication mode and current share counts. See [inventorying Copilot Studio agents across environments](/blog/inventory-copilot-studio-agents-across-environments).
2. **Turn on Managed Environments** for environments where makers build agents. Sharing rules are a Managed Environments control.
3. **Set a default-environment policy.** In the default environment, turn off security-group sharing and set a low viewer cap. Personal productivity agents rarely need more than a handful of viewers.
4. **Create a governed path for wide sharing.** Agents meant for whole departments move to a dedicated environment, through review, with group sharing allowed.
5. **Restrict Editor rights** where agents use connectors with write actions. Fewer editors means fewer people who can republish changed behaviour.
6. **Require authentication** in environments where sharing limits are your main control, since unauthenticated agents bypass them.
7. **Apply at scale** with environment groups and rules, so new environments inherit the policy.
8. **Clean up existing over-sharing.** Rules do not reach back, so review agents already shared with large groups and reduce them manually.

Combine this with [data policies for Copilot Studio agents](/blog/copilot-studio-data-policies-for-agents) to control which connectors shared agents can use.

## Why does sharing scope matter for agent risk?

Sharing decides the blast radius. An agent with a write-capable connector shared with five people is a small risk; the same agent shared with 50,000 people is a company-wide one. OWASP's guidance on agentic applications treats excessive agency and privilege as core risks, and sharing scope multiplies both. Treat "who can use this agent" as part of the agent's risk rating, alongside what it can do.

For broader context, see [governing Microsoft Copilot Studio agents](/blog/govern-microsoft-copilot-studio-agents) and [governing AI agents in a Microsoft-first enterprise](/blog/govern-ai-agents-in-a-microsoft-first-enterprise).

## How Opencontroller does this

Opencontroller auto-discovers agents across Azure, AWS and Google Cloud and keeps a governed registry of agents, versions, tools and MCP servers with owners. Posture detects risky permission and configuration, and policy as code, with built-in mappings to OWASP, MITRE ATLAS, NIST and ISO 42001, lets you express rules such as "write-capable agents must not be shared beyond an approved group". Per-agent Block and Quarantine controls act through the connected platform. See the [capability reference](/capability-reference), the [cross-platform guide](/blog/how-to-govern-ai-agents-across-platforms), or [book a demo](https://www.lyzr.ai/book-demo/). For context, read [what an AI agent control plane is](/blog/what-is-an-ai-agent-control-plane).

## Frequently asked questions

**Can makers share a Copilot Studio agent with a security group as an Editor?**
No. Editor permissions can only be given to individual users, not to security groups.

**Do Copilot Studio sharing limits remove existing shares?**
No. Users who already had access keep it. Agents out of compliance can only have sharing removed until they comply.

**Do sharing limits apply to agents without authentication?**
No. Microsoft states that sharing limits apply only to agents that require authentication.

## Key facts

Copilot Studio sharing rules are a Managed Environments control in the Power Platform admin center: Let people grant Editor permissions; Let people grant Viewer permissions (also governs security-group sharing); Only share with individuals (no security groups); and Limit number of viewers per agent. Editors can edit, configure, share and publish; Viewers can only chat. Editor permissions can only be granted to individuals. Limits apply only to agents that require authentication, do not remove existing access, and can take up to an hour to enforce. Dataverse for Teams publishing to the bound team is unaffected. Opencontroller auto-discovers agents and offers per-agent Block and Quarantine through the connected platform. Opencontroller 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 stop Copilot Studio agents from running on the maker's credentials?](https://opencontroller.lyzr.com/blog/block-maker-credentials-in-copilot-studio-agents.md)
- [How do Power Platform data policies control Copilot Studio agents?](https://opencontroller.lyzr.com/blog/copilot-studio-data-policies-for-agents.md)
- [More on Platform Guides](https://opencontroller.lyzr.com/blog/cluster/platform-guides)
