My main use case for Microsoft Purview Information Protection is sensitivity labeling. I use it for exposing labeling for inside Teams, outside Teams, and similar applications.
Microsoft Purview Information Protection offers sensitivity labels, automated classification, and encryption to protect data across platforms while integrating with M365, Azure, and AWS to prevent unauthorized access and enhance data governance.

| Author info | Rating | Review Summary |
|---|---|---|
| Director, Network & Cloud Infrastructure at a legal firm with 501-1,000 employees | 4.0 | I use Microsoft Purview Information Protection mainly for sensitivity labeling, which simplifies policy enforcement, though limitations in AI classification, scalability, and occasional instability hinder efficiency; setup and licensing are also confusing, but overall, it integrates well within our Microsoft ecosystem. |
My main use case for Microsoft Purview Information Protection is sensitivity labeling. I use it for exposing labeling for inside Teams, outside Teams, and similar applications.
My favorite feature about Microsoft Purview Information Protection is how it applies to everything generally, so I don't have to do it manually. I set a policy and then it applies. When my teams create individual teams, I don't have to worry about them sharing information that they should not or that they cannot. It also notifies end users with labels and tooltips, which I appreciate.
I evaluate the role of sensitivity labels in guiding AI interaction as pretty good, but for us, it's too general. It says, "Here's a dataset," and because it's in this folder, it's just going to apply this label. It would be much nicer if it could analyze the content and say, "This is attorney-client privilege. This is company restricted," rather than applying labels based on folder structure, since my patch notes for a server are not the same as another company's.
Having AI in Microsoft Purview Information Protection is going to be very important for me because our datasets are so large that we're not going to be able to do the classification ourselves. In order for us to use Copilot and expose any data, I have to do the sensitivity labeling first. That's a big task, and the users managing the data are not going to do the work.
I have not had much luck or much experience with the comprehensiveness of the data classification abilities in Microsoft Purview Information Protection, including identifying categories and sensitive information. The information we had at the time just showed that it's going to read all of our information and apply its own set of labels, which scares management. Once you apply the label, how do you get it off? And how do you go back and check the work? You can't.
I believe what can be improved in Microsoft Purview Information Protection needs to be more precise to my needs. One feature I'd have appreciated that doesn't exist yet is related to what another attendee shared with me. He works for a larger company with a lot more data, and the classification limit of 100,000 just does not work for him because he produces well over 100,000 documents a day.
I've been using Microsoft Purview Information Protection for about two years, as they've renamed it, though I've been using Purview for DLP and policies.
Regarding the stability and reliability of Microsoft Purview Information Protection, there have been problems, such as the one with US East that impacted us. There was one recently where many of our vendors were running on Azure, and they had a global issue. I think it was with DNS or something related to that, and it affected us as well.
There have been more global problems than isolated ones. Since identity is where everything is based, if that goes down, you're screwed. Making that more resilient to DNS failures would be great.
Being able to scale is important.
I should clarify that I didn't consider another solution that was cloud-based. We have a product, a DLP, that is just host-based and client-based rather than cloud-based. So we would not have had an opportunity to deploy that structure out to the cloud. This was our only shot.
I don't know how to honestly quantify the return on investment from having Microsoft Purview Information Protection. I don't do the spend and the math because we're forced into the E5 licensing.
It has the potential to save us a lot of time, but it's just not there yet.
Regarding the experience of pricing, setup costs, and licensing for Microsoft Purview Information Protection, it's confusing. Knowing what I have to do for add-ons, I have to buy SCUs, and that's sometimes confusing. It could use a lot more clarity, and there's not a lot of good VARs out there that truly understand it. The local Microsoft representatives are swamped with those types of questions, and things are changing all the time. I just can't keep up.
Microsoft Purview Information Protection integrates with the other security tools that I use because we're a Microsoft shop, so we're E5 and across the board.
I have all the products, and that's fantastic. I'm in the ecosystem using everything, but we're still a very traditional workplace with a lot of our data on-premises. A lot of operations are still on-premises focused solutions versus being more mobile and more open, with traveling people and those situations.
We do have our own APIs that we use for Microsoft Purview Information Protection. We write our own, and some of that is exposed. Some of our applications do use the APIs to communicate with the cloud services. However, we're not a big publisher; we don't publish a lot of APIs. There are a few that we publish, and a few that we consume, but that's it.
My overall rating for Microsoft Purview Information Protection is 8 out of 10.
| Product | Mindshare (%) |
|---|---|
| Microsoft Purview Information Protection | 1.9% |
| Collibra Platform | 8.6% |
| Microsoft Purview Data Governance | 7.8% |
| Other | 81.7% |
| Company Size | Count |
|---|---|
| Small Business | 5 |
| Midsize Enterprise | 2 |
| Large Enterprise | 11 |
| Company Size | Count |
|---|---|
| Small Business | 159 |
| Midsize Enterprise | 82 |
| Large Enterprise | 214 |
Microsoft Purview Information Protection supports compliance with regulatory standards through features like data loss prevention and intuitive DLP rules. It integrates with multiple platforms such as M365, Azure, and AWS for extensive data protection. The platform helps manage sensitive data through automated labeling and effective policy deployment. While there are areas needing improvement like third-party integration, API support, and policy enforcement consistency, Purview remains a powerful tool for businesses to assess data usage and reduce unauthorized access.
What are the key features of Microsoft Purview Information Protection?Companies across various industries implement Microsoft Purview Information Protection to apply sensitivity labels to emails and cloud content like OneDrive and SharePoint. It's utilized for data classification, loss prevention, and governance. Microsoft partners use it for SAP integration and compliance assessments, while consultants focus on protecting and managing data efficiently for clients centered around Microsoft solutions.
Microsoft Purview Information Protection was previously known as Microsoft Information Protection.