Any new connectors will automatically blocked unless they are non-blockable.Īpply the DLP Policy to only the default environment.Ģ. Set the default group for the default environment to blocked. Then move all blockable connectors to the blocked category. Move all non-blockable connectors to the business category. They cannot be blocked from creating apps or flows so it is important to restrict their capabilities. Many arrive at the default environment with no prior-training. Safeguard The Default Environment With A Restrictive DLP PolicyĪll users with a standard Power Apps/Power Automate license have access to the default environment with the Environment Maker role assigned. Do Not Use Power Platform DLP Policy Resource Exemptionsġ. Update The Governance Error Message With An Admin Contact 8.

Create A Blanket Power Platform DLP Policy For The Entire Tenant 7. Check Before Changing The DLP Policy For An Existing Environment 6. Use A Shared Power Platform DLP Policy For DEV-TEST-PROD Environments 5. Fine-Tune Connector Endpoints And Actions 4. Set A Power Platform DLP Policy For Each New Environment 3. Safeguard The Default Environment With A Restrictive DLP Policy 2.

In this article I will share 8 Power Platform DLP Policy best practices and help you build a strategy to prevent data-leakage.ġ. DLP Policies prevent makers from accidentally exposing data to 3rd party services that should not have it. They are essential to put in place for every environment. Power Platform DLP Policies determine which data connectors can be used by apps & flows in an environment and which connectors are blocked.

Rental default letter to tenant