The issue only happen when a flow calls "Run Child Flow" action.
But it was working few weeks ago.
If I remove the action "Run Child Flow", the error message go out.
I tried to add a connector to the DLP in admin console, but there is no connector called "Flow", that should be the same type of the action "Run Child flow".
Someone can help?
Check your child flow steps and actions steps. Compare with DLP config. The error indicates one of the action is violating the policy.
Thanks for the answer...
Actually, the child flow is tested and turned on, without errors or policy broken.
It driven me to think that there is a problem with the action "Run Child Flow", or a special policy to enabled/disabled this kind of solution.
PS: All the flows is inside the same solution in the same environment.
I worked around this issue eliminating the 'Run a Child Flow' from the flows.
When the actions of child flow is running inside the parent flow, the DLP violation does not happens.
Check out the winners of the recent 'Can You Solve These?' community challenge!
Join us for an in-depth look at the new Power Automate features and capabilities at the free Microsoft Business Applications Launch Event.
Features releasing from October 2020 through March 2021
Fill out a quick form to claim your user group badge now!