Flow Connector missing from DLP Rules

[Michael_Thorne]

Hi all,

I'm writing a parent flow that will call a child flow (both flows in a solution).

The Parent Flow uses the Office 365 Email connector. 

When I put the Office 365 Email connector in the business category in DLP, the parent flow then complains about DLP violation.  If I move it to non-business category the DLP violation goes away.

However, I can't find a Flow connector to also put in the business category. 

Maybe it's called something else?  Does any one else know?

Thanks.

[PrasadAthalye]

Which connector is Suppling data to Office 365 Email Connector? Each Connector that is used in this email action should be moved along with it to business so that they can communicate with each other.

Like and Mark this as answer if it resolves your issue.

[Michael_Thorne]

Hi,

The "Office 365 Outlook" connector is is trigger to the parent flow and it is feeding data into the flow.

As I am trying to debug my test flow pair is cut down to bare minimum.

Parent Flow:

Office 365 Outlook trigger -> Run a child flow

Child Flow:

Manual Trigger -> Initialise Variable -> Set Variable -> Respond to a PowerApp or Flow

In my personal development environment I just need "Office 365 Outlook" and "HTTP" in the business category for this work correctly, but in my "real" production environment I'm still getting a DLP issue when attempting to turn on the parent flow (the child flow is already turned on) with both these in the business category.

[TrutzStephani]

The "Trigger child flow" activity works internally as an HTTP connector. Therefore you get the DLP error, if the HTTP connector is not in the business scope as your other connectors.
It's a known issue and hopefully solved soon:
Call Child Flows - Power Automate | Microsoft Docs