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 Apps / Format of $NewPolciyOb...
Power Apps
Unanswered

Format of $NewPolciyObject

(0) ShareShare
ReportReport
Posted on by 1,302

HI

 

In Set-DlpPolicy what is the format of a $NewPolciyOBject ?

I cannot find any documentation for it.

 

Thanks

 

Nigel

 

I have the same question (0)
  • Joel CustomerEffective Profile Picture
    3,224 on at

    were you not able to get your policy created after this? https://powerusers.microsoft.com/t5/Power-Apps-Governance-and/Creating-a-DLP-Policy-using-PowerShell-I-get-asked-for/m-p/603327#M2715

     

     

  • Joel CustomerEffective Profile Picture
    3,224 on at

    One reason why most people don't just use powershell to manage their dlp policies is there are new connectors all the time, so updating your powershell for each connector is not realistic. I like to use the DLP manager in the COE starter kit combined with setting the default category for new apps.

  • NPrice99 Profile Picture
    1,302 on at

    HI @jlindstrom 

     

    new-dlppolicy now only has the environment type.

     

    Set-dlppolicy has the updatedPolicy object (see screenshot)

     

    Dont new connectors go automatically into the Non-Business list  of a DLP ?

     

    Regards

     

    Nigel

    set-dlppolicy.JPG
  • NPrice99 Profile Picture
    1,302 on at

    HI @jlindstrom 

     

    I currently have 32 environments each with its own DLP to look after so having to go to the DLP Editor for each DLP when a new connector comes out will be a pain in the backside.  The reason for this is there is one environment for each Project which may create one or more PowerApps.  If One project needs access to a another connector(with the appropriate business justification) then I just need to update one DLP and it will not affect any other Projects.  If after time, we find that a number of projects have the same connectors in their DLPs we might look at combining the DLPs into one.

     

    I think it is better to have a PowerShell which goes around all of the DLPs and adds the new connector into the non-business list (and optionally if possible to be blocked) of all of the DLPs.

     

    Regards

     

    Nigel

     

     

  • Joel CustomerEffective Profile Picture
    3,224 on at

    New connectors automatically go into whatever your default group is. That could also be the new blocked group.

     

    even with 32 environments you can probably simplify this more using the global with exceptions policy And rather than maintaining 32 different sets of policies have one main one based on your base policy and then per environment exceptions.

     

    also are you sure that you need 32 different environments? Some may be able to share the same environment

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

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 June Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 296 Most Valuable Professional

#2
11manish Profile Picture

11manish 224

#3
Valantis Profile Picture

Valantis 181

Last 30 days Overall leaderboard