Skip to content
Tutorials Center
My learning

Topics

Lesson 33 of 38 ยท Governance and Patterns

Data Loss Prevention and Governance

Understand how admins keep automation safe: DLP policies with Business, Non-business and Blocked connector groups, why a flow gets suspended, security practices, and a lightweight governance model.

Power Automate puts powerful tools in the hands of everyone, and that is exactly why companies govern it. A well-meaning employee could build a flow that copies customer records from a company database into a personal cloud storage account, or posts a confidential file link to a public service. Data loss prevention (DLP) policies stop such flows at the connector level. As a flow author you need to know how they work, because they explain the error "your flow violates a data policy" that appears on otherwise correct flows. As an admin or team lead, you need to know how to design a sensible policy and a practical governance routine.

Admin pages are not available on this site, so the steps are described in words; the example is a stand-in that models the policy check.

What a DLP policy does

A DLP policy sorts connectors into groups, and then enforces a rule: a flow (or app) may use connectors from one group only, not mix Business and Non-business connectors.

Group Meaning
Business Trusted connectors that may touch company data (SharePoint, Dataverse, Outlook, Teams, SQL Server in a typical policy)
Non-business Connectors for personal or untrusted use. Default group for connectors you do not classify
Blocked Connectors nobody may use in the covered environments

If a flow has a SharePoint action (Business) and a Dropbox action (Non-business), saving it or turning it on fails with a data policy violation; the flow is suspended until the conflict is removed. A flow using only Non-business connectors, or only Business connectors, is fine.

flowchart LR
    A["SharePoint<br/>Business"] --- F{"Flow"}
    B["Dropbox<br/>Non-business"] --- F
    F --> V["Violation:<br/>cannot mix groups"]

Mixing groups is the check. A single-group flow passes.

Scope of a policy

  • Tenant-level policies apply to all (or most) environments of the organization.
  • Environment-level policies apply to selected environments only, which lets a trusted Finance environment allow more than the Default environment.
  • When several policies apply, the most restrictive combination wins: a connector blocked by any policy is blocked.

A common design: strict policy for the Default environment (few connectors in Business, the rest Non-business or Blocked), relaxed policies for dedicated, managed environments where flows are owned and reviewed.

Finer controls

  • Connector actions: for some connectors, individual actions can be blocked (for example allow reading but block deleting).
  • HTTP and custom connectors: the generic HTTP connector can call anything, so many policies place it in Blocked or Non-business. Custom connectors can be classified by their URL pattern, so an approved internal API can sit in Business while others stay blocked.
  • Endpoint filtering: allow or block specific destinations for connectors such as HTTP, SQL, or Azure Blob.
  • Managed Environments: a premium admin feature set with sharing limits, usage insights, weekly admin digest and solution checker enforcement.
JS Stand-in: does this flow violate the policy?

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

No output.

If your flow is blocked

  1. Read the message: it names the policy and the connectors in conflict.
  2. Decide whether the design is wrong or the policy is. Often the fix is to replace a Non-business connector by an approved one (OneDrive for Business instead of Dropbox).
  3. If the flow is truly needed, ask the admin to review a policy exception or move your work to an environment with a suitable policy. Do not try to bypass DLP with workarounds such as sending data to your private mailbox; that defeats the purpose and breaks policy.

Security practices for authors

  • Least privilege: use accounts and connections that can reach only what the flow needs.
  • Do not share connections casually: if you share a flow and its connections, other people can act with your identity. Prefer run-only with "provided by run-only user" credentials where the design allows it.
  • Secrets: never put passwords, API keys or tokens in action fields or in Compose actions. Use environment variables of type Secret (backed by Azure Key Vault) or connectors that manage the credential. Turn on Secure inputs and outputs for actions that handle sensitive values.
  • Personal data: know what data your flow stores in run history (28 days) and logs, and who can see it. Mask or avoid sensitive fields.
  • Triggers from the outside: an HTTP request trigger has a URL with a signature key; treat it like a password and restrict who can call it where the platform allows. Never publish it in public code.
  • Review before sharing: flows that email externally, call external APIs or move files out of the company deserve a second pair of eyes.

A lightweight governance model

You do not need a heavy process to avoid chaos. A practical model:

Area Practice
Environments Default for personal, dedicated environments for team and business-critical flows
Policies Sensible DLP groups, reviewed every quarter
Ownership Every flow has two owners or a team; orphaned flows are reassigned
Inventory The admin center and the Center of Excellence (CoE) Starter Kit list flows, makers, connectors and usage
Lifecycle Delete unused flows; require a review for flows with many users
Training Short onboarding for makers about DLP, secrets, naming and where to ask
Support A named channel or mailbox for questions and incidents

The CoE Starter Kit is a free collection of solutions from Microsoft that inventories environments, makers and flows, flags orphaned or high-risk items, and automates nagging emails. It is a good starting point once adoption grows.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. A flow uses a SharePoint action (Business) and a Dropbox action (Non-business). What happens under a DLP policy that sorts them that way?

    A flow may not mix connectors from the Business and Non-business groups.
  2. 2. Why is the HTTP connector often blocked or restricted?

    HTTP can send data to arbitrary destinations.
  3. 3. Where should an API key for a flow be stored?

    Secrets must not sit in plain text in the flow definition or run history.
  4. 4. When several DLP policies apply to an environment, which rule applies?

    A connector blocked by any applicable policy is blocked.

Summary

  • DLP policies group connectors as Business, Non-business or Blocked; a flow may not mix Business and Non-business, and Blocked connectors cannot be used.
  • Policies apply at tenant or environment level; the most restrictive combination wins.
  • If your flow is blocked, redesign it with approved connectors or ask the admin; do not work around the policy.
  • Protect secrets, limit sharing, minimize personal data in run history, and keep two owners per flow.
  • A light governance model: environments, policies, inventory, ownership, lifecycle and support, with the CoE Starter Kit as help.

Next: Flow Patterns That Scale