Hi there,
This is a common challenge when governance and DLP policies are tightened. SharePoint is often blocked in these scenarios because it is frequently categorized as a "Non-Business" connector, while Synapse and Logic Apps are strictly "Business/Enterprise."
A highly viable and professional solution, before committing to a full migration to Logic Apps, is using Azure Service Bus as your bridge:
The Workflow: The Synapse pipeline (or an intermediary Logic App) sends a message to an Azure Service Bus Queue or Topic.
The Trigger: In Power Automate, use the native Service Bus trigger: "When a message is received in a queue (auto-complete)".
Why is this the best path forward?
DLP Compliance: The Service Bus connector is typically classified as "Business" in enterprise DLP policies. This allows it to reside within the same policy group as Synapse and other premium connectors you are likely using in your flow.
Resilience and Reliability: Unlike SharePoint, which was not designed as a trigger bridge, Service Bus is an enterprise-grade messaging service. It ensures no execution is lost during high-traffic spikes or transient failures, as messages are persisted in the queue until successfully processed.
Architectural Decoupling: This moves your solution toward an Event-Driven architecture, removing the overhead and limitations of using UI-based layers like SharePoint lists for backend triggers.
As a secondary alternative, if licensing permits, using Dataverse as the intermediary layer—triggering the flow when a new row is added—would also keep the process within the "Business" data group.
Hope this helps steer the project in the right direction!
