Managed environments (Part 1)

Welcome back to our blog series all about Power Platform environments. Today, we're getting into the nitty-gritty of Power Platform Managed Environments.

🤔 Managed environments, okey... But what are they?

Managed Environments is a set of tools that make it easier for system administrators to control and monitor Power Platform. These tools reduce the work needed and provide better information. Managed Environments can be used for all types of environments, except for Developer environments.

Some key features of Managed Environments include the capability to restrict object sharing, provide usage insights (weekly) about apps, makers and inactive resources, improve data policies, and simplify Application Lifecycle Management (ALM) with Power Platform pipelines.

How to enable Managed Environments?

You must be an admin to enable or edit Managed Environments. That is, you must have the role of global admin, Power Platform service admin, or Dynamics 365 admin Azure Active Directory.

In the Power Platform admin center select Environments, check mark an environment. On the command bar, select Enable Managed Environments. If the environment is already managed, select Edit Managed Environments.

Configure the features, and then select Enable

So, let's dive into the features available

Limit sharing

Admins can control canvas apps sharing. To set up these rules, choose a managed environment from the list in the Power Platform admin center, click "Edit Managed Environments" in the command bar, and find the sharing rules in the "Limit sharing" section.

Solution checker

This is a preview feature in Managed Environments to enforce rich static analysis checks on your solutions against a set of best practice rules and identify problematic patterns.

Settings alternative:

• None: Disables automatic solution validations during import. No impact on solution authoring, exports, or imports.
• Warn: Automatically checks custom solutions during import. If critical issues are found, you receive a warning but can continue the import. A message and email is sent with details of the solution validation issues after successful import.
• Block: Automatically checks custom solutions during import. If critical issues are found, the import is canceled. A message and email is sent with details of the validation issues, so there aren't any changes to the environment due to the import failure.

The email is sent to all users with the roles of Power Platform administrator and Dynamics 365 service administrator. It is also sent to recipients of the weekly digest emails.

Weekly usage insights

Admins get weekly informed about apps usage and users activities

Maker welcome content

This is also a preview feature to provide a customized welcome message to makers to get started with Power Apps

Data policies

Data policies define the consumer connectors that data can be shared with. They make sure that data is managed in a uniform manner across your organization. They also prevent important business data from being accidentally published to connectors like social media sites.
With Managed Environments, admins can easily identify all the data policies that are applied to an environment.

Pipelines in Power Platform

Aimed to democratize Application Lifecycle Management (ALM) for Power Platform and D365 and make this service more approachable for admins and makers.
As prerequisite we have: at least three Power Platform environments, all environments must have a Microsoft Dataverse database, you must have a Power Platform administrator or Dataverse system administrator role to install the pipelines application and all target environments used in a pipeline must be enabled as Managed Environments.

Default environment routing

A feature that we all have been waiting for 👏 👏 👏
This feature allows Power Platform admins to automatically direct new makers into their own personal developer environment when they visit make.powerapps.com for the first time, instead of the default environment.

• Is enabled by Power Platform admins only.
• Requires that the Developer environment assignment setting is enabled for Everyone

Then, enable the Environment routing

I'm preparing a new blog post with focus on Environment routing, stay tuned 😉

To be continued...