Custom DLP XML Generation and Importing

This script will create the custom XML file for a custom DLP Template to be used in Exchange 2013 or Office 365 DLP.  The script will create the entire file, top to bottom.  It will also import the XML if requersted and even create a transport rule (testes in 2013 only).  There i

448 times
Add to favorites
E-mail Twitter Digg Facebook
Sign in to ask a question

  • Australian Centrelink Reference Numbers
    2 Posts | Last post January 31, 2019
    • Hi Damian,
      I have downloaded your script and was able to generate the expression using Regex site and import to Office 365 (it is on Security & Compliance PowerShell now and not Exchange Online anymore).
      It was generating a lot of false positives though as the format is N[9]A[1] which comes up as part of many random numbers.
      Any suggestions on how it could be adjusted to match only when there is a " " or ":" in front of it and improve accuracy with keywords such as "Centrelink", "CRN", etc.?
    • I see this question is now nearly a year old, but if it helps, consider Nucleuz ( for custom DLP sensitive types & policies.
  • REGEX warning or error?
    1 Posts | Last post March 01, 2018
    • Hi,
      I have manually created an XML but found my DLP rule does not do what I expect.  I found this script, which is great for building the structure of the XML.
      I have copied my regex expression (below)
      When I enter this I get the message *** NOTE *** This script cannot validate the RegEx expression you entered.
      I'm not sure if this is an error or warning.  I have used the regex site to validate the format and this seems happy.
      Also I'm not sure if there if the regex should contain that I don't want the words to be case sensitive of the XML content.  I haven't had any prompts for this.
      Any help appreciated.
      Thanks for the script though, this could save a lot of time.  I just need to get my head around my regex stuff I think :)