Loss Prevention (DLP) policy

To resolve the issue with the Data Loss Prevention (DLP) policy 'PWRPLTF_All_Environments' preventing your journey from being published, you will need to identify the specific actions or connectors in your journey that are violating the DLP policy. Here are some steps you can take:

1. Review the DLP Policy: Check the details of the 'PWRPLTF_All_Environments' DLP policy to understand which actions are restricted. This will help you identify which parts of your journey are causing the violation.
2. Modify Your Journey: Once you know which actions are blocked, you can either remove those actions from your journey or replace them with actions that comply with the DLP policy.
3. Test the Changes: After making the necessary adjustments, try to publish your journey again to see if the issue has been resolved.
4. Consult with Admin: If you're unsure about the DLP policy details or how to modify your journey, consult with your administrator who manages DLP policies in your organization.
5. Run Diagnostics: If the problem persists, consider running a diagnostic for DLP policy tips in the Microsoft 365 admin center to analyze the DLP policy and rule configuration for your journey.

Following these steps should help you address the DLP policy violation and successfully publish your journey.

Hi @jeremyaoliver

Thank you for contacting to Microsoft QA.

It seems you're facing an issue where your journey couldn't be published due to a Data Loss Prevention (DLP) policy called 'PWRPLTF_All_Environments'. This can happen when the DLP policy is restricting certain actions that your journey is trying to perform.

Here are some steps you can take to address this issue:

Review the DLP Policy: Check the specifics of the 'PWRPLTF_All_Environments' DLP policy. Ensure that the actions your journey is trying to perform are allowed under this policy. You may need to modify the policy to permit these actions if they are incorrectly restricted.

Policy Author Role: Ensure you have the necessary permissions to make changes to the DLP policy. You will need the policy author role at the root-collection level in Microsoft Purview.

Data Source Registration: Make sure that the data source you're working with is registered in Microsoft Purview for data use management. This is crucial because DLP policies act on registered data sources.

Publishing the Policy: If you've made any changes to the DLP policy or if you created a new one, remember that publishing the data owner policy is a necessary step. Your policy statements will remain in draft mode until published.

Monitoring and Logs: Utilize the Microsoft Purview Audit solutions to identify if there were any specific actions that were blocked by the DLP policy. This can provide insight into what exactly triggered the issue.

Hope this helps you resolve the error! If you're still having trouble, please feel free to provide more specific details about what actions you're trying to take, and I can assist further.

References:

• Policy Creation - Data Policies
• Data Loss Prevention Overview
• Microsoft Purview Service Description