AI governance

Power Platform governance for Copilot Studio: environments, data policies and sharing

How to govern Copilot Studio agents with the Power Platform admin center: split environments and route makers, set data policies for knowledge, tools and channels, cap sharing in Managed Environments, use the inventory, and move on from the CoE Starter Kit, without locking makers out.

9 min read Neptune Group

Navy illustration: an example count of 24 Power Platform environments with three listed: routed developer environments and a sales production environment are managed, while the default environment, flagged in coral, is not managed and holds 4 agents shared with the whole organisation.

Power Platform governance is the set of environments, data policies, sharing limits and inventory that decide where makers build, what their apps, flows and Copilot Studio agents may connect to, and who can use them. The controls sit in the Power Platform admin center. The work is choosing rules strict enough to protect data without pushing makers away.

Copilot Studio changed the stakes. A flow moves data from one place to another; an agent answers questions, reads knowledge sources, calls tools and can be published to Teams or a website. The same admin center governs both, and most of the settings that matter for agents already exist. Our page on Microsoft AI governance for Copilot and agents shows how this fits with the rest of your AI rules.

This article goes through the native building blocks in the order we would set them up: environments, data policies, Managed Environments, the inventory, then the CoE Starter Kit question. It ends with a starting set of rules that keeps agents in check without forcing every maker through a ticket.

What does Power Platform governance cover now that makers build agents?

It covers four controls, all in the Power Platform admin center. Data policies decide which connectors and knowledge sources agents may use, Managed Environments limit how widely agents are shared, and the Power Platform inventory lists agents, apps and flows. Environments are the frame that holds the other three.

What is new is the type of object. Makers can ground an agent on public websites and share it widely, often before anyone in IT has looked at it. The controls are the same ones you may already use for apps and flows, but the questions change:

  • Where may a maker build and test an agent?
  • Which knowledge sources, tools and channels may that agent use?
  • Who may use it, and who signs off when it goes wider?
  • Who can see it in a list, and who can stop it?

Answer them per environment rather than once for the whole tenant. That is what lets you be strict where it matters and relaxed where makers experiment.

How should you split environments?

Keep the default environment for light Microsoft 365 productivity work and move makers into their own developer environments. That is Microsoft's own advice in its environment strategy guidance, which treats the default environment as often the most restricted one, with data policies and sharing controls.

Developer environments are personal. Each maker can have up to three, and they do not count against your tenant's capacity. Microsoft disables, then deletes, a developer environment after 90 days of inactivity when its owner does not respond. Microsoft also recommends grouping these environments, so that the same rules apply to all of them, and you can show makers a welcome message that explains the rules of each environment.

Route makers automatically

Environment routing sends makers to their own developer environment instead of the default one. It covers Copilot Studio, Power Apps and Power Automate (cloud and desktop), but not Power Pages. You can route every maker or only a security group, and set several rules.

Three details shape the plan:

  • Routing is a premium governance feature and relies on Managed Environments: the environments it creates are managed. The default environment itself does not need to be managed.
  • Running a resource in a managed developer environment needs a premium licence. Check who is covered before you route everyone.
  • Routing is off by default, and sharing in routed environments is preset to individuals only, five people at most.

A starting layout to adapt

The layout below is our suggested starting point, not a Microsoft rule. The default environment stays for personal productivity with Microsoft 365 data only. Developer environments, grouped together, are where makers build and try agents. Shared team environments, managed and with a named owner, are where an agent goes once a team relies on it. Give each tier its own data policy and its own sharing limits. Sharing limits are a Managed Environments control, so applying them to the default environment means making it managed: check the licensing impact first.

Which data policies matter for agents?

The ones that cover Copilot Studio connectors, and they apply everywhere: Power Platform data policies apply to Copilot Studio agents in every tenant. According to Microsoft's page on data policies for Copilot Studio, enforcement has applied to all tenants since early 2025, exemptions are no longer possible, and policies are enforced in real time. You may also see them called DLP (data loss prevention) policies.

For agents, the connectors to look at fall into six groups:

  • Authentication: the "Chat without Microsoft Entra ID authentication in Copilot Studio" connector controls whether an agent can run without sign-in.
  • Knowledge sources: documents, SharePoint and OneDrive, and public websites. The connector "Knowledge source with public websites and data in Copilot Studio" is the one that lets an agent answer from the open web.
  • Tools: connectors used as tools. Blocking one also blocks the MCP tools that come with it.
  • HTTP requests and skills: direct calls to services outside your connector catalogue.
  • Channels: Teams and Microsoft 365, Direct Line, Facebook, Omnichannel, SharePoint and WhatsApp.
  • Event triggers: what lets an agent act on its own when something happens.

