Microsoft Purview Data Governance Reviews

I use their information protection labels. 

Information protection labels help us classify and protect data from unauthorized access.

An organization architect has to design the labels to describe the criticality of the data.

For example, we'd put labels and restrictions on certain data, like salary details, which would only be available to HR and certain managers. 

We can also classify policies based on the organization. Workloads and attachments are labeled so that they can not be shared outside of the classification label. 

Data sensitivity is a crucial issue for everyone, especially with remote and hybrid work. Everything has moved to the cloud in the last five or six years. We need to protect our data and the cloud and we do that with our own managed key to ensure DLP.

The labeling is excellent.

The endpoint DLP is very good. They are doing a lot of enhancements there. The DLP features consist of restricting copy-paste, network sharing, and blocking. We can take actions like blocking and warning with custom messaging to the end users. We are able to effectively reduce the data loss through endpoint DLP. 

We also don't have to pay for third-party DLP solutions. 

The OCR feature is really great. They've been improving it. If there is sensitive information in an image, it can be scanned and protected. 

We can prevent, block, or audit however we like. There are activity explorer audit logs that are available for 90 days. 

The solution can be used across Mac, Android and iOS. The support is there if you use those. MacOS does have some different settings, however, I haven't really explored it too much.

Purview is natively integrated with Azure and 365 workloads. We can classify the Azure Infra as well. 

We're using the solution at a large scale. It's important that Purview takes into account critical integrations from around the world. The labeling will automatically classify data that will cover sensitive data. We can make our own classifications on top of that if we need more security. Once the data classification happens in Purview, we can take an extra step if we like. 

The data loss protection is great for remediating policy violations. We have policies configured via labels. We can check in with individual users to see if there are any malicious activities happening. We're extremely confident no one can take data off-site. Even the labels are encrypted. Even if someone takes the data, it's encrypted and safe. 

DLP comes into the picture when a data classification happens. We have to educate the users that we've classified the data based on sensitivity. We enforce DLP policies by forcing users to use labels. If they do not use labels, they cannot, for example, use files for their day-to-day work. We've imposed classification on them. They cannot share or take data without the proper label or access.

Purview has helped us reduce the number of solutions we need to interact with. This fits perfectly with today's data privacy and security concerns. Corporate devices are completely managed through the support of this solution.

Purview has positively affected the visibility we have into our estate. Once the data is classified, you get a complete 360-degree view of it, including where it is and the labels associated with it. With the content explorer, we have eyes on the entirety of our data as it's hosted on the cloud. 

It helps us ensure compliance in real-time. We don't face any issues right now with compliance. Security and compliance are completely in sync, and we've defined the necessary policies. We're audit-ready.  

The solution has helped us know of any insider threats. It's helped us reduce time to action on insider threats by 40%.

While the product doesn't exactly save us money, it does save us time. It's reduced time spent on security by two to three hours. 

There are some non-Microsoft file formats that are not supported. 

While they seem to be focused on Sharepoint and OneDrive, I'd advise that if somebody saves something locally to their hard drive, this should also be classified and protected. 

The DLP has to become more mature now that there are other competitors present in the market.

While the solution went through a name change two years ago, however, I used the compliance security portal for the last three to four years.

The solution isn't completely stable. It's not mature. I'd rate stability six out of ten. There are bugs and glitches. The product is also evolving. They're always adding new features based on feedback and the experience of the customer. They deploy a ton of fixes. 

We have the solution across multiple locations and departments. We have about 2,200 people in the organization, and around 1,700 people use it. 

The solution isn't completely scalable. They are working on it. 

I'm not sure what happened. However, I've noticed, after getting very good support for the last ten years, that, in the last two, the support level has gotten worse. Their engineers don't know the basics of their products. They need to be more knowledgeable and offer a better response time. 

Negative

We did not use anything previously. 

We did testing and a POC for three months until the rollout. We had three to four people working on it. However, one engineer is sufficient with some guidance from Microsoft. One or two engineers would be enough for a complete deployment.  

The implementation process is straightforward. It's not overly complex. 

There is no maintenance needed. Microsoft supports it; if there is any service interruption, they will cover you.

We have witnessed an ROI. We save on costs and do not need to do too much manual work. We've seen an ROI of 17% to 18%.

If you are an organization using Microsoft 365 solutions, it's okay. If you are on Google Solutions and using Google Cloud, it might be costly. Having the complete Microsoft bundle makes it feasible and cost-effective. 

I've heard that Purview and Forcepoint are similar and very comparable.

We're a Microsoft customer.

If an organization doesn't want to spend money on other solutions in the market, I'd recommend Microsoft. Instead of nothing, you'll have something. 

I'd rate the solution seven out of ten. 

I've been using it to help track data from employees or messages. I can use it to see the routing of ongoing and outgoing confidential data. We can audit logs to see the history of particular mailboxes. Auditing has been a very helpful feature. 

It helps with the discovery of overall licenses and security labels. You can find out if any type of security has been triggered or if any type of particular content is being shared with specific users. Using content search, we can manually search for all types of things and see different types of details. 

It helps us with data loss prevention to make sure that nobody actually is accidentally sharing any confidential information, such as legal documents, health information, and personal identity verification numbers. 

They are improving the platform every day, and they are doing a wonderful job now. 

They also include different features. We can pre-enable classification and use enhanced labels. You can create labels to define your data class notifications, such as confidential information. You can create a system keyboard list and a dictionary with sensitivity labels.  

Microsoft introduced a compliance manager to help you find all sorts of things you can do to improve your environment to achieve a higher security score. 

