Microsoft Purview Data Loss Prevention Reviews

The purpose of the solution is connected to the fact that we use the whole Microsoft suite. We use the DLP mostly, but we also use Defender which comes with the Microsoft license.

Up until now, we have used it to investigate everything, what's going on and whether people are sharing data, but mainly for monitoring. There are just a few things that are being blocked right now.

Purview has helped significantly to reduce the number of solutions we need to interact with each other. It's one suite for everything, which is very good.

We can also see compliance in real time. There's great visibility into data governance. That's one of the strongest points. We have 100 percent compliance with legal regulations around the globe. That's very good. It has notably improved our ability to stay on top of compliance. It's not all companies that are 100 percent compliant.

In addition, the time needed to respond to insider threats has decreased. It's very easy to know everything that's going on right now. I have all the controls to see what's being shared everywhere, around the world. If we see something that looks odd, we reach out to the folks involved immediately. It's almost instant. It has reduced our insider threat response time by more than 60 percent.

It is 

• very easy to use
• very easy to learn 
• very well documented

and the community is great as well.

The UX is very good. It's easy to get around inside that tool, and it's easy to get help.

I don't think it's very different from other solutions regarding the features, but because everything is on Microsoft and we use Azure, integration with the product is easier. That's the most important thing when you use many Microsoft products. It's easier to integrate everything in one place.

It's very important that it collects data from non-Microsoft products if we need information about what's going on with other OSs. If we're talking about personal computers, especially employees' computers, they are mostly going to be Windows. But if we're talking about servers, they are mostly Linux.

Purview is also built to take into account regulations from the US, Brazil, Europe, Asia-Pacific, et cetera. This is very important as well because you have to take into account the intricacies of each legal system.

Another good feature is the education it provides to users on how best to handle sensitive data.

There is no AIP for Linux systems. That's a setback. Another thing it's lacking is libraries to work with Python. It has libraries for C# and C++, for example, but not for Python and, these days, Python is very useful.

Power Automate can be improved as well. You can do plenty of things with it but it still doesn't do everything that you have in a full development language. It doesn't have that flexibility.

I would also like more integrations in Power Automate. Because so many things are a premium with Power Automate, you cannot do everything. There are a bunch of integrations that you have to pay more to use. That's not very good.

I have been using Microsoft Purview Data Loss Prevention for one year and three months.

So far, we have not had an outage. It seems like a 99.9 SLA.

It's a SaaS solution, so everything is in the cloud in one place. It's scalable if you're all Microsoft, but if you have Linux, I wouldn't say it's that scalable. You might have to do some work.

We have about 70,000 users. It's a global solution for everyone in our organization.

I have never used the technical support of Microsoft. But the documentation is good, very clear, very easy to use, and in one spot. We find whatever we are looking for.

For DLP, I used Symantec in another organization. In this organization, we used to use McAfee DLP. We switched mainly because of the price. Microsoft provides a bunch of tools for a fixed price, so there are other features that come with that suite of tools.

I believe we have seen return on investment because new engineers know their way around very fast. When I joined the company, it took me just one month to make my way around everything. It's easy to get our hands dirty and start working.

Despite some setbacks regarding the premium features for automating and integrating in Power Apps—you can only use the handiest stuff if you pay a premium price—there are many good things that come with the license that we already have. There is training as well; we can attend as much training as we want. They also provide good support. Overall, the pricing is okay.

The fact that Purview works across multi-cloud and multi-platform environments, is important, in spite of the fact that we mainly use Microsoft and Azure cloud. It's good if we plan, in the future, to move to another cloud service. Also, it's good that Purview can connect to iOS, Mac, and Android devices. The more tools we can integrate the better, because it enables us to scale very fast, even though right now we don't use it on iOS and those other systems.

Purview is still very new for us, even after one year. We're still looking into how things can be done. We're a global company and there are many policies and many different laws across the globe. Sometimes we can't do everything we could theoretically do with the tool. It's a powerful tool but we are still discussing legal matters across the globe.

Regarding maintenance of Purview, we just check if it's up to date and what updates Microsoft has provided. But we don't have to do too much.

