Block a Connector in a Specific Power Platform Environment Using DLP Policy

Quick Answer

The requirement to block a connector in one environment while leaving it available in another is a textbook case for environment-scoped DLP policies rather than any global setting, because DLP policies in Power Platform can be assigned to specific environments rather than applied uniformly across the whole tenant. By classifying the SQL Server connector as Blocked within a policy and assigning that policy only to the production environment, the connector becomes unusable there while the development environment, which has no such policy applied to it, continues to have normal access. This works because DLP classifications such as Blocked, Business Data Only, and No Business Data Allowed are policy-level settings, and a policy's effect is entirely determined by which environments it's assigned to, meaning the same connector can be treated completely differently in two environments simply based on which policies target each one. This is different from restricting a connector everywhere or relying on security roles, which govern user permissions rather than which connectors are usable at all. The pattern to recognize on future questions is that whenever a scenario needs a connector to behave differently across environments rather than tenant-wide, the answer almost always involves creating or scoping a DLP policy to the specific environment or environments where the restriction should apply.