Purview delivers data protection across multi-cloud and multi-platform environments. It is very important. In today's world, most of the things we do are over the cloud. We use many APIs and additional apps in our environment from different vendors. Some of these APIs and apps are being configured over hybrid or multiple clouds. You can audit and monitor all data connectors, and you can configure your database and your database connectors, and all these APIs can be ported to Purview so you can monitor all the information to make sure that it does not leak. You can also encrypt such information to keep it safer.

Purview can connect to iOS, Mac, and Android devices, as well as data and other SaaS apps. We have multiple users who are comfortable with different platforms. Some are on Windows. However, most of the planning teams have iOS-based devices. We like that it is supporting all these platforms and making all those devices and data flow to it. 

It is very easy to learn the interface, and it is very user-friendly. It is really helpful for us to be able to monitor and use Microsoft since it is such a strong tool for analyzing our database.

We use the solution for data loss prevention. One of the features includes this configuration template that we can use for default government policies. You can create a policy for server migration that needs some of the custom configurations, and we do have templates for payroll and inventory. We can use the DLP to educate users on policies and let them know what shouldn't be shared. We can send suggestions about how they can send certain information.

Purview enables you to handle compliance in real-time. It runs in the background and you can engage with it when you get real-time alerts. It's helped us reduce the time needed to act on threats. Instead of manually auditing, we get notifications and can see things highlighted in our dashboards. We've reduced the time to action by about 20%.

I'd like to see them improve the training for implementing this type of solution. If we need particular things, we need to be able to understand how to implement them right away, and not wait days or weeks. 

I've been using the solution for the last four years in different companies. 

It's very stable. 

We have the solution across multiple locations in India. We have ten to 15 engineers working directly with the solution. Then we have around 2,000 active users and are scaling up.

The level of support you get depends on various scenarios. Sometimes you need help from engineers in a different time zone, like the US for infrastructure. 

Positive

The solution is deployed completely on the cloud. We have an enterprise subscription. It's a pretty standard implementation. However, there are some configurations you need to handle initially. For us, we did a migration and then handled some configurations since we moved over to the cloud. 

Implementations are easy, and I appreciate the support Microsoft provides.

For some features, you do need a specific license. For smaller organizations with 200 to 300 employees, it might not make sense to get an enterprise license. However, the pricing is good for the requirements it meets. 

I'm a customer. 

We're not using the AIfunctionality yet. However, we are leaning into it to see how we can implement it in the future. 

I'd rate the solution nine out of ten. 

We use Microsoft Purview to protect and govern our information.

It is important for Microsoft Purview to provide data protection across multi-cloud and multi-platform environments, including AWS and GCP. I have been a consultant for a year and a half, advising mostly European enterprise customers. All customers, from mid-sized to larger, have diverse storage solutions. Therefore, it is important for Microsoft Purview to be flexible enough to be applied to various environments, such as multi-cloud. Although the product is not yet there, it is important to many business customers.

The enterprise IT landscape is diverse, with various devices, SaaS applications, and multi-cloud solutions. Protecting and governing information is a need that spans all of these touchpoints and Microsoft Purview helps us do that.

Purview's native integration with Azure Dynamics 365 and Office 365 is essential because many organizations use these Microsoft products. This native integration is unmatched by other solutions.

Purview DataOps Protection does a great job of remediating policy violations. It has a comprehensive reporting and fine-tuning integration that allows us to track policy violations effectively. Overall, I think it does a great job of protecting data.

Purview recently improved in the area of DLP. These tips are now available across different platforms, such as Office and Outlook, and they are getting better. This is helpful in educating users about policies. 

Microsoft Purview helped us control the growth of data, reduce dark data, and better protect against the filtration of data.

Purview increased our visibility into our other Microsoft solutions.

We use AI and automation sparingly. This is not part of Purview directly, but an AI tool that helps us determine if data is redundant or has business value before we move it to Azure or Microsoft 365. We use the AI tool in a very limited way, such as trainable classifiers. We also have the option to use another product called Syntex in collaboration with Purview, but this has not been explored much.

Technically Purview can enable us to show our compliance in real-time.

Purview reduced the time it takes us to act on insider threats by almost 90 percent. Previously, many violations were not reported or took months to be reported. Now, we can act on violations almost instantly, or within days.

Microsoft Purview partially helps organizations stay on top of compliance. The platform provides a number of technical features that can be used to manage compliance, but it is up to organizations to implement these features and take the necessary steps to ensure compliance.

Microsoft Information Protection uses sensitivity labels to classify and protect sensitive information. MIP works together with Data Loss Prevention to prevent sensitive information from being leaked outside of the organization. MIP also helps to mitigate insider risk by preventing unauthorized users from accessing sensitive information.

Purview's data connectivity platform has a good set of connectors for ingesting data from non-Microsoft data sources. However, it still falls short in terms of coverage of other systems. It is mostly integrated with the Microsoft stack, but there are connectors to other systems and sources of information. Overall, Purview is not a one-stop shop for protecting company information.

I am not sure that Purview was built with compliance guidelines in mind. It does have a component called Compliance Manager, which allows us to track our adherence to different standards, such as security and privacy standards around the globe. However, this is more of an add-on. I think there is still a significant gap between the technical capabilities of Purview and the ability to drive compliance or prove compliance through its use. I think this is a major gap that Microsoft does not adequately address. Purview is not a GRC tool. It is a set of security features, labeling features, and lifecycle features that do not come close to GRC tooling in terms of functionality. Additionally, there is no strong integration with the compliance framework, either in terms of rolling it out or proving our adherence to it.

