What is our primary use case?
Our main use cases for Microsoft Purview Data Loss Prevention are to classify confidential documents, including our company secret, company confidential, private confidential, users' private data, HR data, financial data, and our IT own data.
What is most valuable?
When we utilize Microsoft Purview Data Loss Prevention, it benefits our organization, especially when sending and receiving attachments labeled as confidential. It is quite helpful for executives to confidently send emails knowing that the message will not be forwarded, printed, or shared. That trust is pretty helpful for us in IT, and also in OneDrive and SharePoint, wherever users find documents that have sensitive data. We can ensure that a wrong user opening up will not happen, and we can stay confident that nobody is going to open it.
I appreciate the new feature of Microsoft Purview Data Loss Prevention where Copilot automatically classifies documents in SharePoint, OneDrive, and everywhere with personally identifiable information data, and I would like to see that automatic feature in action.
Microsoft Purview has helped improve our organization's ability to discover sensitive data significantly as we use eDiscovery Purview, which is incredibly helpful.
The automatic tagging feature of Microsoft Purview Data Loss Prevention is an incredible feature that I saw as a big improvement. I think that making the rules, eDiscovery, and policy rules a little bit easier for first-time users would be terrific.
What needs improvement?
Regarding Microsoft Purview's classification and policy controls, while I'm not sure about productivity, it has been incredibly helpful for legal, HR, and finance by ensuring that all documents are labeled correctly so nothing is viewed or shared by anyone else, preventing any information from being leaked to the press or anything else. I wouldn't call it productivity, but it's definitely helpful for our company.
I do not currently utilize the machine learning-driven analysis offered by Microsoft Purview, but I am interested in using it after seeing the Copilot automated feature.
I assess Microsoft Purview Data Loss Prevention's ability to prevent unauthorized sharing of sensitive information positively because we have opened up our SharePoint and some Teams to our partners and customers. We have created policies saying what can be shared with customers when we're communicating in Teams or sharing files. Data classification helps because before a user tries to share, it shows them they cannot share because it contains this information, and the user is happy they have not shared the wrong information.
The challenge with Microsoft Purview Data Loss Prevention involves finding documents, emails, and OneNote with sensitive data. Finding and labeling it is a manual process today, and it is quite messy.
For how long have I used the solution?
I have been using Microsoft Purview Data Loss Prevention for about five years.
What do I think about the stability of the solution?
I would assess the stability and reliability of Microsoft Purview Data Loss Prevention as being flaky at times, where eDiscovery sometimes takes forever or doesn't bring the results we expect. While we use it to delete some emails, Microsoft Purview Data Loss Prevention's eDiscovery sometimes says it deleted them, but we're still finding the emails, so that presents some problems.
I have not experienced any downtime, crashes, or performance issues, though there is some slowness.
What do I think about the scalability of the solution?
I believe that Microsoft Purview Data Loss Prevention scales well with the growing needs of our organization.
While we have expanded usage, it wasn't smooth, as we are mixing and matching our own DLP product with Microsoft Purview Data Loss Prevention, and deciding which features of Microsoft Purview Data Loss Prevention we wanted to use and which ones we want to use from our own DLP was a challenging process, but we figured it out.
How are customer service and support?
I evaluate customer service and technical support for Microsoft Purview Data Loss Prevention as fantastic. Online documentation is pretty good, Copilot is helpful sometimes, and I have never had a problem with support.
On a scale from one to ten, I would rate customer service and technical support an eight because most of the time, we did find an answer through support, but there were instances when support did not respond.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
Prior to adopting Microsoft Purview Data Loss Prevention, I was using another solution to address similar needs.
I was using a product made by a company called Datena for DLP, and for email, we have our own DLP, which is Proofpoint, and that's what we still use.
How was the initial setup?
In terms of deployment, there is nothing to deploy with Microsoft Purview Data Loss Prevention because it already has access to SharePoint, Teams, OneDrive, and email. We just configured it, tested it, and started using it.
What about the implementation team?
I would describe my experience with deploying Microsoft Purview Data Loss Prevention as being in the planning stage of rolling out DLP with our own product along with Microsoft Purview Data Loss Prevention. If Microsoft Purview Data Loss Prevention has a better feature, we're going to end up using that.
What was our ROI?
I have absolutely seen a return on investment with Microsoft Purview Data Loss Prevention.
We save a lot of time for legal by using Microsoft Purview Data Loss Prevention when searching data for legal and HR and employee issues. That is incredibly time-saving since it used to take a lot of time searching for different data across Teams, SharePoint, and email, and now it's all in one place.
Which other solutions did I evaluate?
We did not consider any other solutions before selecting Microsoft Purview Data Loss Prevention.
In my evaluation process regarding Microsoft Purview Data Loss Prevention, nothing stood out to me, mainly because we are a big Microsoft customer, using the entire email, Azure, and all infrastructure, so Microsoft Purview Data Loss Prevention being right there made it a logical choice for us.
What other advice do I have?
My advice for other organizations considering Microsoft Purview Data Loss Prevention is to use it a lot and try to understand Microsoft Purview Data Loss Prevention from their point of view. Understanding how to create policies, rules, and eDiscovery rules first before you start creating your own rules is important. I would rate this review a six overall.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?