Enable the enforcement of DLP policies to include child flows
Important
This content is archived and is not being updated. For the latest documentation, go to What's new in Power Automate?. For the latest release plans, go to Dynamics 365 and Microsoft Power Platform release plans.
| Enabled for | Public preview | Early access | General availability |
|---|---|---|---|
| Admins, makers, marketers, or analysts, automatically | 
Feb 20, 2023 |
- |
Apr 10, 2023 |
Business value
With this feature, admins have their data loss prevention (DLP) policies enforced into child flows, and blocking the HTTP connector won't block child flows.
Feature details
Currently, data loss prevention (DLP) policies aren't enforced into child flows. Because of this, admins can block the HTTP connector if they want to block child flows. Unfortunately, this has the side effect of also blocking child flows if the HTTP connector needs to be blocked for some other reason.
With this feature, DLP policy enforcement includes child flows. If a violation is found anywhere in the flow tree, the parent flow is suspended. After the child flow is edited and saved to remove the violation, the parent flows can be resaved or reactivated to run the DLP policy evaluation again.
This feature will roll out slowly using the DLP change process with design-time and full enforcement stages. A change to no longer block child flows when the HTTP connector is blocked will roll out with full enforcement of DLP policies on child flows when this feature reaches generally availability.