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

Announcements

Welcome to the Power Platform Communities
News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / If DLPs for PAD can on...
Power Automate
Answered

If DLPs for PAD can only be applied to Managed Environments then is there a way to prevent users from publishing Flows to the Default Environment which for most organizations would not be a managed environment?

(0) ShareShare
ReportReport
Posted on by Community Power Pla... Microsoft Employee

If DLPs for PAD can only be applied to Managed Environments then is there a way to prevent users from publishing Flows to the Default Environment which for most organizations would not be a managed environment? Registry setting perhaps?

Categories:
Power Automate Desktop
  • Verified answer
    momlo Profile Picture
    momlo 1,527 Super User 2024 Season 1 on at

    Hi  

    Not sure what exactly you want to block - the creation of any PAD flows, or restricting them from using specific actions in PAD flows?

    What I know you can do is:

    1. Not managed:

    - Use DLP to block the PAD connector entirely - they will not be able to use the connector in PA, but they are still able to create PAD flows*
    - Use AppLocker to block running PAD on managed computers

    2. Managed:

    - All users need a premium license, so you control who can and cannot access env.
    - Use DLP to block the PAD connector entirely - they will not be able to use the connector in PA, but they are still able to create PAD flows*
    - Use DLP to block selected PAD actions
    - Use AppLocker to block running PAD on managed computers

     

    * afaik, did not verify recently

  • rmatesick-nw Profile Picture
    rmatesick-nw 20 on at

    I, too, have this need due to not wanting to make the default environment a Managed Environment.  Plus, we do not want folks to be able to create desktop flows that can interact with non-approved external services/APIs.  For anyone that wants to take advantage of the Windows use rights with PAD, they will likely save desktop flows to the default environment.  It's quite the risk pickle due to the product/licensing limitations.

     

    If we cannot find a smooth solution to still enable local automation with the base Windows use rights, we may likely need to aggressively block installation & execution of PAD on PCs unless said user has a Premium license.  Even then we will need to likely build custom controls to reactively disable/remove desktop flows from the default environment (and other un-Managed environments).

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

News and Announcements

Welcome to the Power Platform Communities

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the July Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
David_MA Profile Picture

David_MA 227 Super User 2026 Season 2

#2
11manish Profile Picture

11manish 221 Super User 2026 Season 2

#3
Mohsin Ali Profile Picture

Mohsin Ali 132

Last 30 days Overall leaderboard

Featured topics

Known issue with browser automation in Power Automate for Desktop on Google Chrome 146 and 147
Share your ideas and struggles with building Power Automate flows!
Survey: Power Automate mobile app
How to Ask for Help with Your Power Automate Workflow
Start and wait for an approval action
Restore a deleted flow
List of actions cheat sheet for Power Automate Desktop
Welcome to the Power Automate forum!

Product updates

Microsoft Power Platform Community release plans