I started working with this tool one year ago and I'm really impressed with its capabilities. I have worked in other banks and we had to use so many things to get one thing done, so I have a positive impression of Purview. I would definitely recommend trying it.

We basically use it to track personal identifiable information. We are also using it to label any confidential, company trade secret, and internal data. We have an internal use policy and a confidential use policy to encrypt the documents.

The auto-labeling feature is definitely the most valuable feature. It goes in and labels the documents for you in different repositories. It covers the Outlook and Exchange repositories along with SharePoint and OneDrive. It is really helpful in those areas.

There is a lot of ambiguity when you are setting up labels, such as sensitive information labels. It is a little daunting at first if you don't have prior knowledge, and there is a little bit of a learning curve for setting up the labels.

Some of the setup wizards could be more helpful from an AI perspective. They can streamline the setup through more AI technologies so that you don't have to jump through so many hoops and different menus and dropdowns. It would be useful to have a setup wizard that is more hands-off and engaging for setting up the information type labels. If you tell them this is what we're trying to protect, it should basically start to lead you down that path of best practices. Such a feature would be great.

It is absolutely stable. A part of the success criteria was to not have any stability issues. It seems very responsive after you get through the deployment aspect of it.

We have been adding more label information types, and it seems to scale well. I don't see any issues there. This part of the solution is built into the Microsoft Cloud ecosystem. Therefore, you don't really have any sort of quota or cap on your data. It seems to be going really well on that front.

Currently, we have about 600 users. We're going to continue on this Microsoft journey. There is another feature that we're looking at called the Purview feature, which is basically adding the same sensitive info type tagging for data in your Microsoft SQL databases. We are currently looking at using that.

Their technical support is excellent. We've had some hiccups here and there regarding the setup. We contacted Microsoft, and they were very quick to respond with solutions. The online Microsoft documentation is also kept fairly up to date, which has been another plus. Its documentation is really well done.

It was fairly complex because it has a very wide and broad gamut of sensitive info types. Each of the labels and sensitive input types that we created took four to six hours of initial setup and work. The deployment itself is pretty instantaneous, but getting the data back and actually seeing the labels and sensitive info types come back in the form of data tagging definitely takes some time. Depending on the size of your repository, it can take longer to scan the data and label it while going through all the algorithms. It probably took a good two to three days to actually see some meaningful data.

It is a part of our Microsoft licensing. We pay for a yearly renewal. Its price is reasonable for the size of the organization we are. It is fairly competitive, and you get what you pay for. We have an E5 license, and a part of understanding the E5 license is to see what all you get with it. If you really look at it from that standpoint, you get a lot of value. You have Defender and all its security features in there as well.

Their licensing is fairly flexible. They have different programs. We've seen ones where you could pay for up to three to five years in advance. There is also a monthly pay-as-you-go type of deal, but we're doing a yearly renewal and fixing the budget.

We didn't evaluate any other product because it was just way too convenient. It is a part of our Microsoft licensing, so we were already paying for it. There wasn't anything appealing to try a third-party solution or anything like that.

I would advise others to definitely go to the documentation first and plan ahead. It is definitely something you plan, and it definitely requires a kind of a crawl-walk-run approach, so you definitely want to plan for it. I would also suggest taking advantage of the testing and reporting features that are available to be able to do a pilot and test it before you actually deploy it.

I would rate Microsoft Endpoint DLP a nine out of ten. There is a little area for improvement, but it is definitely the best in class.

With this product, you can protect your data from getting out of the company, or falling in the wrong hands. You protect your data leakages. It's a very huge subject. It's very important.

The main part I like about it is, that quite a few of the DLP features are built into the latest server operating systems. The reliability of these is good and there's a good amount of documentation in case you run into any problems. They work well. 

The setup is straightforward. 

VM people say you cannot use just one product; you need multiple products across the network and you have to deploy to the backups.

The DLP could always be better.

Overall, they should make their Hyper-V and the clustering more stable. VMware offers very good clustering, for example. Microsoft needs to improve a lot in terms of stability.

Technical support is awful.

I've used the solution for almost 10 years.

