Security & Compliance

    Power Platform governance for apps, flows and agents.

    Every app, flow and agent on the Power Platform gets an environment, approved connectors and an owner. Changes reach production through a pipeline.

    For companies whose departments build their own apps and flows, and whose IT wants to know which of them the business now relies on.

    • Power Platform Admin Center
    • Managed Environments
    • Power Platform Pipelines
    • Dataverse
    • Copilot Studio
    • Entra ID
    Three fenced gardens on a slope, each an environment with apps, flows or an agent, a rail leads from the test to the production garden
    01

    An app moves house

    A member of the logistics team built an app for material orders in the default environment, and by now the whole department orders through it. In the admin center inventory your IT sees the app with its owner and connectors. It moves as a solution into the logistics environment, and the next change goes through the test environment and an approval into production.

    02

    Guardrails for everyone who builds

    The rules apply to every environment in the tenant; building stays with the business teams. It starts with the inventory: what exists, who owns it and which connectors it uses. From that come environments, policies and change paths that your IT adjusts on its own after handover.

    • Environment strategyThe default environment stays for personal productivity, a department's workflows get their own environments for development, test and production, and environment groups give them shared rules. New makers are routed into a developer environment of their own.Result: every app has a place that fits its purpose and its audience.
    • Data policies for connectorsIn the Power Platform admin center we sort connectors into the Business, Non-business and Blocked groups and set where new connectors land. Advanced connector policies work as an allowlist that admits only approved connectors and actions and can block entire MCP servers.Result: data from SharePoint or the ERP flows only into services your IT has approved.
    • Managed EnvironmentsProduction environments get sharing limits for apps, flows and agents, a solution check before import, a weekly usage digest and a welcome message for everyone who builds there.Result: the environments that matter have guardrails, and licence needs are known before the switch.
    • Change paths with pipelinesApps and flows live in solutions, a pipeline takes them from development through test to production, and a responsible person approves before production. Connections and environment variables are set per stage, and earlier versions are kept in the pipeline host.Result: only what has been tested and approved reaches production, and every deployment is logged.
    • Inventory and Center of ExcellenceThe inventory shows apps, flows and agents with environment, owner and connectors, including the resources of people who leave the company. A small board decides on new connectors, environments and exceptions.Result: your IT knows what runs, who owns it and what a changed connector affects.
    • Makers and licencesA request path for new environments, guidance on the rules right where people build, and training for the people in business teams who create apps and flows. Plus an overview of which environment requires which licences.Result: business teams keep building, and licence costs can be planned.
    • Compliance and evidenceAn environment's region decides where its data is stored; what runs globally, such as preview features or names in the admin portals, we record in the environment concept. Dataverse auditing logs changes to records, sharing and roles with retention as you set it, and access in production environments appears in the Purview audit log.Result: on request you can show where the data lives and who changed what.
    03

    What is settled before the first policy

    A person with the Power Platform Administrator role and, for each area, someone who decides on environments and exceptions. A list of the apps and flows your workflows rely on; the inventory supplies the rest. A decision on whether the default environment becomes managed, because that determines who needs a premium licence. And your existing licences, so we can set the need against them.

    04

    Where your IT reads the state

    Environments and environment groups as agreed, with data policies that demonstrably block a test app using a blocked combination. One solution that has gone through a pipeline with approval from development to production. An inventory export with owners and connectors, and a short rulebook for everyone who builds. Following up on new findings can be handed to Support & Operations.

    What you receive from us

    The monthly report on your apps and flows.

    Every month you see which apps and flows were added, who owns them and what the data policies stopped. Shown here as a sample with invented figures.

    Monthly report

    Sample

    Power Platform monthly report

    Customer
    Muster AG, Bern (fictional)
    Reporting month
    October 2026
    Scope
    Five environments, two data policies
    Contact at CNEXT
    Named in the real report
    • 143apps and flows in the inventory
    • 9new this month
    • 4flows with a new owner
    • 1connection stopped by policy

    Summary

    In October nine apps and flows were added, all in their department's environment. Four flows had no active owner after someone left; the HR department named new owners. The data policy stopped a flow that was meant to copy files to a private cloud storage. Two flows that expense reporting relies on moved to the finance environment after review.

    EnvironmentPurposeApps and flowsIn October
    DefaultPersonal workflows of employees617 new flows, all within the policy
    FinanceExpenses and payables272 flows moved in from Default
    ServiceOrders and technician app311 new app after acceptance
    HRJoiners and leavers144 owners reassigned
    TestAcceptance before go-live101 app under review

    Open items

    • The technician app gets a pipeline from Test to Service in November, so changes only go live after review.
    • The department whose flow was stopped now stores the files in its SharePoint site.

    Next steps

    Next report in the first week of November. Your IT approves new environments and exceptions to the policies.

    Samples with invented details for a fictional Muster AG.

    Sound familiar? Tell us where you stand today.

    Contact

    What's new.

    As of: 9 October 2026

    • As of 31 August 2026

      From February 2027, apps in managed environments open only with a licence.

      Anyone using an app in a managed environment needs a standalone licence such as Power Apps Premium or Power Automate Premium, including for apps with standard connectors. Since June 2026 people without a qualifying licence see a notice in the app; from February 2027 the app no longer opens for them. A report in the admin center lists the people affected.

      Source: Microsoft Learn: Licensing requirements for managed environments
    • As of 7 May 2026

      The CoE Starter Kit is no longer being developed.

      Microsoft no longer actively maintains the Center of Excellence Starter Kit and no longer handles issues for it. Its core capabilities are in the Power Platform admin center: inventory, usage, monitoring and recommendations under Actions, complemented by the API, the CLI and the admin connector.

      Source: Microsoft Learn: CoE Starter Kit transition to Power Platform admin center
    • As of 29 September 2026

      Pipelines require managed target environments.

      From October 2026 the admin center flags pipeline deployments to unmanaged target environments. Administrators have 30 days to approve switching the environment to managed, with one possible extension; after that the pipeline blocks further deployments to it. The pipeline host and environments of the developer type do not need to be managed.

      Source: Microsoft Learn: Overview of pipelines in Power Platform

    Governance for every platform.

    The same questions in three environments: who owns what, who can reach what and how you prove it.

    • Governance

      Microsoft 365

      Ownership, lifecycle and sharing for sites and teams, Purview labels and the sharing review before Copilot.

      Microsoft 365
    • Governance

      Power Platform

      Environments, connector data policies, pipelines and an inventory of every app, flow and agent.

    • Governance

      AI/SI

      Agent inventory, data in Copilot, prompt logs and the legal frame for AI in Switzerland.

      AI/SI

    Before the first data policy takes effect.

    Should we make the default environment managed?

    That depends on licences. In a managed environment everyone who uses an app or flow there needs a premium licence, including for simple apps on SharePoint lists. So the default environment often stays unmanaged with a strict data policy, and workflows a department relies on move into their own managed environments.

    What happens to existing apps when a data policy takes effect?

    The platform checks every app, flow and agent against the new policy, suspends violations and disables connections to blocked connectors, usually within an hour. So we first check in the inventory which resources use which connectors, inform the owners and only then switch the policy on.

    Do we still need the CoE Starter Kit?

    An existing installation keeps running but is no longer developed. Inventory, usage, monitoring and recommendations now come from the admin center itself, and we build custom reports on the inventory API. Microsoft has also announced agents that prioritise findings and propose remediation plans for approval; the preview was planned for September 2026. The Center of Excellence as a board stays: people who decide on exceptions.

    May business teams keep building on their own?

    Yes, and that is what the rules are for. With routing, everyone who starts building gets a developer environment of their own with preconfigured sharing limits. Building and testing there works without a premium licence; whoever uses the app day to day needs one. When an app becomes important to the department, it moves as a solution into the department's environment.

    Which licences cover managed environments?

    Power Apps Premium, Power Automate Premium, Copilot Studio, Power Pages and the Dynamics 365 licences with premium use rights, plus the pay-as-you-go meters for Power Apps, Power Pages and Copilot Studio. Per person, one of the two premium licences is enough for both apps and flows. The Developer Plan does not cover use in managed environments.

    How do an external partner's changes reach production?

    Through the same pipeline as your own. The partner develops in its development environment in your tenant, a responsible person on your side approves the deployment, and the solution is installed under a service principal. Pipelines work within one tenant; deploying across tenants is done with Azure DevOps or GitHub.

    Agree on a useful next step

    Tell us about your current workflow, the systems involved and the result you need. In our first conversation, we identify what else we need to know to plan a useful next step.