I would like to see improvements to the compliance manager, such as making it easier to start small and grow over time. This is not possible at this time.

The current event-based retention management is very poor. This is an area that needs improvement. We need to be able to more natively or near natively label content for retention and sensitivity across other lines of business systems like Workday and ServiceNow. This would allow us to extend labeling to those applications and make it native. This would be of great benefit to our clients.

Purview's DLP protection has some downsides. One downside is that the tips only appear in native applications. This means that users will not see them in other applications, such as web browsers. Another downside is that the tips only cover a subset of all the information. This means that users may still need to seek out additional information elsewhere.

The technical support has room for improvement.

I have been using Microsoft Purview for a year and a half.

Microsoft Purview is extremely stable.

Microsoft Purview is highly scalable.

The first level of support is not very knowledgeable and it is hard to get proper support because of the procedures in place.

Neutral

The initial deployment was complex, but not because of technical difficulties. The main challenge was engaging end users and getting them to adopt the new system. This was because the system required them to think about information in a new way. The deployment took around 12 months and required five to ten people working two days a week.

The implementation was completed in-house.

The return on investment is very good for what Purview offers, but it does lack some of the features that other solutions have. For example, if we're replacing something that already exists, we could do something cheaper or quicker. However, the value of this solution is in its ability to mitigate risk. If we don't have any type of classification and security in place, we're always opening ourselves up to risks. The cost of this solution is high, but the cost of not having it could be much higher. The return on investment is around 200 percent.

Some people find the tier licensing system complicated, but it offers a lot of value for money if we use the features. In fact, many clients who use the E5 licenses find that they can get a better return on investment on those licenses. Once they do, they find that the tier licensing system is very fairly priced.

I give Microsoft Purview an eight out of ten.

Time to value is quite long, especially when it impacts end users and requires new skills and knowledge. This is especially true in IT departments and on the business side. However, once the value is realized, the return on investment can be very good.

This type of solution is deployed across the entire Microsoft 365 tenant. It also has an Azure side, which is two things across that tenant as well. There is no area where it is used more or less. However, there is more interest in the areas of security and privacy. Therefore, legal, HR and IT are the most likely places to deploy this solution. Finance and merger and acquisition are also areas where people have more interest in deploying Purview. However, it is normally deployed across the entire organization.

We have around 30 clients consisting of anywhere between 20,000 and 50,000 users.

The maintenance is overseen by a full-time compliance technical person and a compliance business person.

I would advise assessing the maturity of the people and processes before using these types of tools. The technical side of things is not too complicated but we need to have the people and processes in place to classify all of our information and to ensure that our policies are being triggered. This can be a challenge for many organizations, as most have dark data, especially on structured clients. Ultimately, it is the people and the processes that make the success of these tools, not the technology itself.

We use the platform to comply with regulations, and our specific use cases are information protection, information governance, data loss prevention, and insider risk mitigation.

The information protection and data loss prevention functions help our end users be fully aware of the sensitivity of certain information. From a management and CISO perspective, they have insight into where sensitive data is stored and whether we are required by law to delete it after a certain period. That's an invaluable overview of the situation, so our users are more aware, and Purview took our information governance to the next level. It also supports our certifications because it helps us comply with regulations, including ISO/IEC 27001, which are essential to our functioning.

The solution increased visibility into our estate; we had a problem with GDPR-related personal information stored in our environment, which we didn't have any insight into. When we used some of Purview's data governance, data lifecycle management, and content search features, we could rapidly go after that information and resolve compliance issues. The tool also provides management with much better oversight of our stored data.  

Purview enables us to show our compliance in real-time and supports it via the compliance manager and compliance score. The assessment templates within the latter allow us to provide an overview of what we have done within the Microsoft 365 and Dynamics environments to our auditors, which is very handy. We're an ISO-certified company, amongst others. In meetings with compliance regulators, we can show that we're using information protection, DLP, data governance, and data lifecycle management functions to comply with regulations fully. The solution dramatically speeds up the process of talking with external auditors. 

Purview saves us time and money. We're an information-intensive organization; seeing where our sensitive information is stored is a significant time-saver. In addition, showing we're safeguarding that data also saves us a great deal of time. From an efficiency standpoint, AI and auto-classification of information is another big time-saver, as the staff members working for our clients don't want to spend time considering how long data needs to be stored, whether it should be archived, how sensitive it is and so on. I can't quantify exactly how much, but all of the above reasons save us a significant amount of time and money.

The data classification part of the solution is excellent, especially as it gives us an insight into our sensitive data within Microsoft 365. 

Data loss prevention is an extremely useful feature. 

The built-in information protection function is another that stands out. 

Purview delivering data protection across multi-cloud and multi-platform environments, including AWS and GCP, is becoming increasingly important. It's a relatively new functionality, and I see the importance of it growing even more over the coming years. This kind of functionality is highly appreciated for organizations operating a multi-cloud environment. 

It's very important to us that Purview can connect to iOS, Mac, and Android devices and data in other SaaS apps. From information protection and data loss prevention perspectives, information is accessed using many different devices, and extending that protection to iOS and Android is a must-have for any platform.   

The product's natively integrated compliance across Azure, Dynamics 365, and Office 365 is essential. The ability to classify information across workloads, and have a holistic view over our entire data estate where sensitive information is stored and handled, is excellent, especially from a CISO perspective. This is a capability we didn't previously have. Having that overview of where data is stored, plus the multi-platform/multi-cloud approach is the future for data classification and information protection. Wherever our data is stored, we have an overview of which is sensitive and which isn't. 

