Hi @ArunAnthony ,
Keep us posted as to how you get on with reviewing DLP Policies as per Krishna's advice.
We’re also working on improving the experience i.e. with regards to saving a flow that violates the company's DLP Policies. The generic error message does not inform users of which connectors are responsible for the DLP Violation. The Generic Error Message while trying to save the flow - Your flow was created, but it is currently suspended since it uses a combination of connectors that conflict with the company data loss prevention policies or billing restrictions.
On the other hand, when we try to Activate the Flow (from flow properties page or flow list page), we get a much better Error message that provides the names of the Connectors responsible for the DLP Violation
Configured data policies prevent activation of flows which use the '{0}' and '{1}' connectors.
The Flow Definition in the response to the POST/PATCH call indicates that the Flow is suspended (state:Suspended) and the FlowClientSuspensionReason Code. It does not contain any metadata or Error message that includes the names of the Connectors responsible for the DLP violation.
For the START Operation (Flow Activation), the Error response message does contain metadata that gives us the names of the connectors that are responsible for the DLP violation. So we can display these in the Error Message ribbon.
New Expected Experience:
The RP should pipe through the names of the Connectors responsible for the DLP Violation in the response of the POST/PATCH Operation as well. The UX should then consume this and display the same message it displays for Activate Operation.
Cheers,
Allan
-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved. If you like my response, please give it a Thumbs Up.
