Announcing major DLP enhancements for Power Automate and Copilot Studio

DLP (Data Loss Prevention) for Power Automate enables administrators to manage data access from both cloud and desktop Power Automate flows, as well as agent flows in Copilot Studio. Administrators configure Data policies to permit or restrict connectors and actions from being accessed by flows.

We are thrilled to announce a series of recent enhancements to DLP for Power Automate and Copilot Studio, which significantly bolster governance, scalability, and usability across both cloud and desktop automation scenarios.

How does DLP for flows work?

DLP for Power Automate and Copilot Studio is currently generally available for all users. The feature can be accessed from the Power Platform Admin Center, where administrators can create and manage Data policies.

DLP evaluation occurs when editing and saving a flow or when policies are updated.

When a policy change is implemented, flows that do not comply with the Data policy are automatically suspended, and connections to blocked connectors are disabled.

Recent changes that you can now use in your organization

Trigger configuration

Administrators can now block triggers in the same way they can block actions in the DLP configuration experience (triggers are tagged with [TRIGGER]). This provides greater control over which triggers can be used within your organization.

Endpoint Filtering Public Preview for Browser Automation

A new Endpoint Filtering capability is in Public Preview. Endpoint filtering allows administrators to define the websites desktop flows can access by configuring the Browser Automation connector in Data Policies —an essential control for high-risk automation scenarios. Application-level filtering via UI Automation will follow soon this summer.

Environment variable

Use environment variables to migrate application configuration data in solutions. Environment variables are now supported in endpoint definitions, using the @environmentVariables(“environmentVariableName”) pattern.

For example, an SMTP endpoint can be allowed using @environmentVariables(“smtpEndpoint”),587 where the environment variable is defined as smtp-mail.outlook.com.

Recent improvements that make your organization more secured

Runtime Enforcement

We have completed the rollout of support for runtime enforcement as of June 2025. This ensures that Data policies are consistently enforced not only at design time but also during execution.

Automatic reactivation of cloud flows

Policy updates can be disruptive, and administrators may occasionally revert updates that have unexpected effects. We have modified how policy rollout works to now activate compliant cloud flows that had been suspended in the previous 7 days due to policy violations, instead of disabling them. This makes it easier and faster to restore the state of a previous policy version.

Improve performance for large tenants and policies

We have recently strengthened our backend systems to better handle large-scale policy changes with smarter job throttling and improved detection strategies, reducing the time it takes for policy updates to take effect.

The post Announcing major DLP enhancements for Power Automate and Copilot Studio appeared first on Microsoft Power Platform Blog.
Source: Microsoft Power Platform