I greatly appreciate that Purview was built considering critical regulations worldwide, especially the international standards within the compliance manager. There are ISO and NIST standards, ideal for larger countries such as the USA and extensive international organizations.  

We use Purview for data loss prevention (DLP), and we're confident that we can detect and remediate policy violations. Microsoft improved its solution with recent additions, including advanced conditions, and the product is coming of age. The DLP is reaching a maturity level where we can confidently compare it with competitors like Symantec. It goes beyond DLP on emails, documents, on-premise, and endpoints; governmental organizations especially need to detect if sensitive information is being handled on devices. In this respect, Purview offers comprehensive protection.  

Used correctly, Purview is essential in staying on top of compliance. One of the best features in this regard is the solution's compliance manager, which helps us effectively comply with all the regulations. Many organizations should start using the platform because it will keep them on top of their compliance stances, and Microsoft periodically updates the assessments. We must be aware of updates and changes, as we can miss them if we do not pay attention. We can't just run the solution, walk away, and think we're compliant; it requires some monitoring of the developments from a roadmap perspective.   

Microsoft is doing an excellent job improving the platform, and they have a lot coming out shortly. However, the licensing around compliance could be much more transparent; it isn't clear for many organizations what kind of license they need to use, whether that's E5, E5 compliance, an information protection license, user-based, or platform-based. More information here would be a welcome improvement.

Blueprints and landing zones like we have in Azure would be great to see in Purview. The solution could offer a baseline or blueprint of recommended settings for compliance regulations such as GDPR and ISO, which could be applied with a simple switch in the options. 

Some dashboard centralization, like one overview dashboard instead of many loosely connected ones, could be a good improvement.

We must build our own assessments to comply with Dutch regulations, a mix of international and EU standards, as they aren't native to the solution. Many of our clients in the Netherlands require adherence to Dutch regulations, and as well as Purview covers the international aspect, the Dutch side is covered less than we would like.

There's room for improvement regarding Purview's data loss prevention for educating users on how best to handle sensitive data. Microsoft is working on improving the policy tips. Still, from a user's perspective, I want to see more information in the case of a policy violation, such as context or details on why a specific rule is triggered. There are ways to tweak the DLP options, but a significant improvement would be real-time notifications when working on an email or message within Teams, for example. DLP is only triggered when sending or saving, so real-time notifications would be great. The basic functionality is there, but there's room for improvement. 

We've been using Purview for around a year since Microsoft changed the name, but we've used the functionality within Purview for five to ten years.

We haven't had much experience with customer support as we didn't encounter many problems. However, the response is usually rapid, and the expertise depends on the technical knowledge of the agent we speak to.

Neutral

We didn't use different solutions, but some of our clients did and still do, mostly DLP and data classification platforms. The trend is that more have been moving to Purview because many are already paying for it within their licenses and not using it. We're an IT company focusing on Microsoft technology, so we went straight for Purview.

My colleague carried out the initial setup, and I'm primarily involved in deploying the solution's functions to our clients. Setup requires some planning, a discussion with the stakeholders, and a good sense of the data, but it's mostly very straightforward from an admin's perspective.

Our use case is mainly to do with GDPR-related data, and being able to get an overview of that information and act on it led to a speedy return on investment for us. Other organizations in the Netherlands bound by specific government regulations will also see a quick return on their investment when they discover they can classify their information and comply with regulations.

Aside from the complexity of the pricing model, the price itself is realistic. Features like AI components and automatic classification require additional licenses. Still, anyone can start using Purview with a basic E3 license if they're using Microsoft 365 and grow with additional licenses as needed. Overall, we're satisfied with the price.

With the way information is being used and the growth of data, the need for additional licenses for auto-classification etc., will become more and more apparent. I wouldn't be surprised if Microsoft incorporated those into the basic license in the future.

I rate the solution eight out of ten. 

Regarding Purview's data connector platform for supporting ingestion from non-Microsoft data sources, I have yet to work with it much. In highly regulated environments such as government organizations, it's very relevant, but I have yet to see it used much. The main reason is that the data connector platform is a relatively unknown component within the solution. It has its merits, but the use cases are limited.

If this were a year ago, I would have said the solution is getting there but hasn't reached maturity. However, Purview is now a very comprehensive solution; with all the enhancements, it's one of the best products available.

As Purview reached a maturity level where it could compete with third-party DLP solutions, some of our clients were able to move away from specific endpoint DLP products like Symantec DLP. Going with Purview also allowed these clients to fully leverage their existing licenses within Microsoft 365 and simplify their data governance. It provides a holistic view of the data estate, enables Defender for Cloud in Azure, and offers an integrated overview in one pane of glass.

Regarding automation, we use some limited functions using the solution's trainable classifiers and auto-classification of information. This notifies the user when working with certain kinds of sensitive data, GDPR and otherwise, so we use some basic AI functions within the platform.  

We're not currently using the product for insider risk management. Still, we are in the process of looking into implementing those features and how we could leverage them within our environment.

As a financial institution, our objective is to replace our existing in-house project with a comprehensive solution for data cataloging, data provenance, scanning, drift detection, and overall data governance. We use Microsoft Purview to fulfill these requirements and enhance our data management capabilities.

We haven't witnessed the full impact yet, mainly because it took us a considerable amount of time to effectively integrate Microsoft Purview into our system. Additionally, there are critical features that are currently lacking, hindering the platform from realizing its complete value. However, we have confidence in the roadmap and the commitment of the development team.

