Microsoft Purview Data Governance Reviews

I'm an implementer and an integrator. In my last project, I used Purview for a government organization, so we primarily used it for data governance and data lineage. We haven't used it with Microsoft 365. It's a portal that takes data from SQL Server and the data lake. We mainly work on the data governance and security side. About 20 business analysts use Purview. The company has around 100 people in the department.

Microsoft Purview helps us manage data in various formats like Dynamic SQL. It performs two procedures. The primary function is to ingest the SQL database and modify the data type or column name. It also manages the data types and all the metadata related to the tables and columns. It puts everything in one place in the call view or the description pertaining to the business logic, plus the column-level descriptions.

It streamlines things by reducing the number of solutions that must interact with each other. When everything was done manually, each program maintained its own version of the Excel file. Now, it's in one central place, and I can go to Purview to manage the permissions.

By centralizing everything, Purview gives senior management greater visibility into their data. It also makes the data more accessible to non-technical people who need to access the data daily. It's easy for an admin to provide them access if they need to check something quickly. 

Purview checks compliance in real-time. It's helpful when we're meeting with regulators. We must follow European data regulations, so we must manage security and access. We need to show them a log of who had access, who gave it to them, and how many days they had access. That is all shown in Purview, plus other columns like the NHS identification numbers, etc. 

I rate Purview a six out of ten for its ability to help us stay on top of compliance. The product is still not mature enough. There are so many servers on Purview.

I like Purview's data discovery features. It automatically scans and identifies all the fields. In the last project, the customer required us to have some of the codes we specified in this, and we had to structure the codes in a specific way. We can define the structure. 

Previously, everything used Excel, so everyone had their own version of the same spreadsheet with different data, and they were managing it on SharePoint. That's why we moved it to Purview. 

Purview's privileged access manager helps us explore user access rights within the data lake. We use the data lineage and governance features. It can also explore secret data, but we still haven't implemented this feature. It has secure connectors for non-Microsoft sources, which is critical. We're bringing in files from storage. Purview connects to storage, scans it, and edits the required information. 

We've had a few issues with the scanner. It runs perfectly one day, and on another day, it will run the whole night. It's probably related to the rules. If I set some compliance rules and apply the rules to any column, I can't delete it. I have to disable it and reactivate it.

We have two instances. One is for everything, and the other is for the production environment. Sometimes there is a bug when the scan runs overnight. When we come in the next morning, it's still running, so we have to stop and restart it. This is costly.

I have used Purview for a year and a half. 

I rate Purview a six out of ten for stability. 

Purview is scalable. You can integrate it with on-premise solutions and third-party products. 

I rate Microsoft's support a seven out of ten.

Neutral

Our client was using Informatica. We used Purview for this project because the client has everything on Azure. It's better to use Purview when you work on Azure. We compared Informatica's available features with Purview's, and the client decided to go with Purview because of all the services in Azure. Microsoft is constantly adding new features to Purview.

Deploying Purview is straightforward. We deployed manually by creating services in Azure. The initial setup took five or six months. After that, we spent some time setting up the scan rules and defining the structure. I deployed the solution along with three other people. We worked with one or two people from Microsoft during the deployment. We have an excellent relationship with Microsoft, and they're helpful when we have any questions. 

We've seen a return from using Purview because it's more accessible to high-level managers without technical knowledge. 

Purview's price is pretty high when you factor in storage costs. 

I rate Microsoft Purview a six out of ten. It's a good service if you only use Azure. If you have an on-prem environment or use another cloud provider, you can compare Purview to other solutions. 

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.

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 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.

Microsoft Purview helps our business identify valuable information across various data types by using machine learning and customizable tags. It then allows users to export this data with PowerShell and combine it with metadata from other Microsoft products, facilitating both data analysis and migration processes.

While I haven't used Purview's cross-platform capabilities, I'm impressed by Microsoft's integration of its various solutions, including ComplianceOne and SharePoint, which cater to large enterprises. A deep dive into the functionality confirmed this positive impression.

The ability of Microsoft Purview to connect across devices, including Macs like mine, is a major benefit. While I was surprised to find PowerShell running smoothly on Mac, Purview itself has been user-friendly and avoided the issues I've read about online. This ease of use is crucial for me.

