Showing results for 
Search instead for 
Did you mean: 

Hide/Label connectors that are not enabled for Business Data

When an environment has been created with Data Loss Prevention policy that only allows certain connectors, then the other connectors should not be available (or should be labled) when designing the flow. As currently implemented,  a flow creator can spend a lot of time creating a Flow only to find out that it will be suspended because they used a connector that was not authorized for use.

Status: New
Regular Visitor

We really need this option!

New Member

Aggreed. Why should we subject our Tenet users to create flows and not get an error until they try to save. They should not be able to pick a blocked connector in our tenet.

New Member

I was hoping the admin approach used for TEAMS apps management would be the same for Flow Connectors.


Environments should respect Data Loss Policies applied to the environments where certain Connectors are BLOCKED.

Business and Non-Business connectors should be visible but ideally warn in case the connects are mixed.