The most significant value lies in its seamless integration into the Azure ecosystem, automating various processes and reducing operational burdens. The ability to consolidate metadata from diverse services and databases into a centralized repository is crucial. Moreover, the flexibility of exchanging data through APIs allows us to extend and build upon the platform to meet our specific needs. The openness to supporting customers across various environments and the potential of a comprehensive data strategy are key factors that keep us committed to Microsoft.

Overcoming certain control issues would significantly enhance our overall satisfaction. We encountered challenges in building a custom subscription, and certain essential Azure financial control functions, like customer-managed keys, were not implemented.

I have been working with it for approximately two years.

We have around ten thousand users, and the scale might not necessitate the same level of custom development as larger companies. Despite our size, there are instances where building and hosting certain systems, like a database, provides us with greater control over our data.

I find it to be quite good. The enterprise culture and support we receive are appealing aspects. While our operational support may not match the industry leader, it surpasses what we've experienced with the third-ranked provider. I would rate it seven out of ten.

Neutral

Regarding choosing Microsoft over competitors, our decision was heavily influenced by corporate alignment. We already had a significant business relationship with Microsoft, and there was strong alignment at the senior leadership level between our institution and Microsoft. Despite acknowledging that Microsoft is behind AWS in terms of service maturity, especially in areas like data databases, authentication, authorization, and management automation, we recognized the benefits of our existing alignment.

While it may take another year to reach the desired level of functionality, we believe in the platform's potential and anticipate improvements in its feature set.

In the long run, using Purview may be more cost-effective than building and operating our own solution.

I currently rate it a five out of ten, and I believe there's potential for it to reach a seven within the next year.

We are integrating Purview with Copilot. We are creating prompts in Copilot for whatever we require from Purview. There are multiple scenarios where we create something in Purview: eDiscovery, auditing, labels, and data loss protection alerts. It is something like the parent application for the data loss alerts.

The major benefit is the workflow inside Purview. While creating policies, we can add an organization's security groups and, for those particular users, we can control the user data or exfiltration. We can control the workflow of those users. If we want to exclude a particular channel that they use to communicate about sensitive data, we don't need to monitor it. We can just exclude it. That means we can include or exclude every individual step in their workflow. Based on our customers' requirements, because there are a lot of features in Purview, we can easily include, exclude, enable, or disable things. That is the major advantage of Purview.

Also, it has reduced false-positive alerts for data loss protection. Why? Because the policies or detection patterns are based on the normal or generic concepts that apply within each organization. Each will have its own set of policies. And that generates fewer alerts. An organization can have particular data monitored, and that can be changed from organization to organization. As a result, there is a lower chance of false-positive scenarios.

My favorite features are eDiscovery and insider risk management, because these are the major threats to an organization that can't be easily traced.

Also, there are multiple rules within Purview related to cloud applications. Purview's major focus is on Microsoft Azure and its Microsoft cloud-related applications, such as Exchange, OneDrive, SharePoint, et cetera. They have created a set of rules and added workflows to the policies as well. That means we can directly add those particular cloud workflows to the policies. Alerts can be triggered and workflows implemented based on the rules that we set while creating a policy inside Purview.

We also use Copilot, the next generation of ChatGPT. If you ask it: "According to Purview, what were the DLP alerts that were generating today?" it will take just five seconds to generate the data—whatever is available in the backend of Purview. Copilot is integrated with Purview. If a person is using Purview but doesn't have any idea how to operate it—meaning they don't know how to search for alerts—they can easily ask Copilot. They can create a prompt. That way, a non-technical person can get the data.

Also, all the required security products are integrated with Purview, including endpoint DLP.

I would like to see them simplify advanced hunting. There are differences when looking at an incident in the M365 portal versus Purview, and the main one is the advanced hunting. In the M365 portal, you can write KQL queries and fetch data. If that was available in Purview, it would be very good.

Another issue is that for incidents, only DLP alerts are available in Purview, not the incidents themselves. An incident consists of multiple categories of alerts belonging to multiple products. But in Purview, we can only see DLP alerts, yet those alerts could be part of an incident in the incident portal. We are not able to see if a particular alert ID is part of a given incident.

For example, if an exfiltration happens, the exfiltration-related alert will only be triggered inside of Purview. But it's possible that before the exfiltration, there was a kill chain there, such as initial access, privilege escalation, a user being compromised, or a brute-force attack. Those types of alerts are not available inside Purview. They are covered in other Microsoft products. All those products' alerts will combine into one case and generate an incident as a single story. But in Purview, the incident is not available.

I have been using Microsoft Purview since it was introduced. I am part of our Purview team.

With Purview itself, I have not faced any issues, but there have been some with Copilot.

The scalability of Purview is eight to nine out of 10.

The price is a little bit high, but it's worth the money because it has a lot of features. And there will be more features in the future.

My advice is that you need to understand the architecture of Purview first. Play with it and go through the data loss policies. Whoever is using Purview should have some idea about data loss protection policies. If you have these things, you can easily do things in Purview, such as labeling and IRM.

There is no maintenance. As a user, you just see the alerts, while the protection is taken care of by the Microsoft team.

I see many customers these days looking into Microsoft Purview syntax and mainly using the solution for data lineage and data governance. The customer wants to be able to understand data a bit more within the organization and be able to classify and protect sensitive data and understand what it is. 

My company works with the healthcare and financial sectors.

Microsoft Purview can give good information on the cause of the breach, and that comes into the forefront of many organizations nowadays to know how to protect data not only from external sources but also internally as well.

