<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Data Loss Prevention - Tag - shellgio.net</title><link>https://shellgio.net/tags/data-loss-prevention/</link><description>Data Loss Prevention - Tag - shellgio.net</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 16 Jul 2026 20:16:05 +0100</lastBuildDate><atom:link href="https://shellgio.net/tags/data-loss-prevention/" rel="self" type="application/rss+xml"/><item><title>A quick way to copy the conditions of a DLP rule with PowerShell and the AdvancedRule parameter</title><link>https://shellgio.net/quick-way-copy-dlp-rules-conditions/</link><pubDate>Thu, 16 Jul 2026 20:16:05 +0100</pubDate><author>xxxx</author><guid>https://shellgio.net/quick-way-copy-dlp-rules-conditions/</guid><description><![CDATA[<div class="featured-image">
                <img src="/assets/images/quick-way-copy-dlp-rules-conditions.png" referrerpolicy="no-referrer">
            </div><p>Sometimes the easiest way to build a complex Microsoft Purview Data Loss Prevention rule is not to start from scratch. You may already have a rule whose conditions, classifiers, and nested logic are exactly what you need for a lab, a backup, or a similar deployment in another tenant.</p>
<p>This is where the <code>AdvancedRule</code> property can be very useful.</p>
<p>In this post, I will show you how I <strong>extract the condition logic from an existing DLP rule</strong>, remove a few properties that can cause portability problems, save the result as JSON, and use it with <code>New-DlpComplianceRule</code>.</p>]]></description></item></channel></rss>