{"id":108603,"date":"2024-04-04T08:00:00","date_gmt":"2024-04-04T15:00:00","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/?p=108603"},"modified":"2024-05-16T08:36:53","modified_gmt":"2024-05-16T15:36:53","slug":"increase-efficiency-with-microsoft-power-platform-governance-features","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/2024\/04\/04\/increase-efficiency-with-microsoft-power-platform-governance-features\/","title":{"rendered":"Increase efficiency with Microsoft Power Platform governance features\u00a0"},"content":{"rendered":"\n

Preview Microsoft Power Platform environment groups and rules <\/h2>\n\n\n\n

As organizations expand their Microsoft Power Platform footprint to meet the needs of their users for application modernization and the inclusion of Microsoft Copilot, administrators can utilize premium features such as managed environments to govern at-scale quickly and easily, while increasing visibility and control. However, as more environments are deployed, administrators need a way to streamline governance and ensure consistency. <\/p>\n\n\n\n

One of the reasons why Microsoft Power Platform is becoming more popular and widely adopted in organizations is its ability to enable rapid application development and innovation. Microsoft Power Platform allows users of different skill levels to create and customize apps, workflows, chatbots, and reports that suit their business needs, using low-code or no-code tools. Microsoft Power Platform also integrates seamlessly with other Microsoft products, such as Microsoft 365, Microsoft Dynamics 365, Microsoft Azure, and Microsoft Teams, as well as with external data sources and services. By using Microsoft Power Platform, organizations can empower their employees to solve problems, automate processes, and improve efficiency, without compromising security or compliance. <\/p>\n\n\n\n

In our effort to increase efficiency and streamline the process of managing Microsoft Power Platform, we\u2019re thrilled to introduce the public preview of Microsoft Power Platform environment groups and rules<\/a> <\/strong>and the newest capabilities of environment routing.  <\/p>\n\n\n\n

Explore more about environment groups and rules in the official documentation<\/a>. <\/p>\n\n\n\n

Making governance at-scale even easier <\/h2>\n\n\n\n

Environment groups empower admins to establish governance policies through customizable rules, ensuring consistency across environments and eliminating chaos. Microsoft Power Platform administrators can create environment groups. These groups serve as holders for related environments. You can use environment groups to organize your environments by department, project, cost center, or any other relevant criteria, offering a systematic way to manage collection of environments in aggregate. <\/p>\n\n\n\n

In each environment group, administrators can uniformly apply six key capabilities of managed environments to all associated environments. These include setting sharing restrictions for canvas apps, utilizing AI to generate app and solution summaries, and enforcing best practices with solution checker\u2014eliminating the need for manual solution checking. This initial suite of rules is just the beginning, with plans to expand in the near future, providing Microsoft Power Platform administrators even greater control over their environment groups.  <\/p>\n\n\n\n

By joining a group, an environment automatically follows all of the group\u2019s rules. You don’t need to set it up manually. This makes sure that all environments in the group are aligned with the basic standards from the start. To ensure that each environment in an environment group maintains the configuration settings determined at the environment group level, the administrators of those single environments within the group will not be able to alter those settings and fall out of compliance with any configured rules. \u00a0<\/p>\n\n\n

\"\"<\/figure>\n\n\n\n

Why is default environment routing important? <\/h2>\n\n\n\n

Thanks to environment groups, these environments come preloaded with essential admin settings, including sharing limits and solution-checker, making adoption a breeze for Microsoft Power Platform admins. Previously, new makers had to figure out which environment to work in. With default environment routing, this decision happens automatically. Default environment routing<\/a> is a feature that automatically directs new makers to their personal developer environments instead of the default environment.\u00a0<\/p>\n\n\n\n

Personal developer environments are individual workspaces, similar to Microsoft OneDrive, where makers can confidently build apps and solutions using Microsoft Dataverse without worrying about others accessing their work, assets, and artifacts. Admins no longer need to be concerned about makers accidentally working in the default environment, where their work might conflict with others. <\/p>\n\n\n\n

When combining with environment groups and rules, these environments come preconfigured with environment-level governance settings, including sharing limits and solution checker. This feature helps new makers to avoid confusion and conflicts when working in Microsoft Power Platform and helps admins to manage their environments more easily. <\/p>\n\n\n\n

What are the key points to remember? <\/h2>\n\n\n\n