Much of the feedback I get from customers on how Microsoft Purview improves organizations is around the visibility factor at the end of the day. It's all about protecting data and ensuring you don't lose data externally and internally.

Many customers also say that Microsoft Purview also helps simplify the management of data governance policies, as it gives you visibility, automation, and authentication. For example, you can now see classifications whether your documents meet specific criteria or not, through Microsoft Purview.

From my experience and customer feedback, one of the most valuable features of Microsoft Purview is ease of use, especially for content hosted within Microsoft 365 and Azure. You can connect Microsoft Purview to different sources.

I also like that the pricing model for the solution is reasonable, though that would depend on how much you use. That makes it much easier for people to have that initial setup, get started, and see all of the information straight away. If you want a more complex Microsoft Purview setup, you may have to contact a consultant for more technical aspects to enable the solution. Still, one of the most significant selling points for me is the setup, including the automation experience.

Microsoft Purview delivers data protection across multi-cloud and multiple-platform environments, including AWS and GCP, which I find very important because if you look at the percentage of customers that have multiple automated channels or multiple-platform setups, it's very, very high, primarily because customers don't put eggs in one basket.

It's also essential for me that Microsoft Purview can connect to iOS, Mac, and Android devices, including other SaaS apps, as I spend quite a lot of my time using my iPhone and iPad, whether for a webinar at the end of the day while I'm preparing dinner, and that's still the same information on my company laptop or desktop, which means I still need to ensure that the data I access is still very secure. 

Though you can protect yourself with multifactor authentication, people find ways to get past that, so you have to ensure that even if someone's getting into your organization now, the location within is siloed, and you could see the different classification levels that could easily be applied, making it more difficult for that person to get what he needs easily, compared to SharePoint that's open to everyone, making it a walk in the park, so what Microsoft Purview is able to provide is very important in this hybrid age.

I find Microsoft Purview very important in its natively integrated compliance across Azure, Dynamics 365, and Office 365, as you'll have sensitive content stored these days, especially if you're an organization with a lot of customer data in your database. Microsoft Purview helps secure customer records and also has a data loss prevention feature, plus data governance and compliance features that I find very important for organizations.

Microsoft Purview has also helped reduce the number of solutions my company needed. The solution is part of the project Microsoft has rapidly been developing, and over the years, the components of the Microsoft services went through a confusing renaming cycle. There were a lot of different services, but I've found out how each should be used, such as for security and compliance, some complementing technologies for identification, classification, traffic, and AI, for example, that I'm continuing to evaluate. At first, there was a bit of confusion, but now it all makes sense.

The simplicity of the number of solutions made data governance a lot easier. With Microsoft Purview, you won't have to interact with a substantial amount of systems, and I'm a firm believer that more risk could arise when you introduce more complexity into a solution or system you're developing. The services you make use of could sometimes deprecate and change features. Hence, having compliance, governance, automation, and data discovery features in one solution, such as Microsoft Purview, makes my life and the customer's life easier.

A key feature of Microsoft Purview for me is that it was built while considering critical regulations worldwide. My company works with organizations where there's usually a requirement for compliance, such as GDPR. I also work with many Germany-based customers that require GWC compliance, and there's strictness with the way data is stored and classified. You must advise and know all regulations, which Microsoft Purview enables you to do. For example, if you look at the amount of data in terms of size, such as the terabytes being housed in various websites, there's no way you could get the information without Microsoft Purview. There's too much data within organizations now, and all it takes is a tiny percentage of that data to be shared in the wrong way or be leaked, which could incur substantial fines, so Microsoft Purview is a product that justifies itself in that very premise.

Microsoft Purview has also enabled visibility, giving customers an overview of how much data is compliant. The solution also provides visibility into the quality of data, movement, and performance, so visibility is another valuable feature of Microsoft Purview.

My company uses the AI and automation features of Microsoft Purview, which I find very critical within the solution. The speed and accuracy of risk detection improved with  AI and automation features because classifying data is easier now, giving me a headstart. The AI can do essential, light work, going around all of the various containers within the organization, so the team only does twenty percent of the work now, such as management, reviews, and reports.

Microsoft Purview AI and automation make it less admin-intensive from a data protection and compliance point of view. If you look into a role within an organization, for example, I'm a DPO, which is a relatively new role. With Microsoft Purview, you'd only need one to two people full-time, another key benefit of the solution. The rest of the work would continue to fall on the shoulders of the IT team, which is stretched in organizations today.

The solution enables you to show real-time compliance. Microsoft Purview gives you the necessary data because it ties into the compliance scores when you eliminate instances. Right now, there are a lot of backlog reports in terms of compliance on static IPs, data leakage, lineage, and backup.

Real-time compliance data provided by Microsoft Purview has helped organizations, especially in terms of meeting with compliance regulators. I helped organizations with technical enablement, mainly stakeholders who requested assistance, and the reporting in Microsoft Purview has taken so much responsibility from the hands of stakeholders. The solution has better reporting that has broken down data for organizations, giving headlines and figures you usually won't easily catch, which makes successful deployment a lot easier.

Microsoft Purview has also helped reduce the time to action on insider threats, whether fraud or rest protection. Organizations, especially huge financial organizations, are bothered by threats, and Microsoft Purview has been beneficial. In terms of how much the solution reduced the time to action on insider threats, based on all industries I've worked with, it's twenty to twenty-five percent. I'm basing this figure on the fact that the automation from Microsoft Purview is very powerful, and the solution gives accurate protection. If you get an alert from Microsoft Purview, it's usually for valid reasons.

