Hidden DLP policies block Power Apps connector combinations
Reviewed by Helen Jones
A newly published Collab365 problem report documents Power Apps makers reaching a data loss prevention (DLP) policy block only after designing apps around SharePoint, Dataverse, or custom connectors. Microsoft confirms that applicable tenant and environment policies are evaluated at design and runtime, and the most restrictive connector grouping wins.
Citizen builders usually choose connectors around the workflow, but governance evaluates the combined connector set inside a specific environment. A technically sensible app can therefore become non-compliant late in the build, creating redesign and admin delays. Makers cannot override tenant policy, but they can surface the risk earlier. Recording the environment, planned connectors, data types, and business reason gives an admin enough context to approve an exception or suggest a compliant design.
Analysis
Before adding the next connector, list every connector and data source plus the target environment, then ask your Power Platform admin whether that combination is permitted. If it is blocked, request either an approved exception or a named fallback connector or environment before building further.
Source note
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "Hidden DLP policies block Power Apps connector combinations", Collab365 Spaces.