Skip to content
Tutorials Center
My learning

Topics

Lesson 32 of 38 ยท Governance and Performance

Data Loss Prevention Policies and Governance

Understand Power Platform data policies (DLP): Business, Non-business and Blocked connector groups, scope, environment groups, the CoE Starter Kit and governance habits.

Low-code makes it easy for anyone to connect an app to anything. That is the strength and the risk: a well-meaning maker could build a flow that copies customer rows from a database to a personal file-sharing account. Data loss prevention (DLP) policies, now called data policies in the admin center, stop such combinations by controlling which connectors can be used together.

Connector groups

A policy sorts connectors into three groups:

  • Business: connectors for company data (SharePoint, SQL Server, Dataverse, Teams).
  • Non-business: connectors that are allowed but kept separate (social networks, personal services).
  • Blocked: connectors that cannot be used at all.

The core rule: an app or flow cannot use connectors from the Business group and the Non-business group at the same time. It may use several Business connectors together, or several Non-business ones, but never one of each. A Blocked connector cannot be used anywhere the policy applies.

By default, new connectors fall into a configurable group (usually Non-business), so admins review the list when Microsoft adds connectors.

The three groups

Business Company data
Non-business Allowed, kept apart
Blocked Not allowed

Business and Non-business cannot mix.

1 / 2

Creating a policy

In the Power Platform admin center, choose Security (or Policies), then Data and privacy, then Data policy, New policy. You:

  1. Name the policy.
  2. Choose the scope: all environments, selected environments, or all except some. A tenant-level policy plus environment-level ones can both apply; the most restrictive combination wins.
  3. Move connectors between Business, Non-business and Blocked. You can set rules per connector action and endpoint for some connectors (for example, allow only certain HTTP URLs).
  4. Review and create.

Changes apply to apps and flows. Existing ones that now break the rule are suspended or fail at run time with a policy message; makers must change the design.

Evaluating a policy: a stand-in

The grouping rule is easy to model. This stand-in checks whether an app's connector list is allowed under a sample policy. It is a teaching model of the rule, not the admin center.

JS Stand-in: is this connector set allowed?

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Environment strategy and governance

A policy works best when combined with an environment plan:

  • Default environment: strict policy (only Microsoft 365 basics Business, most others blocked) because everyone makes things there.
  • Team or project environments: a broader policy for approved teams.
  • Developer environments: personal sandboxes with a clear lifetime.
  • Production: tightly controlled access and policies.

Environment groups and managed environments add governance features: usage insights, sharing limits (limit how many people an app can be shared with), solution checker enforcement, weekly digests, and IP firewall options. Some of them require premium licensing; check the official licensing page.

Monitoring: the CoE Starter Kit

The Center of Excellence (CoE) Starter Kit is a free set of solutions from Microsoft that inventories apps, flows, makers and connectors in your tenant, with dashboards in Power BI and flows to nag owners of orphaned or unused apps. Treat it as a template you adapt; it needs setup and a dedicated environment.

Roles for administration

  • Power Platform Administrator (a Microsoft Entra role): manages the whole platform.
  • Environment Admin: manages one environment.
  • Environment Maker: may create resources in an environment.

Grant the smallest role that fits. Use groups to control who can create environments or developer environments.

Governance habits that work

  1. Educate makers: a short guide with approved connectors and the support contact.
  2. Offer a safe place to build instead of just saying no.
  3. Review orphaned and unused apps regularly (the CoE kit helps).
  4. Log activity in Microsoft Purview (audit log) for sensitive environments.
  5. Document every business-critical app: owner, data, connectors, support.

A simple inventory report: a stand-in

JS Stand-in: find risky apps in an inventory

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does a DLP (data) policy control?

    Policies group connectors into Business, Non-business and Blocked and restrict how they combine.
  2. 2. May an app use one Business and one Non-business connector together?

    Mixing the two groups is the exact scenario a DLP policy prevents.
  3. 3. Which environment should have the strictest policy because anyone can build in it?

    The Default environment is open to all users, so restrict what connectors it allows.
  4. 4. What is the CoE Starter Kit?

    It is a free template solution set for inventory, dashboards and governance flows.

Summary

  • Data policies split connectors into Business, Non-business and Blocked; the first two cannot mix in one app or flow.
  • Scope policies by tenant, environments or environment groups; the most restrictive result applies.
  • Combine policies with an environment strategy, managed environments and the CoE Starter Kit.
  • Educate makers, offer safe spaces and review inventory regularly.

Next: Delegation and Performance