Overall, Microsoft Purview has affected the ability of customers or organizations to stay on top of compliance. You see many good products in the market, but if you have a customer  mainly using Microsoft products, such as Dynamics 365, CRM, etc., and the customer belongs to the financial industry or the public sector, for example, that's dealing with information, it's a no-brainer to have Microsoft Purview in the organization.

One drawback of Microsoft Purview, though it's beneficial and easy to use, is that when you start plugging in connectors for third-party sources when setting the solution up for data collection, it becomes a bit more tricky. There's limited documentation, so it's not as intuitive as setting up other parts of Microsoft Purview. If the process of connecting with third-party cloud providers and other SaaS products could be simplified, that would make Microsoft Purview a better product.

In terms of how Microsoft Purview supports ingestion from non-Microsoft data sources, from a user experience point of view, it's a bit more challenging and results in a bit more struggle in that area. Overall, it's decent, but it would benefit customers if Microsoft spent more time and energy improving that experience and getting it on par with other Microsoft products. Microsoft could make it a lot easier to build connections with other cloud vendors, such as AWS and GCS. Microsoft will get there eventually, but it needs to understand its customer base and look at the percentage.

I've been using Microsoft Purview for a year and a half, particularly getting up to speed with the current version. However, Microsoft had different iterations of the solution that my company used in the past two years.

Microsoft Purview is a very stable solution.

Microsoft Purview is a scalable solution, and that's the beauty of a cloud-based solution. It doesn't matter if you bring more files and documents tomorrow. You won't have to go to the data center and deploy server loads. You just have to pay, and that's the beauty of it.

I'd give Microsoft Purview technical support a rating of seven out of ten because it's tricky to get to the correct department, such as the product support team, for example, when you contact Microsoft Support. I do like that there's user documentation that helps get a lot out of the way, and my experience with Microsoft user documentation is pretty good.

Neutral

Some customers used different setups before using Microsoft Purview, but those were outdated and designed for file sharing and on-premises storage. Now, they are on Microsoft Purview.

Microsoft Purview, as a solution, is set apart by being baked into the Microsoft Stack.

Deploying Microsoft Purview is pretty straightforward, though an organization may have to contact a partner or consultant to assist with deploying the tool because my company doesn't deal with critical business situations. There's a need to ensure that the website is set up proactively, works with the tool, and also covers information on how to address possible issues that could arise in the future.

The deployment itself isn't too tricky and can be done quickly, but you must ensure that the organization has adopted it. It's not merely about deploying Microsoft Purview, and then that's it. You must ensure the proper psychology is there and that you're continuing to scan new data sources if you're buying into a new service. You have to keep the solution up-to-date and also know what to do if a disaster occurs. Microsoft Purview isn't a tool you can just turn off. Each organization goes through a pilot, and my company does a phased approach, such as a pre-production environment. My company shows the customer how the tool works and what it would do in different scenarios and lets the customer practice using Microsoft Purview.

You get ROI from Microsoft Purview because its cost is entirely justified, considering the value it brings back to your organization from the data insights the tool provides. The significant decrease in the percentage of risks, particularly from insider frauds and data loss, whether maliciously or unintentionally, or by accident, helps the organization enjoy ROI from Microsoft Purview.

The solution also helps my company uphold its reputation of abiding by European legislation, such as the GDPR, knowing that the company can keep data secure and that Microsoft Purview can help prevent organizations or companies from being out of business by decreasing data loss and insider fraud risks, so I'd say the ROI can be pretty high from the solution.

Microsoft Purview has reasonable pricing. The solution helps save money, and its cost is justified, at least for the organizations I've worked with. Microsoft Purview has a pay-per-use pricing model, so it's one of the most cost-effective tools, as your cost will be based on your usage. It's a pricing model that Microsoft has nailed down, making it great that whether you're a small organization or a multinational, giant organization, the pricing model for Microsoft Purview works. If you look into the cost of the breach versus the ongoing learning cost over a year or so, the solution's price is more than justified. However, I'm unable to give the exact figure on how much money Microsoft Purview can save an organization, as I'm a consultant who doesn't have precise information.

I don't use Microsoft Purview for data loss protection within the company, but I've seen its use case, so I understand where you would use that feature.

Regarding how Microsoft Purview AI and automation features affected the quality of insights my customers have, it's hard to say currently because there's not much of a benchmark to go off. The AI isn't going to be as accurate as a person who's been in the organization for ten years, for example, who knows the data and types of data the organization has. If you look at the way AI is developing, it's not fair to rate it yet, but if it keeps going in the same trajectory, it will be possible in the not-so-distant future.

Microsoft Purview has a cloud-based deployment on Azure.

The customers I've worked with vary from multinational data organizations with fifty thousand people to organizations with five hundred to less than a thousand people.

In terms of maintenance, my recommendation is to always keep on top of it, such as continuously scanning and being on top of it when building new apps and doing data migrations, but not necessarily in terms of updates. You should ensure encrypting your data as well, but from a maintenance point of view, Microsoft Purview is pretty self-sufficient, but you'd have to monitor it and not forget about it if you want to keep reaping the benefits.

I would recommend Microsoft Purview to others, but my advice is to ensure that the data layer underneath your organization is solid and that you're building a solid foundation. The success of any product or solution is dependent on a good foundation. You also have to ensure that you have the right people, the deployment is based on your industry, and you're meeting the standards, whether setting the solution up within a year or so. It's similar to building a house. Without the proper foundation, you're never going to finish building properly. Issues will crop up, and your home won't be properly aligned. However, if you build it entirely on a concrete, perfectly flat base, then it will be maintained well, and you can go forward with it.

