Microsoft Data Loss Prevention Review

Definitely the best in class with great stability, competitive price, support for different repositories, and very useful auto-labeling feature


What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

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.

How was the initial setup?

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.

What's my experience with pricing, setup cost, and licensing?

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.

Which other solutions did I evaluate?

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.

What other advice do I have?

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.

Which deployment model are you using for this solution?

Public Cloud
**Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Find out what your peers are saying about Microsoft, Broadcom, Forcepoint and others in Data Loss Prevention (DLP). Updated: August 2021.
535,544 professionals have used our research since 2012.
Add a Comment
ITCS user
Guest