web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Blocked by Data Loss P...
Power Automate
Suggested Answer

Blocked by Data Loss Prevention Policy

(0) ShareShare
ReportReport
Posted on by Microsoft Employee
Hi Team,
 
I am planning to create an automation for listing some records from ServiceNow using Power Automate, while adding an action, I am using an authentication type OAuth2 and when submitting client ID and client secret of ServiceNow, I get an error: 
Failed to create connection for connection id '/providers/Microsoft.PowerApps/apis/shared_service-now/connections/shared-service-now-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'. Connection creation/edit of 'shared_service-now' has been blocked by Data Loss Prevention (DLP) policy 'Personal Developer (default)'.
 
Could someone please help me to resolve this issue?

Regards,
Pragya
PowerAutomate.png
I have the same question (0)
  • Suggested answer
    Fredrik_A Profile Picture
    3,644 Super User 2026 Season 1 on at
    Hello,
     
    you need admin permissions to change this, but you can do it by going to:
     
    Power Platform admin center -> Data -> Data policies and then edit the policy named Personal Developer (default).
     
    The reason its blocking you is because the connector is blocked by the policy, you need to remove it from the "Blocked" ones. 
     
     
    If my response solved your issue, please mark it as ✅ Accepted Answer and give it a like.
  • Suggested answer
    11manish Profile Picture
    2,426 on at
    This error is not a technical configuration issue with your Client ID or Secret; it is a governance restriction.
     
    The error message—Connection creation/edit of 'shared_service-now' has been blocked by Data Loss Prevention (DLP) policy—means that your Power Platform administrator has explicitly placed the ServiceNow connector in a restricted or blocked category within the "Personal Developer (default)" environment's data policy.
     
    Why this is happening
    Data Loss Prevention (DLP) policies are designed to prevent data from being accidentally moved between "Business" and "Non-Business" environments. In a "Personal Developer" environment, admins often apply strict default policies to ensure users don't inadvertently connect sensitive corporate data (like that in ServiceNow) to unauthorized third-party services.
     
    How to resolve this

    1. Contact your Power Platform Administrator
    You cannot resolve this yourself unless you have administrative rights to the Power Platform Admin Center. You need to contact the person who manages your tenant's Power Platform environment and provide them with the following details:
    The Policy Name: Personal Developer (default)
    The Connector Name: ServiceNow
    The Intent: Explain that you are building an integration and need the ServiceNow connector moved to the "Business" (or "Allowed") data group within that specific policy.
     
    2. Verify the Environment
    Sometimes users accidentally try to build flows in a restricted "Personal" environment when they should be working in a designated "Development" or "Sandbox" environment where the DLP policies are more permissive. Ensure you are building in the correct environment assigned to your project.
     
    3. The "HTTP" Workaround (Advanced)
    If your administrator refuses to change the DLP policy, you can sometimes bypass specific connector restrictions by using the generic HTTP with Microsoft Entra ID (formerly Azure AD) connector (or the basic HTTP connector if that is allowed).
    How it works: Instead of using the dedicated "ServiceNow" connector, you use the HTTP connector to make direct REST API calls to the ServiceNow endpoint.
     
  • Suggested answer
    PD-10031035-0 Profile Picture
    Microsoft Employee on at
    Thanks both for your prompt response. I don't have the permissions to edit the policy Personal Developer(Default) via Power Platform Admin center. I will open a support request with the Power Platform team and hopefully the issue with policy get resolved.
     
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the April Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Vish WR Profile Picture

Vish WR 707

#2
Haque Profile Picture

Haque 475

#3
Valantis Profile Picture

Valantis 456

Last 30 days Overall leaderboard