You’re offline. This is a read only version of the page.
Announcements
We are changing connectors runtime enforcement to include Triggers in addition to Actions.
When this will happen:
This will be rolling out starting February 17th and will be globally enabled by March 14th, 2025.
How this could affect your organization:
Customers who have created data policies with connector action control (Connector action control - Power Platform | Microsoft Learn ) that defines a set of allowed actions and blocks all other actions will also now be blocking non-specified triggers. Triggers can be added to the policy via PowerShell and will soon be visible in the data policy user interface as well for easier management.
If a trigger is not specified in your policies that limit connector actions, those triggers will start to fail at runtime in Power Automate with an error related to DLP Policy configuration.
What you can do to prepare:
Administrators can refer to this documentation article (Identify blocked Power Automate flows from data policies - Power Platform | Microsoft Learn) on how to get an inventory of your flows and how to proactively add those triggers that are in violation of your policy to the appropriate policies.
If you have any questions, please ask here and we'll answer them along with updating the guidance to clear up any confusion. Thanks!
Share
Report
All responses (
Answers (
522
