16Hello everyone,
I have encountered a behavior in one of our environments that I do not fully understand and would like to know whether others have observed the same thing.
We have a DLP policy called "example-DLP" that blocks the use of the OneDrive for Business connector.
When creating a flow using the Standard Harness, I cannot use the trigger "When a file is modified" because the platform correctly reports that the connector is blocked by the DLP policy.
However, when I create what appears to be the same flow using the GitHub Copilot Harness, I am able to select the same trigger, save the flow, and successfully execute it. The flow runs as expected despite the DLP restriction that prevents it in the Standard Harness.
My questions are:
- Is this expected behavior?
- Are DLP policies evaluated differently in the GitHub Copilot Harness compared to the Standard Harness?
- Has anyone seen similar differences with other connectors?
- Could this represent a governance or security concern if certain connectors can be used despite DLP restrictions that apply elsewhere?
I would appreciate any clarification from the community or Microsoft regarding the intended behavior.
Thank you.
