A managed environment is a Power Platform environment with Microsoft’s premium governance features switched on. It adds controls such as limits on how widely staff can share apps, a weekly email about usage, and automatic checks on solutions as they are imported. You switch it on in the Power Platform admin centre, the website where administrators run Power Platform. Whether your business needs one depends as much on your licences as on the features, so this guide covers both.
First, a few terms
Power Platform is Microsoft’s set of tools for building business software with little or no code. Power Apps builds apps, Power Automate builds flows, which are automated routines such as approvals, and Copilot Studio builds agents, AI assistants that answer questions or carry out tasks. Staff who build these things are called makers.
An environment is a container for apps, flows, agents and data. It keeps one set of work apart from another, such as a test version and the live one. Every organisation gets a default environment automatically, and anyone with a Power Apps, Power Automate, Microsoft 365 or Dynamics 365 licence can build in it. Microsoft says the default environment is meant for experiments and light work, not for production systems the business depends on.
What is the Power Platform admin centre?
The admin centre lives at admin.powerplatform.microsoft.com. Microsoft describes it as the place to manage environments, security, Copilot, monitoring, deployments, licensing and support across Power Platform and some Dynamics 365 apps. Each of those has its own area in the left-hand navigation. There is also an Actions area, where Microsoft lists recommendations for your setup. Power BI is the exception, as it has its own admin portal.
To switch on a managed environment, you need the Power Platform Administrator or Dynamics 365 Administrator role in Microsoft Entra ID, the service that holds your staff’s Microsoft sign-ins. Someone who is only an admin of one environment cannot do it.
What a managed environment adds
Microsoft calls managed environments “a suite of premium capabilities” that give administrators more control with less effort. For a smaller firm, four of them matter most.
Sharing limits can stop makers sharing a canvas app with security groups or with everyone. A canvas app is one laid out by hand, screen by screen, and a security group is a named list of users. You can also cap the number of individuals an app is shared with, and set similar rules for flows and agents. People who already have access keep it, but an app that breaks the new rules can only be unshared until it complies.
Usage insights send administrators a weekly email. It shows the most used apps and flows, the most active makers, and apps and flows nobody has launched for a while, which are good candidates for tidying up. Tenant-level analytics, a setting that collects usage data across your organisation, must be on for this to work.
Solution checker enforcement tests solutions, which are packages of apps, flows and data tables, against Microsoft’s best-practice rules when they are imported. You can set it to warn, or to block solutions with critical issues.
Maker welcome content shows makers a message of your choosing, such as your house rules for building apps.
The settings also show which data policies apply to the environment. Data policies decide which connectors, the links to services such as SharePoint or social media, can share data. They work in any environment, managed or not, and Microsoft recommends protecting every environment with one. More advanced controls, such as an IP firewall and customer-managed encryption keys, tend to suit larger or regulated firms.
The catch: licences
Managed environments come included with standalone licences such as Power Apps Premium and Power Automate Premium, and with qualifying Dynamics 365 licences. The rule that follows is strict. Once an environment is managed, everyone who runs an app or flow in it needs one of those licences or a pay-as-you-go plan. The Power Apps rights that come with Microsoft 365 do not count.
Microsoft is moving to enforce this. Its page on licensing requirements for managed environments says administrators have received notices since March 2026, and users without a qualifying licence have seen in-app warnings since June 2026. From February 2027, those users cannot open apps in a managed environment at all. The Licensing area of the admin centre can produce a report of the users affected.
One more date matters if anyone has signed up for Microsoft’s free Developer Plan. Unmanaged developer environments are being retired. New ones cannot be created from 15 November 2026, and existing ones are suspended from 15 December 2026 unless they are made managed first.
Does your business need one?
Ask three questions. Who builds, who uses the results, and what licences do those users hold?
If a few staff build personal apps and flows in the default environment, and everyone has only Microsoft 365, managing that environment would mean a premium licence for everyone who runs those apps and flows. Data policies and sensible sharing habits may be enough for now.
If you run apps the business depends on, used by many people or touching customer or financial data, a managed environment earns its place. The case is strongest when those users already hold qualifying licences, because the extra controls then cost nothing more. A sensible pattern is a separate production environment, managed, for business-critical apps, with the default environment left for personal work.
How to switch one on
Production, sandbox and trial environments need Dataverse, Microsoft’s database for Power Platform, before they can be managed. Then follow Microsoft’s steps:
- Sign in to the Power Platform admin centre at admin.powerplatform.microsoft.com.
- In the navigation pane, select Manage, then select Environments.
- Select the three dots next to the environment, then select Enable Managed Environments.
- Choose your settings for sharing, usage insights, the solution checker and the welcome message, then select Enable.
To change the settings later, select Edit Managed Environments in the same place. Microsoft notes that new sharing rules can take up to an hour to take effect.
Getting it right first time
Spark 365 works with UK firms on the Power Platform. If you would like help deciding which environments to manage, and what that means for your licences before February 2027, we are happy to talk it through.