DLP Error resolve

Question

how to resolve DLP ERROR to automate web page?how to resolve DLP ERROR to automate web page

Answer 1

Hi Guman, Rajendra

Have you got the chance to review the AI Answer suggestions? If you haven't already, please give those a try and see if it helps.

In addition, you should closely review the flow run details or designer error banner, as it typically identifies the exact action or connector causing the violation, this helps narrow down what needs to be adjusted.

If your automation involves a browser step (e.g., opening or interacting with a web page), check whether endpoint/browser-level controls are restricting automation (such as managed Edge policies or restricted URLs), as these can also trigger DLP-related blocks even when the flow design looks correct.

Where changes are required but not permitted in your environment, document the business justification and required data movement clearly before escalation, this increases the likelihood of approval when reviewed by the security or admin team.

If the issue persists after aligning the flow and validating the trigger point, only a policy review or exception at the admin/security level can fully unblock the scenario.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Resolving a DLP (Data Loss Prevention) error when trying to automate a web page depends on where the DLP policy is enforced. In Microsoft environments, DLP is typically enforced through Power Automate / Power Platform, Microsoft Purview DLP, or endpoint/browser controls. When DLP blocks automation, it means a policy is intentionally preventing data from flowing to or from that web page or connector.

For web automation via Microsoft tools, the main resolution paths are:

1. If using Power Automate / Project Roadmap or related flows
   • Roadmap and related flows require several connectors to be in the same DLP group (Business or Non-Business) in the default environment:
     1. Microsoft Dataverse Connector
     2. Legacy Microsoft Dataverse Connector
     3. Roadmap for Project Connector
     4. Project Online Connector
     5. Azure DevOps Connector
   • If a DLP policy separates these connectors into different groups or blocks one of them, flows will fail with DLP errors.
   • Resolution requires a Power Platform admin to:
     1. Go to Power Platform admin center → Data policies.
     2. Edit the relevant DLP policy for the default environment.
     3. Move all five connectors into the same group (either all Business or all Non-Business) and ensure none of them are in the Blocked group.
   • Existing roadmap rows created before the change may still show errors; new rows should work after the policy is corrected.
2. If using Power Automate Desktop flows for web automation
   • Desktop flows are governed by DLP policies that classify action groups as Business, Non-business, or Blocked.
   • A DLP error occurs when:
     • A flow mixes Business and Non-business action groups in the same flow, or
     • The flow uses actions or action groups marked as Blocked.
   • To resolve:
     1. Open the desktop flow in the Power Automate for desktop designer.
     2. Identify actions flagged in the DLP error (for example, Database actions vs Excel actions, or Email actions if they are blocked).
     3. Delete or disable the actions that violate the policy:
        • For Business vs Non-business violations, remove all actions from one of the conflicting groups.
        • For Blocked actions, remove or disable every action that is marked as blocked.
     4. Save the flow again; the DLP violation banner should clear and the flow will no longer be suspended.
   • If the desktop flow is called from a cloud flow, the cloud flow will also be suspended until the desktop flow’s DLP violations are fixed and the desktop flow is reselected in the cloud flow.
3. If the DLP policy is managed centrally (Purview / security team)
   • DLP is designed to prevent sensitive data from being sent to untrusted sites or services. If automation of a web page is blocked by DLP and the automation genuinely needs to handle sensitive data, only an administrator can change that:
     • Contact the organization’s Microsoft 365 / security / Power Platform admin.
     • Provide details of the flow, the target website, and the exact DLP error message.
     • The admin can then adjust the DLP policy (for example, move connectors into the same group, or change a blocked action/connector) if this aligns with organizational security requirements.

If the goal is to automate a web page that handles sensitive information, any change to DLP should be made by an admin with full awareness of the data protection implications.

---

References:

• Facing Project Roadmap DLP error? Here's more information about it.
• Data loss prevention (DLP) policies
• Understand Data Loss Prevention (DLP) in Microsoft Edge for Business
• Configure endpoint data loss prevention settings
• Use the Microsoft Purview Data Loss Prevention migration assistant for Symantec and Forcepoint