The solution is very stable and extremely reliable. There are no bugs or glitches. It doesn't crash or freeze.

The solution has been very scalable. 

As an integrator, we don't have a single client. We have so many clients. The average number of users can be as low as 100 and can go as higher 1,000. It varies. Not everyone implements DLP. A basic level of DLP is implemented, however, it is a very niche implementation and DLP is done only if someone has to be compliant. For example, a company might need either an SSA 2018 certification or SOC 1 Type 2 certifications. 

You can troubleshoot easily via documentation, which is readily available. 

Technical support seriously needs work. They are not helpful at all.

Microsoft has kind of become a monopoly now and there are so many users. They are more interested in selling the products. They're not interested in supporting them. Unlike the other companies who have at least a ticket system, here, when you are a monopolistic company, you don't care. You know the products will sell, and people will buy them.

Negative

You have the full encryption file and folder, however, for that, we use a different product. We don't use Microsoft. BitLocker has given us encryption features, however, we don't use that. Mostly, we prefer McAfee for that.

The initial setup is pretty straightforward. I see a lot of improvement on the installation part when compared to earlier days when it was a little bit tough. Right now, the documentation is good and implementation is not taking that much time. You're up and running quickly. The final aspects might require additional time, however, 80% of it you finish pretty fast. 20% of the time is when you want to fine-tune, depending on your site requirements There it might require an extra effort.

There are some products that are available on a subscription basis. Predominantly, what I use is the one that comes with the operating system and I use other third-party products basically to cover anything that's missing.

We are an integrator as well for Microsoft DLP.

Our deployments are mostly on-premise or private cloud, not on the public cloud.

Overall, I'd rate the solution a seven out of ten.

We use Microsoft Purview Data Loss Prevention for the entire life cycle and not just DLP. That is, we use it for discovery, classification, and DLP.

Earlier, our customers had no control at all over compliance, and confidential documents that were going out were not at all looked into. Microsoft Purview Data Loss Prevention has been a huge benefit to our clients in this regard.

I like the whole value proposition of Microsoft Purview, particularly the DLP and integration with external solutions.

Purview's natively integrated compliance across Azure, Dynamics 365, and Office 365 is important to us because it's all about compliance.

Organizations have various compliance policies including the regulatory policies that are defined within the organization and those for a particular region. Therefore, it is important to our organization that Purview is built taking into account critical regulations from around the world.

This solution enables our clients to show compliance in real time and has helped them in their meetings with compliance regulators.

Purview Data Loss Prevention provides presentations to educate users on how best to handle sensitive data. When the user doesn't know whether a document should be classified under a certain label, Purview will provide suggestions or will auto-classify the particular document. It has automatic labeling capabilities.

It's important that Purview provides data protection for iOS, Android, and data in other SaaS apps because our customers have heterogeneous environments. Purview perfectly fits into the heterogeneous space.

Purview has reduced the number of solutions needed to interact with each other and has coexisted with them. Some customers have completely replaced their solutions with Purview, and others have Purview for classification labeling and a third-party solution for the DLP verdict.

It has helped our clients to reduce the time to action on insider threats because it can be integrated.

I would like Microsoft Purview Data Loss Prevention to be on the source code or SQL databases. It is difficult to do classification and labeling when you have a third-party source code or a third-party Oracle database. It is seamless when it comes to Microsoft documents but is not so with third-party source codes. Microsoft needs to work on it a little bit more.

Everybody wants information protection, but not all of them can afford the M365 license. I would like Purview to be a standalone product or solution.

We've been working with this solution for the past three years.

It is definitely stable.

Our clients are medium to large organizations, and Microsoft Purview Data Loss Prevention has to be a scalable solution for them.

Overall, Microsoft's technical support is good, and I would give them a rating of six out of ten.

Neutral

The initial deployment is straightforward. We can quickly configure the policies, but the classification and labeling take time.

The solution does require monitoring.

Microsoft Purview Data Loss Prevention is part of a bundle and is not sold as a standalone product.

I recommend Microsoft Purview Data Loss Prevention and rate it at nine on a scale from one to ten.