FIX Microsoft Purview DLP Mistakes in 10 Minutes or Less!

[@patrick__007]

Created a DLP for Teams (like in your examle) a while ago. The DLP is in simulation mode, but after two weeks there are still no records found. Great video!

[@peterrisingM365]

Think I just answered your same query in another comment. Two weeks eh. That's way too long. I would suggest checking for policy conflicts first. If there are none, perhaps log a ticket with MS Support.

[@Maurexianer]

Hi Peter, I try to create the EDR/DLP solutions. These solutions work with "stored fingerprints (hashes) on Sharepoint 365 Office Doc. Library, block upload sensitive data to sharepoint. My Secret DB contain: CLIENTNUMBER,TEAM,SEGMENT,CLIENTNAME. Is necessary to create a Database MySQL in this case? Store the sensitive data in a relational database like Azure SQL or MySQL

[@peterrisingM365]

It sounds like you're working on a robust EDR/DLP solution to protect sensitive data on SharePoint 365. Given that your Secret DB contains sensitive information such as CLIENTNUMBER, TEAM, SEGMENT, and CLIENTNAME, it's crucial to store this data securely. Using a relational database like Azure SQL or MySQL is a good approach for storing sensitive data. Both options offer strong security features, including encryption at rest and in transit, access controls, and compliance with various industry standards. Here are some considerations for each option: Azure SQL: This is a fully managed relational database service provided by Microsoft. It integrates seamlessly with other Azure services and offers advanced security features like threat detection, auditing, and data masking. It's a great choice if you're already using other Azure services and want a fully managed solution. MySQL: This is an open-source relational database management system. It can be hosted on various platforms, including Azure, AWS, and on-premises. MySQL offers flexibility and control over your database environment. If you prefer an open-source solution and have the expertise to manage it, MySQL can be a good fit. Both options are capable of handling the storage and security requirements for your sensitive data. The choice between Azure SQL and MySQL will depend on your specific needs, existing infrastructure, and preference for managed versus self-managed solutions.

[@simple-security]

I wonder why there isn't a matrix of use DLP cases which provide the basics, eg: policy name, data source dependency, application dependency

[@peterrisingM365]

This may help a little.