My rating for Microsoft Purview is eight out of ten because it only requires limited improvement, and you won't find another solution better than Microsoft Purview in the market.

I'm a Microsoft consultant involved in the technical enablement of various Microsoft services.

We need to catalog and assign terminology to all of our data to find all the personal information that we have within our copy systems.

Over the last three years or so, we have been using Kafka and nesting queues a lot. We wanted to bring in an orchestration engine to integrate seamlessly with our nesting system. We had a lot of legacy applications that are not that old, and we did not want to rewrite software components that we own to get the benefits of orchestration. That's where there is a need. One of the factors that will decide if the use of Camunda will spread out to more use cases in our company is the ease of integration.

We weren't sure what our data was in certain areas. We created red Xs that basically indicated the kinds of codes and criteria we are looking for. Purview uses them to scan, and then it tells us what it has found and where that data may lie within our servers and databases. Now, people in our company have a good understanding, when they look at a database, of what data is in that database.

It has dramatically improved the visibility we have into our environment. That's the main concept of Purview, to show you what data you have. The solution has been magnificent due to the fact that now we know, when we scan the data set, what we have within the database.

One of the compliance criteria in the UK is to make sure you know where all your personal information is, and Purview gives us the ability to know that across our data estate. When we have meetings with compliance regulators it's great because we can demonstrate where our data is. There are no awkward questions because we can say, "This is where our data is." We know it's accurate and it's one version of the truth. Everyone understands that, which is fantastic.

As a result, it has definitely saved us time because when we have requirements meetings they try to establish where the data is. But with the cataloging ability of the tool, we know where all the data is. We don't need to spend five hours finding out where all the data is because we already know. We've already got a scan and it's already told us, and we have verified that. Now we can use that as a blueprint to go forward.

Purview gives us the ability to find out what data we hold, and in which tables, so we can understand and have one version of the truth in every database server system.

The cataloging tool is definitely the most valuable. To catalog data you can have Purview do a scan that you configure yourself. It goes through all of your data in the database server you're connected to and will say there is "date of birth" in this column and personal information in that column, and names in this other column. It tells you about all the data you have in your tables, which helps people understand our data. We now know what data we have.

It's also very important that the solution provides data protection across multi-cloud and multi-platform environments. Purview has links to all of our data so that we can make sure we have the right data protection involved.

Also, because it's very important to make sure that we have everything in place, and we only deal with companies that have all their compliance and rules in place, the fact Purview was built taking into account critical regulations from around the world is essential for our company, when it comes to scanning data.

Purview's data connector platform for non-Microsoft data sources is good, but there is some functionality that hasn't been developed yet. There are some servers that it can't connect to yet, because they're still in a trial process. However, there are obviously some non-MS sources it can support, which is good. Hopefully, for the ones it can't connect to, that will be rolled out soon.

There are other things that need to be developed in Purview. The data retention isn't great at the moment, and in that area we need certain functionality to be built. However, it's a very good tool and one I would champion.

I've been using Microsoft Purview for the last two years.

It hasn't gone wrong yet, so I can only give the stability a 10 out of 10. There have been no issues so far.

There should be no issue rolling it out, going forward. It's already working on seven or eight systems at the moment. However, we expect it will be on a lot more.

We have had a lot of contact with their technical support. Because we're at a very early stage with Purview, we need to make sure that we understand the functionality. They've been fantastic, mainly their support in America. They've been great. There have been no issues and it's very straightforward to understand what they're saying.

Positive

We previously used IBM InfoSphere. That tool wasn't good enough for what we needed.

The setup was pretty straightforward. We worked with our data engineer and it was sorted straight away. It was deployed very easily, in part because it's cloud-based. We had two or three people involved who work in data engineering, architecture, and data governance.

It's deployed across cloud and on-prem solutions. The maintenance is not heavy. It's very straightforward.

It was all done in-house.

We have seen ROI massively. We now know where all our data is, so we don't need to worry about that. The amount of time that it would have taken to do that manually, without a tool like this, would have been huge. It was done automatically with the scan.

The pricing is absolutely excellent, fantastic. And the licensing is also fantastic. You pay for what you use, and the license isn't massive, unlike a lot of other licenses.

We used the review sites to look at all the other technology, and it came up that Purview was the most cost-effective tool to do what we wanted. It wasn't just the cost, but rather, the cost and the functionality. What we wanted was the right price. We found that other tools could do very similar things for a lot more money. While the cost of Purview is very good, the functionality is also very good.

Make sure you have all the details of your endpoints in place because Purview needs to link to the endpoints. If you haven't got the endpoints in place, then you can't make the connection to the servers and to the databases. But if you have all those details in hand, it's very simple and straightforward.

Regardless of our use case, it's important that Purview helps protect iOS, Mac, Android, and data in other SaaS apps. But we use it to catalog our on-prem and our cloud so for us, it's not necessary that it covers iPhone or iOS or Mac. It's more of a system-architecture scanner.

And because it's a cataloging tool for us, we still need our existing systems in place. Purview is like a layer on top of that to find out where we have things and where we need things.

It's a cloud-based system, but it doesn't have any relation to Office or other Microsoft systems. It can link up to anything.

The only reason I'm not going to give it a 10 overall is that not all the functionality has been rolled out yet. Purview is very early on as a tool.

Overall, Purview is a fantastic tool for staying on top of compliance, knowing where your data is and what data you hold. In terms of data retention, you know what data is where and how long it's been there for. It really helps the business to understand that.