My previous projects focused on M365, but the next step is integrating Azure Virtual Machines into our solutions. In this context, Purview's ability to natively integrate compliance across both Azure Dynamics and Office 365 is crucial for ensuring our work scales effectively.

The biggest advantage of Purview is its ability to centralize data management. This multi-platform tool integrates data assets from across the company, providing a reliable and unified way to handle data procedures. This consistency, a hallmark of Microsoft products, is valuable for many users.

Designed for our regulated environment, Purview offers a variety of features that enable us to develop compliant solutions even when limitations seem to restrict what's achievable.

Purview has helped save us time through automation.

The most valuable aspect of Purview is its PowerShell connectivity, enabling automation. The content explorer helps visualize how classifiers, including custom-sensitive information types, identify content. Purview even allows testing these custom types with a dedicated button. Overall, PowerShell governance and export capabilities significantly improve our workflow by automating tasks and simplifying data extraction.

While Microsoft Purview addresses global regulations, it lacks out-of-the-box functionality. Extensive development is needed to define sensitive information types and train rectifiers for each customer. Most importantly, Purview currently lacks multi-language support, hindering its use in multilingual environments. Since communication compliance is the only exception, future updates should include sensitive information types and keywords in major languages, especially those relevant to the European Union. This would require customization efforts to create equivalents for these information types and keywords in other languages.

The rapid pace of feature changes in Purview, including marketing shifts, retirements, merges, and splits, creates challenges. Documentation struggles to keep up, leaving users behind. Further compounding this issue is the inconsistency of PowerShell modules. While some, like the SAP exporter, function well, others, like the trainable classifier's missing fetch module, significantly limit the usability of a potentially valuable feature. This lack of polish hinders automation efforts and makes data governance assessments more difficult.

Setting up Purview in a production tenant proved challenging due to a lack of clear documentation on permission requirements. While Purview offers role-based access with custom role creation, there's no built-in explanation of each role's function and associated permissions. Microsoft Learn documentation wasn't helpful either. Ideally, Purview should provide in-context information about each role within the portal, eliminating the need for cryptic names and extensive external research.

I have been using Microsoft Purview for under one year.

Microsoft Purview seems to be functioning, but there's a lack of clarity on how it analyzes data. The content explorer shows inconsistencies, with Microsoft acknowledging that the actual document count might differ from what's displayed. This suggests limitations in the current setup. While improvement is desirable, it's still a usable tool.

I submitted a support request in the test tenant, possibly specific to that environment. However, the Purview quality was lacking. Automatic replies didn't address my question, which seemed misplaced within the chosen topic. It felt like I contacted the wrong department. Instead of offering real support, they suggested I write a public blog post seeking help online. This was essentially non-existent support, potentially due to limited resources for test tenant users. It's unclear if this reflects the quality of support for the expensive enterprise licenses.

While deploying Purview itself was easy for me after I had spent significant time getting a Microsoft certification, onboarding junior colleagues who haven't had that preparation is proving more challenging. Despite their initial confusion, the overall structure and features of Purview seem well-organized and at least decent.

While a single person could deploy Purview in this instance because it's a test tenant, it's important to clarify that this ease of deployment applies only to the test environment and wouldn't be representative of the process for a production tenant.

The implementation was completed in-house.

Microsoft Purview is a subscription-based service, so we need either an E3 or E5 license to use it. The specific features we have access to within Purview depend on which of these licenses we have.

I would rate Microsoft Purview eight out of ten.

To choose the best Purview subscription for your needs, I recommend using a test tenant to explore Purview's features and value proposition. This will help you identify the most critical functionalities and choose the subscription that best aligns with your business requirements.

Our primary use case of Microsoft Purview is data discovery and scanning data sources.

Microsoft Purview is a cloud-based service on Azure, but the way it scans data sources is hybrid. While Purview itself resides in the cloud, some on-premises servers called integration runtimes are deployed within Purview to scan specific data sources. These on-premises servers are essential for making those sources accessible to Purview for further management and governance. In essence, Purview leverages a hybrid approach for data source scanning, but everything else about the service operates entirely in the cloud.

