Power Platform Community Forum Thread Details

Hi Everyone,

I noticed a new governance control in Copilot Studio → Settings → Data access → Agents called:

“Choose who has permission to share agents with your entire organization.”

This looks like one of Microsoft’s newest admin-level sharing policies for Copilot Studio, and I wanted to open a discussion to better understand its impact and best practices.

What This Setting Does

It seems to define which users or groups are allowed to share Copilot Studio agents org-wide.

The available options are:

Allow all users to share with anyone in the organization
No users can share with anyone in the organization, but can choose who they share agents with
Allow specific groups of users to share with anyone in the organization (new granular option)
The third option is particularly interesting it lets admins designate approved groups (for example, “AgentWorld,” “AI Governance,” or “Center of Excellence”) that can share bots across the tenant, while limiting others to local or team sharing.

Why This Matters

This new control appears to:

Strengthen data governance and security for enterprise deployments
Prevent broad sharing of draft or test agents
Help organizations maintain oversight of who can publish or share copilots publicly within the tenant
Align Copilot Studio’s governance model with Power Platform environment permissions

Discussion Points

Have others seen this feature in their tenants yet?
Does changing this require Global Admin or Power Platform Admin permissions?
Does it affect only Copilot Studio agents, or also custom copilots built within Microsoft 365 Copilot?
How does this setting interact with Managed Environments or DLP policies?

Would love to hear how others plan to configure this in their organizations and whether Microsoft has shared detailed documentation or roadmap notes for this feature.

Categories:

Bot administration

Hi @sannavajjala87

Agree and actually this is a great feature for one specific reason which you ask about.

Discussion Points

Have others seen this feature in their tenants yet?
- Yes
Does changing this require Global Admin or Power Platform Admin permissions?
- Yes
Does it affect only Copilot Studio agents, or also custom copilots built within Microsoft 365 Copilot?
- Both, it covers full and lite so I really really love this.
How does this setting interact with Managed Environments or DLP policies?
- They work in conjunction; this is more of a specific, let's call it catch all. You can block specific groups etc or everyone or no one, where-as let's pretend you block or allow the sharing of specific security groups (which might have certain security roles), BUT you want that security group to only be able to use X and Y connectors and block everything else. You would combine this + DLP policies + any specific Environment specific groupings in Managed groups.
- So they are building blocks, where this confines groups/people, and the others, while they can do that too, this is easier so that the others can focus on feature level or asset level control

Yeah this one I really like because I hated creating policies etc to emulate this and I wish this was there when I was at PPCC it would have changed my answers to some people.