Power Platform Environment Groups Reference Setup for AI-Built Apps
A Power Platform environment groups reference setup for AI-built apps: managed environments, group rules, advanced connector policy and routing, in order.
Your makers are building apps, flows and agents with AI help. In a tenant nobody has configured, the agents they build in Copilot Studio and the apps and flows they build in Power Apps and Power Automate land in the default environment. Learn says so plainly: “If no rule matches, or if environment routing isn’t turned on, the maker is routed to the default environment.” The Environment routing setting is off by default.
This is a Power Platform environment groups reference setup for AI-built apps: what to configure, and in what order.
The default applies to makers who build agents in Copilot Studio and to makers who build apps and flows in Power Apps and Power Automate. They stay in the default environment until you turn routing on for those products (Environment routing, What is a personal environment?, Environment routing for Copilot Managed Runtime).
One routing behaviour is already on in your tenant. Routing for Copilot Managed Runtime (preview) “is on in every tenant, and you can’t turn it off.” If your tenant has no routing rules, Power Platform creates a rule that routes Everyone to their own personal environment. It also creates a default environment group with Copilot Managed Runtime rules. If your tenant already has routing rules, Power Platform doesn’t change them. Either way, Microsoft may have already made part of your routing design for you.
There is also a date to plan around. Unmanaged developer environments are deprecated and “suspended starting December 15, 2026,” while the managed developer environments that routing creates aren’t affected.
The order matters because “Routing never moves a personal environment from one environment group to another.” If you route makers into the wrong group, you have to remove each personal environment from that group and add it to the right one. While it sits outside a group, its settings unlock. Sharing works the same way. Sharing rules apply when someone shares, and they don’t affect people who already have access (Limit sharing).
Takeaway: the order you configure these controls decides what you can still change later.
The Power Platform environment groups reference setup at a glance
Seven layers, in the order we recommend configuring them.
| Layer | What it does | What Learn says happens without it |
|---|---|---|
| 1. Licensing and roles | Confirms who can switch things on and who can run what lands in managed environments | “Starting February 2027, users who don't have an appropriate license can't open apps in managed environments.” |
| 2. Managed environments | Unlocks the premium governance features on each environment | “Environment groups can only contain managed environments.” |
| 3. Environment groups with published rules | Locks settings across every environment in the group | “only published rules are enforced across environments” |
| 4. Tenant data policy floor plus advanced connector policy | Sets connector boundaries for every new maker, then tightens them per group | “No specific data policies are assigned to the developer environment.” |
| 5. Environment routing | Gives each maker a managed personal environment inside a chosen group | “the maker is routed to the default environment” |
| 6. Pipelines in Power Platform | Provides a reviewable promotion path into shared environments | Learn lists the manual steps pipelines remove: “connect to multiple environments, export solutions, download solution files, manually create connections and populate deployment settings files, import solutions” |
| 7. Copilot Managed Runtime layer (preview) | Applies Microsoft-managed rules to Copilot Managed Runtime apps | If your tenant already has routing rules, “only makers who match one of them can build Copilot Managed Runtime apps.” |
If you already sort agents into risk tiers, these groups are where those tiers get enforced. That makes this setup a natural companion to risk-tiered agent governance.
This piece builds on the dev/test/prod layout in our Power Automate environment strategy guide and adds three things to it: the setup order for AI-built apps, the advanced connector policy layer and the Copilot Managed Runtime layer (preview).
Our recommended setup uses four groups. This layout is our recommendation, not Microsoft’s:
- Maker workspaces for routed personal environments.
- Pro developer workspaces for routed personal environments of your professional developers.
- Dev/Test, a shared group.
- Production, a shared group.
The layout builds on Learn’s own examples. What is a personal environment? uses a “Pro developer workspaces” and “Maker workspaces” routing example. Environment groups uses “Personal Productivity” for routed environments and splits Dev/Test from Production.
The structural rules come straight from Learn:
- “Environment groups can only contain managed environments.”
- “Each environment can belong to only one group, and groups can’t overlap or be nested.”
- “Keep personal environments in environment groups of their own, separate from shared development, test, and production environments.”
Takeaway: draw this layout on paper before you touch the admin center.
Step 1: Roles and licensing, checked before anything is switched on
Start with roles. “To enable or edit managed environments, you need the Power Platform Administrator or Dynamics 365 Administrator role in Microsoft Entra ID.” Users with the Delegated Admin role or the Environment Admin security role can’t change the property (Enable managed environments).
Next is licensing. Managed environments are “a suite of premium capabilities,” and they are included as an entitlement with standalone Power Apps, Power Automate, Microsoft Copilot Studio, Power Pages and Dynamics 365 licenses (Managed environments overview). Environment groups and environment routing are both premium governance features.
Routed personal environments are managed environments, and that sentence shapes your rollout. Learn puts it this way: “Because personal environments are managed environments, makers and users need a premium license to run them. The Power Apps Developer Plan doesn’t include use rights for managed environments. Starting February 2027, users who don’t have an appropriate license can’t open apps in managed environments.”
There is one carve-out, and it is preview: “Makers who use their personal environment only to build Copilot Managed Runtime apps don’t need a premium Power Platform license. Building apps consumes Copilot Credits, and running them requires Copilot Credits or a Power Apps Premium license.”
Takeaway: confirm license coverage for your Maker workspaces audience first. If you route makers into managed environments without that coverage, you create a run-time problem for the people who open their apps.
Step 2: Managed environments setup on the environments that will join shared groups
Your managed environments setup starts with the environments you own: shared Dev/Test and Production. In the Power Platform admin center, select Manage, then Environments. Select the ellipsis next to an environment, then select Enable Managed Environments. If it’s already managed, select Edit Managed Environments instead.
You have two scripted routes.
The first is the pac admin command pac admin set-governance-config, documented as “Enable, disable, and edit managed environments.” Its --protection-level parameter takes Standard to enable managed environments.
The second is PowerShell. Learn gives this script for a single environment:
$GovernanceConfiguration = [pscustomobject] @{
protectionLevel = "Standard"
settings = [pscustomobject]@{
extendedSettings = @{}
}
}
Set-AdminPowerAppEnvironmentGovernanceConfiguration -EnvironmentName <EnvironmentID> -UpdatedGovernanceConfiguration $GovernanceConfiguration
Dataverse is required for production, sandbox and trial environments. Developer environments don’t need Dataverse to become managed.
One caveat matters here. Learn says: “If the target environment isn’t a managed environment, copying settings also enables it as a managed environment.” For this setup, that means a settings copy changes the target’s status. Plan copies with that in mind.
Takeaway: enable managed environments on shared Dev/Test and Production now. Personal environments arrive already managed, because routing creates them that way.
Step 3: Create environment groups and publish the environment group rules
You have four ways to create groups:
- Admin center: select Manage, then Environment groups, then New group (Environment groups).
- CLI:
pac environment-management create-environment-group, which is “(Preview) Create the environment group.” (pac environment-management). - The Power Platform REST API, which backs that same CLI command.
- The Power Platform for Admins V2 (Preview) connector, which creates and deletes groups and adds or removes environments.
pac admin doesn’t create groups. Its group commands only add an environment to a group and list groups.
Our recommended setup for rules uses Learn’s names exactly (Rules for environment groups):
- Maker workspaces: Sharing controls for canvas apps, Sharing controls for solution-aware cloud flows, Sharing agents with Editor permissions, Sharing agents with Viewer permissions, Maker welcome content, Usage insights, Generative AI settings. Step 4 adds Advanced connector policy.
- Shared Dev/Test and Production: Solution checker enforcement.
Once you publish a rule, it locks. The setting “becomes locked (read-only) within individual environments.” Learn also states: “Per-environment exceptions aren’t currently supported.” Rules you leave untouched stay under environment-level control.
The caveats, each stated as what Learn says and what it means for this setup:
- Button names differ. Learn says “Publish rules” on the groups page and “Apply” in the rules gallery. For this setup, publish (Apply in the rules gallery) is the step that enforces a rule. Saving alone doesn’t.
- Adding and removing work differently. Learn says “You can add and apply rules in bulk, but you must remove them individually.” For this setup, getting a rule set wrong costs more to undo than to get right the first time.
- There is no pause. Asked whether you can temporarily disable a rule, Learn answers “No.” For this setup, the only way to stop enforcing a rule is to remove it.
- Some rules need setup first. Learn says Maker welcome content and Default deployment pipeline rules “require individual configuration before you can apply them.” For this setup, write the welcome content before you build the group.
Takeaway: publish the rules on a group before any environment is routed into it.
Step 4: Data policies: a tenant floor first, then an advanced connector policy on top
Routed developer environments get no data policy of their own. Learn says: “No specific data policies are assigned to the developer environment. The developer environment inherits existing, tenant-level data policies.” The policy that applies is “Your tenant-level data policies, plus the rules of the environment group.” Your tenant data policy is therefore the floor for every new maker.
Our recommended setup adds the Advanced connector policy rule to Maker workspaces (Advanced connector policies). Three properties make it the right tool for maker workspaces:
- It denies by default. “New connectors added to the platform are automatically blocked.”
- It can block connectors that classic policies can’t. “On managed environments (single or environment group), you can block any connector or any action, including those that are nonblockable in classic data policies.”
- It combines with your existing policies. Mixed mode is the default: “ACP runs alongside classic data policies, and the most restrictive settings from both are enforced.”
Caveats, each stated as what Learn says and what it means for this setup:
- Certified connectors only. Learn says: “Custom connectors and HTTP connectors aren’t yet supported.” For this setup, keep classic data policies in place for custom and HTTP connectors.
- Design-time enforcement is rolling out. Learn says design-time enforcement arrives in the Power Automate maker portal first, then Copilot Studio, then the Power Apps maker portal. Each portal’s release marks ACP general availability for that workload. For this setup, ACP is runtime-only in any portal that hasn’t reached design time yet.
- Whole MCP servers, not tools. Learn says granular control over individual MCP tools isn’t available, while “Blocking the entire MCP server is supported.” For this setup, an MCP server is either allowed or blocked as a whole. So weigh every tool a server exposes when you make that call.
- ACP-only mode is preview. The group rule “Advanced connector policies only (preview)” is a preview rule. For this setup, stay in mixed mode on Maker workspaces.
Removal doesn’t undo an ACP. If you remove the rule from a group, or remove an environment from the group, the affected environments keep the last ACP configuration they received. Learn calls this intentional, “because it prevents an enforcement gap where connectors would otherwise become unexpectedly unblocked.”
Takeaway: set the tenant floor, then the group ACP, and only then route anyone.
Step 5: Turn on environment routing
Learn still calls environment routing “default environment routing” on some pages. To turn it on, select Manage, then Tenant settings, then Environment routing. It’s off by default, and “Only Power Platform admins can enable environment routing.”
Our recommended setup mirrors Learn’s example with two rules. The first sends the Pro Developers security group to Pro developer workspaces. The second, last in priority, sends Everyone to Maker workspaces. Every new routing rule must name an environment group. “When a maker accesses a portal, the system evaluates the rules in order and applies the first matching rule.”
The Everyone rule has hard limits. “You can’t delete the routing rule that routes Everyone to an environment group. After Copilot Managed Runtime governance initializes in your tenant, you can’t modify it either.” Governance initializes when someone creates the first app. It initializes earlier if an admin opens the app governance experience in the Microsoft 365 admin center (preview).
The Everyone rule must also be last in priority. If it sits above a security-group rule, adjust the priority before you make any other change (What is a personal environment?, Environment routing for Copilot Managed Runtime).
Before you build on Learn’s example, check two things: whether your tenant already has an Everyone rule, and which group it names. If it does and governance has initialized, you can’t repoint it. Our recommended setup for that case is to route makers with security-group rules placed above the Everyone rule.
If you create security-group rules without an Everyone rule, only matching makers can build Copilot Managed Runtime apps. Learn says: “All other makers are blocked until admins of these tenants create a new Everyone routing rule or add makers to security groups used in routing rules.”
| Setting | Routed environment default | Group rule override |
|---|---|---|
| Sharing limits | Excludes security groups; shares with five individuals | Published sharing control rules override it |
| Solution checker | Warn | Published Solution checker enforcement overrides it |
| Usage insights | On | Published Usage insights rule overrides it |
| Maker welcome | Not established | Published Maker welcome content overrides it |
| Data policies | Tenant-level only | Group ACP adds to the tenant policy; the most restrictive result applies (ACP-only mode is a preview rule) |
| Security role | Makers get the admin security role | Not changed by group rules; group-governed settings are locked |
Takeaway: routing works the way you want only when Steps 2 to 4 are already in place.
Step 6: Pipelines in Power Platform as the promotion path
Learn’s guidance is short: “When a larger group of people starts to rely on an app, flow, or agent, move it to a shared environment that your organization owns and supports.”
Our recommended setup uses Pipelines in Power Platform as the reviewable route from personal environments into shared Dev/Test and Production. This applies to work built in Power Apps, Power Automate and Copilot Studio. For pipeline setup detail, including approval gates and deployment settings, see our guide to moving flows from dev to prod with Pipelines in Power Platform.
The Default deployment pipeline (preview) rule associates a pipeline with development environments in a group:
- Development means developer or sandbox. “Development” environments are defined as developer or sandbox environments.
- Both ends become managed. “Source and target environments used in the default pipelines are automatically enabled as managed environments.”
- It takes time. “Wait up to 10 minutes for the rule to apply.”
Our recommended setup sets Solution checker enforcement to Block on the Dev/Test and Production groups. Here is what each mode does, in Learn’s words:
- Warn: “you’re warned about the action but the import itself continues.”
- Block: “When a solution has highly-critical issues, the import process is canceled, and a message stating that the imported solution had validation issues is shown.”
Learn adds: “As a reminder, only critical severity rules block a solution from being imported.”
Takeaway: in our recommended setup, work that a larger group relies on moves through a pipeline into a shared group with Block enforcement. Sharing from a personal environment still works within the group’s sharing rules.
Step 7: The Copilot Managed Runtime layer (preview), kept short
Microsoft manages the default environment group for Copilot Managed Runtime, and “You can’t delete this group” (default governance settings).
As of November 6, 2026, the group includes 18 Microsoft first-party connectors that authenticate exclusively through Entra ID and 12 Microsoft first-party MCP servers. Microsoft adds qualifying connectors automatically. Selecting Edit this policy gives you control of the connector policy, and “Automatic updates from Microsoft stop for connectors, MCP servers, and action controls.”
Two settings are disabled by default. Each can be configured for an environment or an environment group:
- External artifacts in managed apps.
- App creation with the Copilot Managed Runtime CLI.
Existing configurations survive. “Organizations that already use Microsoft Power Platform keep their existing environment routing, environment groups, and advanced connector policies,” and the Copilot Managed Runtime rules “layer in without overriding existing configurations.”
Learn describes these apps as “governed from the moment they’re created” (overview). The feature is preview, and the security and governance page adds: “These protections don’t replace reviewing app code and dependencies.” There is also a documented known issue: guest users can’t open these apps, even with guest sharing turned on.
Takeaway: treat this as one more group you inherit, not a replacement for your own layout.
Setup order checklist
In our recommended order, routing comes after groups, rules and data policies. That way every new personal environment is created inside a group that is already governed.
- 1
Roles and licensing
Confirm Power Platform Administrator or Dynamics 365 Administrator access. Confirm premium license coverage for the Maker workspaces audience.
- 2
Managed environments
Manage > Environments > ellipsis > Enable Managed Environments on shared Dev/Test and Production. Or run pac admin set-governance-config with --protection-level Standard.
- 3
Groups and rules
Manage > Environment groups > New group, or pac environment-management create-environment-group (preview). On each group's Rules tab, use + Add rules, then publish (Apply in the rules gallery).
- 4
Data policy floor, then ACP
Set the tenant data policy floor. Then add Advanced connector policy to Maker workspaces from the group Rules tab (+ Add rules).
- 5
Environment routing
Manage > Tenant settings > Environment routing. Add Pro Developers to Pro developer workspaces first, with Everyone to Maker workspaces last.
- 6
Promotion path
From the group Rules tab (+ Add rules), configure Default deployment pipeline (preview) and set Solution checker enforcement to Block on Dev/Test and Production.
- 7
Copilot Managed Runtime review
In the Microsoft 365 admin center, go to Apps > Settings > Environment groups and review the inherited default group.
Changes don’t take effect instantly. Learn gives “a few minutes” for rules gallery propagation, “up to an hour” for sharing limits, and “up to 10 minutes” for the pipeline rule. Verify each setting has applied before you test.
Get a second set of eyes on what your makers are building
If makers in your tenant are already building with AI, a short review names the top three risks in what they’ve built or plan to build and recommends one next step.
Book a free 30-minute AI app review with Citizen Development Academy
Stay in the loop
Get new posts delivered to your inbox. No spam, unsubscribe anytime.
Related articles
Configure Copilot Studio Security Controls for Agents Your Business Users Build
Configure Copilot Studio security controls in the right order: data policies, build access, knowledge, sharing, authentication and monitoring for agents.
Scanning AI-Generated Code in Pipelines: A Gated PR Intake
Scanning AI-generated code in pipelines: a gated pull request intake for apps built in Lovable, Cursor or Claude Code, before they reach company data.