Microsoft Purview's data connector platform for handling non-Microsoft data sources effectively addresses our data ingestion requirements.

Purview affects the visibility we have into our estate. It is the primary reason why we use the solution.

While Microsoft Purview doesn't directly provide revenue, it saves our business money by improving efficiency. Imagine we're launching a marketing campaign and need customer or product data. Before Purview, we'd have to search for existing reports, unsure if they even exist. Now, Purview lets us see all reports, who created them, and when they were updated. This saves us time by eliminating manual data searches, ultimately reducing costs because people's time is valuable.

Purview's greatest benefit for us is data discovery. Even someone unfamiliar with our data can use Purview's basic keyword search to find relevant data sources. Purview then reveals details like data points, who maintains the source, update frequency, record and data point counts, columns, and data types – all this metadata is instantly available, making Purview our primary tool for data discovery.

While Microsoft Purview currently allows weekly scans for data sources, this limitation hinders the usefulness of the tool for frequently changing data. Ideally, Purview should offer daily scan frequencies to better accommodate these dynamic environments.

Microsoft should provide full access to log details, particularly those related to technical aspects of data source integration. Hiding information from technical users assumes a lack of understanding on their part, which isn't the case. While Microsoft claims Purview is under constant development and some features lack documentation, this shouldn't prevent transparency, especially for established functionalities we rely on.

I have been using Microsoft Purview for nearly one year.

Microsoft Purview is stable.

Microsoft Purview meets our scaling needs.

The error codes displayed by the user interface weren't detailed enough to diagnose a problem we had, so we contacted technical support for help. Even with some internal information, we couldn't properly debug the issue. Microsoft then examined their internal logs to provide more details about the error message, which was all we needed. Once we saw the additional log information, we were able to pinpoint the exact problem and fix it.

Neutral

Since Purview is an Azure service, enabling it for our company was simple for IT. Once activated, I became the collection admin, and data admin, and assumed all the associated Purview roles. Setting up the first data scan for our reports and data sources was surprisingly easy, even without any prior experience, though being technical helped! The process is entirely point-and-click with no coding required.

The week-long deployment involved collaboration with our IT network team to handle resources behind corporate firewalls, while I managed the remaining tasks, bringing the total number involved to three.

While we evaluated various data discovery and analytics solutions, particularly open-source options, we ultimately chose Microsoft Purview due to its seamless integration with our existing Azure Stack environment. Since Purview was already included in some of our corporate Microsoft agreements, it offered a cost-effective and user-friendly starting point for our data discovery needs.

I would rate Microsoft Purview eight out of ten.

While our data platform handles governance and privacy, we use Microsoft Purview specifically for data discovery. It helps us scan existing governed data sources and make them discoverable through various methods like keyword search, research tools, and browsing by data source. Notably, Purview provides valuable metadata, even though we don't currently leverage its compliance features.

No maintenance is required on our end.

Before considering Microsoft Purview, identify your specific data governance needs. Purview is a comprehensive solution, so pinpoint the features you require (data discovery, classification, sharing, etc.) and how they address your challenges. If you only need a few functionalities and paying extra for unused features isn't ideal, a simpler solution might suffice. However, if you plan to leverage Purview's full potential and the cost aligns with your budget, then I would recommend Purview.

We utilize Microsoft Purview to manage our data classifications, identify sensitive information in our documents for certification protection and data loss prevention, and we anticipate employing insider risk management. While we haven't yet implemented insider risk management, it is part of our strategic plan and compliance assessment.

From an access management standpoint, we have users accessing our data from various mobile devices, including Android, iOS, and iPad, as well as Windows and MacBook computers. Therefore, it is crucial to implement consistent policies and safeguards across all platforms, regardless of the operating system or device type.

We are a heavily Microsoft shop so all Microsoft platforms are important to us and Purview's natively integrated compliance is great.

It is important and useful for us that Purview was built taking into account critical regulations from around the world.

We report on all of our DLP policy violations. We have alerts set up to notify our security team to take action when violations occur.