Filter rather than block

You do not have to choose between all or nothing. For public websites, SharePoint and HTTP, endpoint filtering lets you allow only approved sites or addresses instead of blocking the connector outright. An agent that may read your public product pages but not the rest of the web is a better outcome than a blanket ban that makers work around.

A sensible split: block public website knowledge and HTTP in the default environment, allow them with filtering in developer and team environments, and keep channels to Teams and Microsoft 365 until someone asks for more.

What do Managed Environments add?

Managed Environments are a set of premium capabilities in the Power Platform admin center. Two of them matter most for agents: environment routing, covered above, and sharing limits. The Managed Environments overview lists the others.

The sharing limits for agents are set per environment or per environment group. You can:

  • restrict sharing to individuals, so nobody can share an agent with a whole group;
  • once sharing is limited to individuals, cap the number of viewers for each agent;
  • decide whether makers may grant the Editor role, which only ever goes to named individuals, never to a group.

Three caveats matter. They only apply to agents that require sign-in. They are not retroactive, so agents already shared stay as they are. And they can take up to an hour to apply.

An agent published without authentication sits outside these caps. Pair the sharing limits with a data policy that blocks the "Chat without Microsoft Entra ID authentication in Copilot Studio" connector, and allow unauthenticated agents only in the environment where a public-facing agent genuinely belongs.

How do you see every app, flow and agent?

With the Power Platform inventory. It lists agents built in Copilot Studio and with Agent Builder in Microsoft Copilot (formerly Microsoft 365 Copilot), plus apps, flows, environments and environment groups. Updates appear within 15 minutes, and the list can be exported to CSV.

The inventory is also where you act. An admin can block a published agent or a canvas app while they investigate, and the block can be reversed. That matters for the tone of your governance: you can stop an agent that worries you without deleting a maker's work.

Give the right people the right role. The AI Administrator and AI Reader roles are limited to AI resources in the inventory, which suits a team that looks after agents but not the whole platform.

The inventory is not the only list. Agents also appear in the agent registry of the Microsoft 365 admin center, alongside agents from SharePoint and other platforms. Our article on Microsoft Agent 365 and the agent registry explains how the two views fit together.

Where does the CoE Starter Kit stand?

The CoE Starter Kit is no longer actively maintained, as its Learn page states. Its core capabilities are now part of the Power Platform admin center, through the Inventory, Usage, Monitor and Actions pages, with the Power Platform CLI, the Power Platform APIs and the Power Platform for Admins V2 connector for automation.

In practice:

  • Microsoft ships no further features or fixes for it, and reported problems are no longer looked at. Security vulnerabilities should still be reported to the Microsoft Security Response Center.
  • The kit remains available, for existing and new deployments.
  • Its GitHub repository was archived on 2 July 2026 and is read-only.

If you run the kit today, it remains available, but nothing in it will be updated when the platform around it changes. The useful step is to list what you actually rely on, report by report and flow by flow, and match each item to a page in the admin center. Keep the custom pieces that have no equivalent, and give each one an owner, since nobody upstream will update them.

Which rules keep agents safe without locking makers out?

Start with a few controls that each prevent one concrete problem, and set each one at the level that leaves room to build. The table below is a starting point to adapt.

Power Platform controls for Copilot Studio agents

Starting settings to adapt to your tenant and your licences.

ControlWhat it preventsStart with
Environment routing Makers building agents in the default environment, mixed with everyone else's work Route a pilot security group first, then every maker
Strict data policy on the default environment Agents in the shared default environment reaching connectors beyond Microsoft 365, or the open web Microsoft 365 productivity connectors only
Block unauthenticated chat Agents anyone can reach without signing in, which sharing limits do not cover Blocked everywhere except one named environment
Public website knowledge with endpoint filtering Answers built from web pages nobody has checked Allow approved sites only, in developer and team environments
Connectors as tools and HTTP requests Agents calling services or MCP tools nobody has reviewed Allow what each environment needs; HTTP on request
Channels Agents published to channels nobody supports Teams and Microsoft 365 only
Sharing limits in Managed Environments An agent opened to a whole group before anyone has tested it Individuals only, with a viewer cap you set
Power Platform inventory Agents nobody knows about, or nobody can stop Regular CSV export, owners named, block while you investigate
CoE Starter Kit review Reports that depend on a toolkit Microsoft no longer maintains Map each report you use to an admin center page

