Set up Microsoft Exact Data Match - Sensitive Info Type Setup

This is the final video in the series on building an EDM solution using Microsoft Purview. In this video, we will set up the Sensitive Info Definition that uses EDM. I will cover creating the SIT using XML, and cover the key decisions/items that go into your policy design.
L I N K S
MSFT Doc
learn.microsoft.com/en-us/mic...
Git Hub Design
github.com/dougsbaker/Public-...
github.com/dougsbaker/Public-...
C H A P T E R S
00:00 Intro
00:41 Create an EDM SIT Rule Pack using XML
14:59 Upload Rule Pack
17:06 Test EDM SIT / Diagnosing Issues
20:45 Adding EDM SIT to Data Loss Prevention Policy
22:55 EDM Primary Match Issue testing
28:22 Wrap Up

[@skywalk3rcodm917]

This is impressive 👍🏻

[@2tempests1hearld]

Hey Doug! I wanted to say that I came across your videos while trying to figure out how in the world to deal with Microsoft DLP. Thank you for the content and the work you put in. I know one more sub isn't a big deal in the grand scheme of things but I hope it helps and keeps you encouraged to keep making such informative and topical videos on a crazy expansive and complicated product

[@DougDoesTech]

Thanks Eric! The kind words mean a ton!

[@Arte-MMN]

Hi Doug, very nice video series, help a lot to understand EDM. One question, can this be configure only in the tenant_? I mean every xml that you configured locally, can be done everything just using the office365 tenant EDM feature? thanks!

[@DougDoesTech]

Yes since I made this video they now have an option for configuring in the gui. So no need to do the xml.

[@coryhogan8667]

Hey Doug!
This video helped me understand the back end much better.
I see in your final code you went back to the original classifier WITH the keyword (string below). Was this indeed the final solution? I am having the same issue - though I often find the throttling can take up to an hour or so to reflect the changes. Curious if you found the issue elsewhere and it was not a keyword issue.

[@DougDoesTech]

Hey Cory, sorry I forgot to put the update in. It was a throttling issue. I didn’t give enough time from making the edit to it going live. When I went back and checked later it all worked fine.