Power Platform Administration Step By Step Step by step · Lab 2

Managed Environments: Set Them Up Before Feb 2027

What Managed Environments add, the licence rule behind them, and how to set sharing limits, solution checker and usage insights with pac.

8 November 2026 · 5 min read

Edit Managed Environments: exclude sharing with security groups and limit sharing to 20 individuals — Watch the lesson: Lab 2: Managed Environments | Power Platform Administration Step By Step

A managed environment is a normal environment with a set of governance features switched on: who it can be shared with, what makers see when they arrive, how solutions are checked, and a weekly digest for admins. In Lab 2 of the Power Platform Administration course, we make Pragati’s admin lab environment managed.

What Managed Environments add

Slide: sharing limits, usage insights, maker welcome content, solution checker, and more — The features, grouped.

Sharing limits: cap how widely apps and agents can be shared.
Usage insights: a weekly digest e-mail to admins.
Maker welcome content: your own message when makers first arrive.
Solution checker enforcement: warn or block imports that fail the checks.
And more: an IP firewall, longer backups, the catalog, routing and pipelines.

The licence rule

There is no Managed Environments product to buy. Instead, people who use apps and flows in a managed environment need premium licences: Power Apps, Power Automate, Copilot Studio or Dynamics 365. The Developer Plan gives no Managed Environments use rights.

Microsoft shows notices to unlicensed users since June 2026 and has announced a block from February 2027. Check the licensing report before you switch a busy environment to managed. In the lab, the admin’s Power Apps Plan 2 trial gives the rights at no cost.

Open the environment, Edit managed environments. Under Manage sharing → Power Apps: exclude sharing with security groups, and limit sharing to 20 individuals. A maker can no longer share an app with the whole company by accident. For Copilot Studio, agents can be shared with individuals only.

Manage sharing: exclude sharing with security groups, limit total individuals to 20 — Sharing limits for canvas and code apps.

Step 2: Enforce the solution checker

Solution checker enforcement: Block. A solution with critical security or reliability issues cannot be imported into this environment.

Solution checker enforcement slider set to Block — Block, not just warn, for environments the business relies on.

Step 3: Usage insights and welcome content

Include the environment in the weekly e-mail digest of top apps and flows, and add maker welcome content: a short message makers see when they first open Power Apps here. Save; the settings apply at once.

Usage insights included in the weekly digest, and maker welcome content text — Tell makers where they are and what the rules are, the first time they arrive.

Step 4: Automate it

pac admin set-governance-config does the same in one line: standard protection, no group sharing, at most twenty people, and the solution checker set to block. Ideal for configuring many environments the same way.

Terminal: pac admin set-governance-config with protection level Standard and solution checker mode block — One command per environment, or a loop over many.

What a tech lead should take away

Check licences first. Managed Environments are free to switch on, but every user then needs a premium licence.
Sharing limits and the solution checker stop the two most common accidents: an app shared with everyone, and a broken solution in production.
Script it. Twenty environments configured by hand will drift; one script will not.

Do it yourself

Lab guides, practice and full mock exams come with a subscription. See the plans