Where to start, in this order:

  1. Export the inventory and note which agents sit in the default environment.
  2. Tighten the data policy on the default environment and tell makers why.
  3. Turn on routing for a pilot group, with a welcome message that explains the rules.
  4. Group developer environments so that the same rules, sharing limits included, apply to all of them, and scope a data policy to those environments.
  5. Create a managed team environment for agents that a team relies on, with a named owner.
  6. Review the CoE Starter Kit reports you use and move them to the admin center.

Before tightening the default environment, talk to the makers whose agents live there. For agents grounded on SharePoint content, the quality of your permissions matters as much as any of these settings: our Copilot governance best practices cover oversharing, and SharePoint agents are governed through the sites they read.

How Neptune helps

Neptune is an integrator. We select the governance tooling that fits your tenant and your licences, implement it with your team, train your admins and makers, and support you once it runs: professional services during the project, then customer success.

We configure the native controls first: data policies and Managed Environments in the Power Platform admin center, including environment routing and sharing limits. The governance layer we put in place then adds the daily follow-up:

  • One inventory of apps, flows and agents, with the owner, activity and risk of each.
  • Daily checks on every app, flow and agent, ranked by severity and sent to its owner.
  • Agents grounded on public websites or shared too widely are flagged, and the agent owner is asked to fix them.
  • Every agent has a named owner. Agents with no recent activity and agents that were never published are flagged, and nothing is archived or deleted until the owner confirms.
  • Oversharing is tracked in Power Platform and Power BI, as well as in SharePoint and OneDrive.

Rules start in report mode, so you see what would be flagged before anything changes, and enforcement is switched on in waves, with owners informed. See how we cover AI agents within Microsoft 365 governance, or contact us to talk about the agents in your environments.

Sources

Copilot Studio agents arriving faster than you can review them? See how we govern Copilot Studio and other agents.

FAQ

Questions on this topic

Do Copilot Studio agents follow Power Platform data policies?

Yes. Power Platform data policies apply to Copilot Studio agents in every tenant, and enforcement has covered all tenants since early 2025 with no exemptions left. Policies can block public website knowledge, agents that run without Microsoft Entra ID authentication, HTTP requests, connectors used as tools or specific channels. For websites, SharePoint and HTTP, endpoint filtering lets you allow approved addresses only.

Can we stop makers sharing agents with the whole organisation?

Yes, in Managed Environments. Sharing limits can restrict sharing to individuals, so nobody shares an agent with a whole group, and cap how many people can use it. They apply only to agents that require sign-in, are not retroactive and can take up to an hour to apply. Block unauthenticated agents with a data policy so they cannot bypass the cap.

Can Copilot Studio agents use public websites as knowledge?

Yes, makers can ground an agent on public websites. Admins control this with the data policy connector "Knowledge source with public websites and data in Copilot Studio": block it, or use endpoint filtering to allow only the sites you approve. A common choice is to block it in the default environment and allow approved sites in the environments where makers build.

What is a Managed Environment?

Managed Environments are a set of premium governance capabilities in the Power Platform admin center. For agents, the two that matter most are sharing limits, which cap who can use an agent, and environment routing, which sends makers to their own developer environment. Running resources in a managed developer environment needs a premium licence, so check coverage before you switch them on.

Is the CoE Starter Kit still maintained?

Not actively. Microsoft states that the CoE Starter Kit is no longer actively maintained: it gets no new features or updates, and reported issues are no longer reviewed. The kit remains available, and its GitHub repository was archived on 2 July 2026. Microsoft points to the Inventory, Usage, Monitor and Actions pages of the Power Platform admin center, which now hold its core capabilities.

Can makers keep using the default environment?

For light Microsoft 365 productivity work, yes. Microsoft's environment guidance recommends moving makers who build apps, flows or agents into their own developer environments, and environment routing can do that automatically for everyone or for a security group. Keep a strict data policy on the default environment so whatever stays there cannot use connectors beyond the Microsoft 365 ones you allow, or the open web.

Have a question about your own tenant?

Tell us what you are working on and we will tell you where we would start.