Microsoft Purview Data Loss Prevention is an effective tool for educating users on how to best handle sensitive data. It can detect and identify various types of sensitive data, although we have observed that not all of the built-in detection mechanisms function flawlessly. Consequently, we have had to modify some of the detection modules. Additionally, certain detection rules specific to New Zealand have not performed as expected. Despite these limitations, the ability to detect sensitive data and utilize prompts to guide users in correctly classifying documents is quite valuable. We intend to expand our use of these features as we progressively deploy Purview across our organization.

We have several Mac OS users in our business, so it is important that Purview can and does extend policies regardless of the platform being used.

Since implementing Purview, the compliance assessment process has been effective. The expansion of country-specific regulations has been a crucial development. In New Zealand, we've utilized built-in privacy act laws and regulations, which have been beneficial. However, I believe the integration of the Copilot tool and advancements in AI will likely bring about continuous changes to the compliance landscape.

With Purview, we can continue using native Microsoft products for scalability, eliminating the need to rely on external vendors. This approach reduces the number of vendors in our environment.

The visibility Purview provides into our estate is useful. We have had a privacy campaign running for the last year and using Purview to essentially see where our data and sensor data are.

Purview enables us to show our compliance in real-time. We would use it to help demonstrate our compliance to regulators.

Purview enables us to save approximately 30 percent of our security team's time by providing visibility into previously obscured areas of our environment. Moreover, Purview is seamlessly integrated into our existing Microsoft licenses, eliminating any additional costs.

Purview helps us stay on top of compliance.

Data authentication enables us to classify documents based on whether they should be restricted for internal consumption or permitted for external sharing. This classification allows us to apply appropriate policies to each document type.

The DLP is also a valuable feature that we use.

The reporting is limited and has room for improvement.

Privacy features should be integrated into the core product rather than offered as optional add-ons, as privacy is not a luxury but a fundamental requirement.

I have been using Microsoft Purview for six months.

I would rate the stability of Purview a nine out of ten.

Purview can meet our scalability needs.

The technical support used to be more reliable and consistently good. Now, while it's still possible to get assistance from a knowledgeable representative, the overall quality of support has declined.

Neutral

We previously used Azure Information Protection and Symantec DLP. We switched to Microsoft Purview because of the cost savings.

Initial deployment is straightforward as we are a Microsoft shop, facilitating seamless integration with the native platform.

The deployment of Purview involved three individuals: one primary engineer and one architect. The initial deployment phase spanned six weeks, followed by an ongoing tuning process to maintain Purview's up-to-date status.

We have seen a return on investment, but it is too early to quantify the exact savings.

Purview is included in our Microsoft E5 licensing. There is no additional cost, but it does require us to maintain an E5 license to continue using Purview.

To fully justify the cost of Purview, it is important to leverage all of its capabilities.

I would rate Microsoft Purview a seven out of ten. While Purview is gradually improving, its reporting capabilities remain subpar. As we introduce additional products like Copilot and others, there will likely be a need for more robust integration plans that outline how these products will interact and the benefits they will provide.

We only use Microsoft Purview in our Microsoft 365 workload environment.

We are currently evaluating AI products like Copilot and several chatGPT-style tools for potential implementation within our organization. However, we are proceeding cautiously until we have fully implemented Purview to address our concerns regarding potential data loss associated with AI product usage. Once we are satisfied with Purview's effectiveness in mitigating these risks, we will accelerate our evaluation and adoption of AI products.

We have 5,000 users who were using Purview for the software, and we have a two-person support team. Every corporate user in our organization has a license to use the solution.

Purview requires regular maintenance because there is an ongoing need to review components like DLP rules and data classification. This ongoing maintenance ensures that the system continues to function effectively and accurately. Additionally, ongoing tuning helps to minimize false positives and false negatives, ensuring that the system accurately detects potential issues.

Ensure clear communication regarding the desired grouping of data classifications and the functioning of the data loss prevention policy. Understanding these aspects is crucial for effective product utilization. User training and communication are essential around the implementation of the data loss prevention policy as it impacts user behavior. Senior leadership should take the lead in championing this initiative, possibly as part of a broader privacy or border protection campaign. Our involvement in this process can be minimal.

Data loss prevention is a significant use case for us. I'm not on the security team, so I don't know exactly what kicked it off, but I believe we wanted Purview for the DLP capabilities first, and that led to us taking advantage of the other aspects of the solution. We have Azure, Purview, Defender, and all of the other Microsoft products. We're trying to leverage and use all of them. 

We have Intune for deployments and things like that. We're rolling out the zero-trust model right now. We use Jamf to manage our Macs because I'm not knowledgeable enough to Intune correctly, and it doesn't have the functionality that Jamf does. We can move over to Intune or whatever. So I think they're definitely trying to push me that way.

I don't know if I've gotten much value out of Purview personally, but our security team loves it. Our biggest concern is leakage or theft of our data because we have a lot of PII and stuff that has not been released. We like the insights Purview provides and the way the solution can track and manage things. I'd say that was probably their favorite piece of it so far. From everything the security team has told me, the policy management and DLP features are working spectacularly.

We have had some issues automating our document management with Power Apps. I haven't been super-disappointed with anything except for Power Apps, which kinda drives me nuts. I think it's because I am a coder who can do things properly, and I keep trying to do things there, but it's not working out the way. The security team is pretty quick. I'm kind of a thorn in their side. I always try to get around stuff. They haven't come to me for anything saying, "Hey, I can't find this information." They're pretty good. Maybe, there's a lack of documentation, but that doesn't seem to be an issue for our team. 

Another thing involves SharePoint. We have everything in SharePoint up on the cloud, and we want to ensure it's secure, so we have blocked all external access. You need to have one of our devices and our codes. But the C suite wasn't pleased because it was accessible externally for a while. And we have a penetration company that does testing. They were able to harass one of our users enough that they finally clicked the button that says "Approve this Login," so it just takes one time. 

They find red flags everywhere in organizations. The gut reaction was to cut off external access for now and figure out what we can do down the road after that, but this is a stopgap measure. However, the C suite told us that it wasn't good enough, but there was no way somebody outside could access our systems. You need to be on a trusted IP or our VPN. We have conditional access configured.  

We hired an actual outside consultant company to come in And I've been working with them for close to a year now. We're trying to leverage Purview and Power Apps to automate our document management. We have a ticket open with Microsoft because that's one more thing we're struggling with. It's supposed to go through and look for any PII data, like Social Security numbers, etc. We also have really low retention policies. For example, our emails are retained for only six months maximum. Team conversations are saved for two days. They're they're brutal. Legal discovery can be expensive, so they want to make sure we don't have anything to discover. 

I'm wondering if Purview can do some of the things that we're struggling with, and we're tripping over ourselves because the other thing we did was configure it so you have to be in a special group to even access those files. I might be wrong, but I'm pretty sure that Purview Information Protection has a labeling component. Still, I don't know how much it organizes labeled documents, and I think it also includes labeling after detecting user behavior that the system tracks.  They talked about something similar in one of the keynotes I recently listened to. I'm like, "Why are we not doing that?"  I'm looking at how we're just beating our heads against the wall. Even if we get this in place, it would still be very challenging. 

We like this In terms of usability and security. It will be difficult for our teams to do their jobs with all this other garbage in place. At this point, we've got it almost always set up, but it isn't working the way we need it to on the Power Apps side of things. 

And we've got a ticket open with the Power Apps team to figure out why it isn't working because it's supposed to be on a scheduled thing, but we've let it sit for weeks at a time, and nothing ever happens. It doesn't run. And there's no way to monitor. We don't know if it's doing anything, or we can look at our files to make sure that could be improved. 

We started using Purview in the last six months.

We are a new company. We broke off from a much larger organization three years ago, but we had about 3,000 people in the last organization, and we're down to 300. Before Purview, I don't think we had anything for DLP because there was so much to do. It was all hands on deck for about a year and a half where we were just trying to get that stuff done.

We have dev and production environments in AWS, and we're using native AWS tools to monitor the applications over there. I don't know how effective they are compared to Purview. We outsourced all of that to another company. The guy who owns it used to work with us.

I am not involved in purchasing. My company is willing to throw as much money as needed to be as secure as possible. Security is our priority, so we'd probably pay for it even if it was pretty expensive.

I rate Microsoft Purview eight out of 10.