Microsoft Purview Data Governance Reviews

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.

To ensure compliance with numerous regulations for our data governance initiative, we employ Microsoft Purview for data classification.

In our specific case, we only have on-premises servers and the same Microsoft cloud platform, Azure. I have not used Microsoft Purview with any other cloud providers like AWS or anything like that. However, it appears that Purview can be used to protect data across multiple clouds and platforms.

In the future, it could be important for us that Purview can connect to iOS, Mac, and Android devices. We will be onboarding data that requires updating some of the tables, descriptions, and other aspects. In that case, it would be beneficial for users to be able to access it from different devices. However, in my case and for the people in IT, we will always be using computers.

Microsoft Purview's native integration with Azure Dynamics and Office compliance is good. We have utilized it with Synapse Analytics and Data Factory, both Microsoft products. The integration is seamless and efficient. However, in the context of Synapse Analytics, its value proposition is less evident. While it is a nice feature, I cannot fully grasp its significance.

It is crucial that Purview was built with consideration for critical regulations from around the world. This is an integral part of the classification rules and it simplifies our work. However, I haven't seen specific references to regulations such as GDPR or PII. There are numerous laws in different states, as well as preferences here in Canada, but I haven't come across specific examples. Nevertheless, the classifications encompass a wide range of government information, sensitive data like financial information, and personal information based on various formats that we can even adjust or create our own. So, it's a positive aspect.

Purview has assisted us in creating an updated catalog that is more realistic. It has also enabled us to quickly classify our data. Additionally, we aim to enrich the data catalog with more metadata, both now and in the future. While this process is primarily manual, we are exploring ways to involve business users to streamline it.

It has improved the visibility into our estate.

Purview allows us to demonstrate our compliance on a near real-time basis. While executing a single scan will provide updated information, it doesn't provide true real-time visibility. To achieve the closest to real-time compliance monitoring, we can execute data extraction processes every four hours.

We have saved around 40 hours per month on some of our projects, which also leads to cost savings.

The ability to classify data quickly and effortlessly is arguably Microsoft Purview's most valuable feature. It can scan all tables and columns, identifying those that contain personal names, date builds, or other sensitive information.

I am interested in exploring the process of data scanning to identify data lines that do not contain stored procedures. This would allow us to detect potential black boxes within our data, where we are unable to trace the flow of information and identify all instances of stored procedures. Additionally, we would like to expand the reporting capabilities beyond Power BI to encompass other visualization tools such as Tableau, Looker, and others.

Reflecting organizational changes within Purview is impractical. Any such changes necessitate discarding existing data and starting anew, which increases both the cost and time required for maintenance. Therefore, I believe that enhancing Purview's maintainability is crucial.

I have been using Microsoft Purview for one year.

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

Purview is easily scalable in the cloud.

The technical support team was readily available for a Zoom call and was able to view my screen and provide assistance. The only downside was that I ultimately resolved the issue myself, which suggests that the local Microsoft support may not be as knowledgeable.

Positive

I have used other solutions other than Purview but it doesn't encompass the entire data management lifecycle. For example, Tableau has a data management suite, but it's primarily focused on analyzing reports, enforcing visualization governance, and managing data within Tableau itself. It doesn't extend to data sources or beyond that. Other data management tools in development offer similar functionality, but they may not have specific classifications for personal information.

The initial deployment was straightforward. The cloud administrator handled the subscription and all the necessary paperwork, while I proceeded with the setup.

The price is reasonable considering its value.

I would rate Microsoft Purview nine out of ten. Purview is a good product but still has some areas to improve.

Thus far, we haven't had any comprehensive maintenance for Purview. While there is maintenance required for scanning new servers, that's essentially the extent of our maintenance efforts. We may need to make significant changes to Purview's structure to enhance its usability. Purview's current structure resembles that of an organizational department. For instance, if a marketing application is mistakenly scanned under HR, I cannot simply move it to the correct location. Instead, I must discard all existing data and start from scratch.

Our primary use cases involve sensitivity labels and data loss prevention. Within data governance, our focus is on ensuring the security of data that leaves our locations and that only authorized people view it.

The data protection feature is vital as it controls who can access data when it moves out of our protected boundary. Additionally, it helps us meet federal regulations by ensuring that sensitive data does not get out into the world where we don't want it to be.

We are currently in the rollout phase, so I am not entirely sure about specific areas of improvement. However, there are some problems with DLP rules, and it would be great if the security around DLP could be expanded.

I've used Microsoft Purview Data Governance for about a year.

We are in the rollout phase, so I don't know much about its stability yet.

The scalability is probably solid.

I rate Microsoft support seven out of 10. The support could be better, particularly with consulting.

Neutral

The initial testing has been fairly smooth. There's a learning curve. We're still figuring out the product's limitations. 

We did everything in-house for the deployment.

On a scale of one to ten, I would rate the overall solution as an eight.

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.

I was working for a nonprofit here in Kansas called Children International. I was a global data engineering manager, and I was tasked specifically with developing a data governance program. And at the same time, that's right when Purview came out. So I spent a year in that realm. I've been very plugged into Purview ever since.

The main use is data governance. Now, not every firm is necessarily at that maturity level when it comes to understanding data as an asset. So, a lot of companies can use it just as a data dictionary, a business glossary, which is nice, but it doesn't give the entire picture of what Purview can actually do, and so, actually, there were a dozen of implementations of Purview that I have been a part of in the past. I've led as a consultant and an architect. I'd say maybe I have used twenty-five percent of every feature that it has to offer. I am still kind of catching up with the rest of the features.

Microsoft Purview breaks down barriers to sharing information, accessing data, understanding what a piece of data means, how it is defined, how it's interpreted, and then how the end user uses it. So, with Purview, when it's best used, and it is at its best when the end users are the ones that are very involved because they're the ones who are going to be using it. Its users can see the support, and it grows year over year, you know, a kind of revenue measure. I don't know how exactly this is created. Also, I don't know what fields it uses. I don't know exactly what this means. We have a different department in the company that may need this. So they feel the need to go out and then hop to Purview. So it definitely knocks down a lot of barriers. It eliminates a lot of needless communication between different departments, and it just centralizes all information about an organization's data assets.

Speaking of the valuable features, I would speak on behalf of my clients, considering how it seemed when it was implemented. So, the sensitivity labels are big. The insights are also very nice as it gives the visual representation of being able to look at what or how the data storage is performing, especially monitoring if they are tagging technical assets or if they are adding business glossary terms. So, that's big, along with the basic features of Microsoft Purview. I'd say the last one that is very big with most clients is data lineage and being able to integrate that end-to-end flow component kind of so they can see that this is data from a Power BI dataset, and then they can follow where that dataset is coming from like it's from a SQL query in a Power BI report itself and data coming from a SQL Server, etcetera, etcetera.

The out-of-the-box connectors and being able to connect to third-party apps and data storage were some of the areas where they started off strong, but that's something that I think needs to continuously be at the forefront of the developers and the engineers for Purview to make sure that it is constantly up to date and can talk with any data source that it may need within a data state. So I would say that's not necessarily a con, but it's a possible weak point that could be strengthened.

I've been implementing Microsoft Purview with my clients for three and a half years. I'm a consultant for a Microsoft partner.

I think Purview, in terms of its stability, a lot of people think Purview itself is for data governance. Whereas data governance is something that is more like how we now view, let's say, Toyota six sigma or Agile, where it's kind of embedded in an organization and kind of culturally and throughout the work that's being done, it's kind of embedded in the network. I think Purview is kind of the same way. So, data governance operates in the same way. It first needs to be adopted and agreed upon by those that will be using it. Purview is the tool, and that's, like, the actual interface, and that's the actual, you know, that's the tool that allows it to be done. But in terms of stability, I think Purview does as good a job as it can of providing a foundation to make stability with data governance as easy as possible for those that manage it, but it does come down to those that are in charge of Purview itself to make sure that it stays stable. Well, I won't just say stable. I'll say that it is as stable as the data governance maturity that exists within an organization. It can't be more stable than that.

Scalability is fantastic considering their pricing since it addresses their pricing where it can have your incremental scans, which can cut down on your computing costs. That's great for scalability. So, if you have more data and you need to scan more and more, you don't need to scan the exact same data again and again and again. You may be okay only scanning the entire database maybe once a week, and then, let's say daily, you have incremental refreshers that help very much, or that help a lot with scalability. I think as more an organization scales and the more that it uses Purview with that scaling, the more you can get out of it, and the more it'll end up helping the organization, the more the stewards that are in their tagging things, the more that data is suggested, and that triggers are set up for ingestion runs. The more it scales, the better it is.

I have spoken with Purview's product team consisting of engineers who created Purview that writes the documentation that will work on bugs hands-on. Also, I've been a part of a lot of conversations, and I provided a lot of feedback in terms of improving Purview itself as a product and how we use it with our clients. So, there's been a lot of collaboration on that.

Considering Purview, I rate technical support a ten out of ten.

Positive

There was not one solution. There were multiple solutions like Profisee involved. We also had Atlas and kind of a lot of commingling of those two and kind of piecemeal together solutions between a lot of those to do a Purview does. So not a whole lot, I guess, is what I'm trying to say.

The deployment of the solution was done on Azure. A majority of our deployments for our clients are through a private cloud, and they're locked down with private DNS zones and custom DNS records on the back end if they're on their own servers and private endpoints as well. So fairly locked down, especially with where we talked about a lot of the data being sensitive and a need for it to be protected and monitored. Well, if data needs to be protected and monitored, then it likely is going to be needing something to be secure. So it's all been on a private cloud so far.

I was involved in the initial deployment of Purview. The initial deployments were actually straightforward because we were figuring out about the features, and found that it was a little less feature-rich, so there was less of a question. And it hasn't given us the time to figure out where it works well or where it doesn't work well, and if we need to bring in consultants or can we do this in-house. As Microsoft Purview got a little more mature, the deployments got a little more complex, as we were kind of seeing that there are a lot of ways, like there were a hundred ways to do one thing or less. I think that applies to anything in software. But it applies to Purview as well and where we control access to a given data source while figuring out if we should use the policies and governance features within Purview. We also thought if we should do it in Azure portal using RBAC or should it be elsewhere. So I think we passed that part, and then now we're going to get back to some smooth deployments, and a lot of them will be templatized, you know, whether it be in ARM templates or Bicep like Terraform. Overall, at first, the setup process was fairly smooth to moderate.

I have not been able to conduct any actual ROI analysis on Purview just because it is hard to measure those kinds of intangibles of how those results show up. But they absolutely show up if we consider data to be an asset. Also then, it can also be a liability, just like something that would be like a can of soup on the shelf in a restaurant. That's an asset as it exists then, but also there can be hazards. So, if it's a large pallet, it could fall and cause damage. So, data cost would be a liability. I think that it is not something that currently appears on the balance sheet and can be cut to draw that line, but I think it'll be made much clearer in the near future, especially as we've become more and more data-saturated and we'll be more conscious of the value of data. Regarding ROI, I have not done any analysis in that realm, but I have full confidence that there are real ROIs that do exist and that will show up one way or another in the future.

Price-wise, I think it's very generous and accessible to not just enterprises but small to medium-sized companies as well. I think it's very fair in terms of how they break apart the storage and the actual computing, and that makes it very accessible. So, that is a very big plus for Purview. I think a lot of clients and organizations would feel that way as well.

On the time front, I can absolutely speak about the cost of the solution since time is money. Saving analysts or developers, or engineers time can add or translate into actual savings if you can do the right calculation. But just to stick on that time front, I've seen it cut down, let's say, a given team, or a data governance team, I'd say, in a reduction of fifty to sixty percent of the time that would be spent answering maybe questions for other parts of the business about what a certain data means or where this data lives, they can just point them into certain directions, and they can point them to Purview and have those answers or have or have this questions answered. So that's a big part. And then also being able to have those ties from the business to IT and being able to bridge that gap and being able to have a technical asset ingested from the data side or, from the technical side, and then being able to get the business to interact with that as well. I would say that total savings in terms of on a team-to-team basis, I could see anywhere from fifty to seventy-five percent reduction in time spent on those activities just by having Purview.

After looking through other options, we decided for our clients that in these situations where they're already in a Microsoft data environment in terms of their data, whether it's living in Azure or on-prem, but the analytics that they're doing, whether it be with Power BI, with Synapse and Data Factory, it integrated so well.

Speaking about the importance that Purview delivers data protection across multi-cloud and multi-platform environments, including AWS and Google Cloud Platform, I would say that it's very important, and I am going to lean on the side of this that has to do with data protection in terms of international data protection and various laws that kind of force data to stay in certain places. For example, I have one of my clients, which is a Fortune 100 company, and they have three different main regions around the world, including Asia Pacific, the EU, and the US. They had a lot of financial data that were in these three regions, but they couldn't cross each other even though it was the same data that was being used in the same applications, but it was difficult due to various barriers and regulations for the actual data control. Hence, they couldn't pass between each other. So that was kind of an issue. We had to actually go and deploy multiple instances of Purview. We had a dev and a prod instance in these three regions. That was definitely very important, and that was because of not only regulations but because of their desire to keep their data private, secure, and kind of locked down.

Speaking of how important it is for me that Purview can connect to iOS, Mac, and Android devices and data in other SaaS apps, it is not very important as it's typically with legacy databases and data warehouses.

Regarding Purview's data connector platform for supporting ingestion from non-Microsoft data sources, I think it's very robust, and out of the gate, they included a data connector that you can plug in straight to Amazon and SAP. I believe now that they have some connectors for Salesforce and things like that and Snowflake. So they are absolutely staying right on or ahead of the curve when it comes to making this kind of making sure that the interoperability between other vendors as well is taken into account, which is awesome.

Speaking of how important is Purview's natively integrated compliance across Azure Dynamics and Office, I think it's very important, and it does it very well. I mean, literally without a problem. It's completely seamless, and so it does that perfectly.

Speaking of how important it is to me that Purview was built taking into account critical regulations from around the world, I think that it is very important. So, that's what kind of gave birth to the original classifications for 200 or so out-of-the-box classifications for a lot of data for possible credit card numbers, passport data, and ZIP codes in different countries. They were definitely aware of that, and you could tell from their design process they keep updating those. And so that was definitely built with that in mind for sure.

I have never used Purview for data loss protection. Typically, in these solutions, when we're deploying Purview, they're usually at a stage in their data platform maturity where they already kind of have that taken care of elsewhere.

Speaking of whether Purview helped reduce the number of solutions I need to interact with, I would say that I don't think so because I think data governance exists kind of outside the solution's architecture for these kinds of things. So, I'll say no, but that's not in a bad way. It's just not its job, in my opinion.

In terms of Purview's visibility, I think visibility is the most significant part since that's kind of what it does as long as it's set up correctly and maintained by the data stewards and the business experts. The domain experts that actually know how to interpret these business glossary terms and can link them to data assets, then it is the most useful tool out there.

I haven't used Microsoft Purview's automation. However, I have used Purview's AI since we have had a few situations. While not many organizations have had to do this, we had two instances of Purview in a given tenant, which would be dev and prod. So, we would use some APIs and some Purview CLI. We automated a lot of those processes. Also, it's workflow automation in terms of approvals and sign-offs from a given definition being changed or a term being added and being able to send that to the right people, especially by sending an email to the right group for approval. So the automation piece is huge. I have not yet been a part of, or I have not, used any of the AI-related features.

Speaking of how automation affected my speed and accuracy of risk detection, I would say it went very well, especially when dealing with financial data or when dealing with possible credit card data, personal information, and health data. In PII or PHI, being able to have those classifications kind of flag that data if it comes through, and then being able to mask it or identify those is something huge. So, that's probably one of my favorite features considering how it's integrated into the various protection services that Microsoft and Azure have to offer.

Speaking of how automation affected the quality of the insights I have, I would say it has more to do with speed on that front. Also, it's going to be as good as the developers, data stewards, and experts working on it. As you know, it'll be as good as the effort that they put in to constantly go through and curate or update a certain classification, including what the threshold may be to make sure it's catching all of where it needs to cache for risk detection or risk mitigation. And there's definitely a one-to-one relationship that is a very linear relationship. So the more end users and stewards are involved, the more you get out of it in terms of every feature that it has to offer.

Regarding Purview enabling me to show my compliance in real-time, I would say that I believe that there are some integrations that I have not personally, which I think came out in Purview the last time when I was very heavily involved with Purview, which is maybe four or five months back. So, I have not used those yet. But in terms of real-time, I don't think we have used it yet. But I'm sure we'll do that eventually.

Regarding whether Purview helped to reduce the time to action needed for insider threats, I would say it has, especially in the context of early detection for possible sensitive data, like health data, credit card information, and things like that, and being able to alert the right parties. So, they can make decisions on whether they need a mask or not or if there was a problem with the actual data source, whether the data kind of slipped through, and if it should have been taken out. So, definitely, it works in that kind of early detection there and in terms of the speed of making those decisions.

I would say that Purview has helped save time and money for my clients. So, it's definitely a long road for data governance, and a lot of the benefits aren't necessarily very tangible, so they might not show up on the balance sheet. However, data is an asset and needs to be treated as such. Hence, those who implement these data governance programs and who use Purview to do that are absolutely gonna be ahead of the curve, and we'll save countless dollars and time. I mean, the savings start immediately. So, down the road is when you really see those effects come up.

I would agree that Purview has affected my ability to stay on top of compliance.

Regarding others who are looking into evaluating the solution, I think they should prepare by making sure that the individuals or the teams that internally exist that are in charge of or that have a very large say, and how data governance is or functions within that organization, they need to be on board and they need to be willing to kind of to go through the motions and be okay with having an iterative process once Purview is deployed. It's not all going to be solved on day one, and they're not going to have everything that they need right away. Again, it's a tool that their data storage and domain experts can use, I would say.

As I am trying to be as unbiased as possible, I would suggest those planning to use the solution contact Microsoft since there are a lot of financial incentives and reimbursements, and discounts that exist right now, also in the past, and in the future, I would assume that for Purview's demos and PoC engagements. So, trying to find or just having the first part, which is the internal understanding of what data governance is and what they want out of it, while the second part is Microsoft does very well by tucking in partners that can show them ropes.

Since there were some features recently that maybe I haven't been able to test, I rate the overall solution a nine out of ten.

In both my previous and current organizations, I've worked with Microsoft Purview. While my previous company had a premium license for all services, my current one doesn't. At my previous company, I used Purview to design communication compliance policies, likely leveraging some pre-built policies from Microsoft security. Initially, we lacked a specific goal, but my exploration of the platform led me to pursue a cybersecurity certification to optimize its use. This helped me design DLP policies more effectively and implement signing for communication compliance policies. Recently, I discovered eDiscovery and its value for exporting large datasets for specific employees based on their protection level. Lastly, I found its activity tracking feature particularly useful for monitoring employee movements in our large, partially remote workforce of nearly 100 employees, with less than half in the main office. This tracking proved valuable for detecting potential data leaks during employee departures. I briefly explored Insight Risk Management during a one-month license trial.

Purview's multi-platform capabilities, supporting iOS, Mac, and Android, have been invaluable to me. As a beginner in device management software, the prospect of using another option with a large web portal felt daunting. Purview's ability to manage devices across different operating systems saved me significant time.

At my previous company, all internal data lived in Azure, but client data resided in Salesforce. This siloed structure made comprehensive data control impractical without a tool like Purview that seamlessly supports ingestion from non-Microsoft data sources.

Purview's natively integrated compliance across Azure Dynamics 365 and Office 365 is even stronger than its ability to integrate with third-party solutions.

It's crucial that Purview was built with critical regulations from around the world in mind, especially for those of us in the European Union where EU regulations apply. This is a key consideration for everyone involved in data governance. While some frameworks offer vast data capabilities, the sheer volume of work required for a medium-sized business to ensure compliance with regulations across all these frameworks would be insurmountable.

I initially found the DLP system overwhelming due to its capabilities exceeding the needs of our small organization, where I implemented simpler policies. However, it proved valuable for ensuring compliance with GDPR, and PCI DSS and provided visibility into sensitive data sharing.

Purview has saved our organization a huge amount of money and time.

Through Purview, we were able to streamline our technology stack by consolidating the number of solutions we relied on. This prompted us to re-evaluate our vendor landscape, ultimately leading us to migrate everything to Microsoft and leverage their comprehensive suite of tools. Surprisingly, most of the functionalities we previously paid for were already available within the Microsoft ecosystem. This simplified our IT infrastructure, transitioning us from a predominantly on-premises setup to a cloud-based one, with Microsoft solutions forming the core of our cloud environment.

Purview has improved my ability to stay on top of compliance.

The most valuable feature is the tracking activity and device onboarding.

I have some concerns about the separation of roles in Purview from the Microsoft tenant, as well as how they interact with the security portal and endpoint manager. Certain permission issues or protracted permission updates could arise due to suboptimal configuration, potentially extending the expected timeframe.

I have been using Microsoft Purview for two years.

Microsoft Purview is stable in protection but there are some bugs in the GUI.

Designed for enterprise-level organizations, Microsoft Purview scales effortlessly.

The initial deployment was straightforward. I was able to do the entire deployment with the help of one other person.

We used a Microsoft partner when we started working with the tenant before starting to use Purview.

While Purview's standard pricing might not be accessible to most small businesses, we were fortunate to benefit from the educational pricing which made it a financially viable option for our needs.

I would rate Microsoft Purview a nine out of ten.

Maintaining Purview is essential, as some internal problems, like endpoints disconnecting within the organization, can develop over time.

To fully leverage Microsoft Purview's capabilities, it is recommended that one first familiarize themselves with the organization's existing infrastructure.

Our goal was to provide insights into the latest data entries, implement governance measures, identify and classify sensitive data, and address specific business use cases. The primary use cases revolved around establishing a comprehensive data lineage, accompanied by pertinent metadata. This was primarily aimed at providing a business-centric dashboard, enabling stakeholders to visualize how data moves from one point to another and ultimately reaches the target. 

In my experience, I've utilized it on Windows machines with Blackfish without encountering any issues.

The dashboard offers insights into the nature of the data, and the transformations occurring between different columns, and allows for traceability to identify any issues that may arise. These use cases have proven highly beneficial not only for business analysis but also for support activities. For instance, it aids support personnel in quickly identifying issues such as missing data or anomalies, streamlining the troubleshooting process for efficient problem resolution.

Purview facilitates data management across diverse cloud and platform environments, encompassing AWS and GCP. However, my experience has been exclusively with Azure. Given that my ecosystem operates within Azure, both the source and target activities are conducted seamlessly within the Azure framework. The integration is smooth since Microsoft Purview is inherently designed for Microsoft components, making it effortless to establish connections and retrieve the required data. I haven't employed it for other sources or alternative cloud systems.

The importance of Purview lies in its careful consideration of critical global regulations. As a data governance solution, it plays a crucial role in business development processes. Given the potentially sensitive nature of incoming data, proper classification is essential to ensure specialized treatment. This facilitates easy access for subsequent activities such as metadata modifications or updates, providing sufficient information for comprehension by business personnel. The tool proves beneficial for data quality officers, enabling them to monitor data and detect any discrepancies, empowering them to take necessary actions. In the realm of the cloud, Purview emerges as a highly valuable data governance solution.

The integration of Microsoft Purview has significantly reduced the need for multiple solutions to interact within our company. This reduction not only streamlines processes but also saves time. For example, when a problem arises, understanding, identifying, and resolving it becomes much easier compared to the traditional approach of tracing through multiple systems for the root cause. With Microsoft Purview, the identification process is simplified, leading to potential savings in support efforts. Business stakeholders also benefit by gaining more visibility into how data flows through the system and understanding the metadata information without relying heavily on support or technical personnel. This autonomy enhances their ability to assess and comprehend the situation independently.

I haven't implemented it to enhance response time for insider threats by applying security measures. However, the tool does provide visibility into the movement of data, allowing the data control officer to monitor and classify alarms promptly. In the event of an alert, appropriate actions can be taken accordingly.

Efforts have significantly diminished, and this reduction is directly proportional to cost savings. As a technical person involved in both solution development and support processes, I've observed a reduction of more than fifty percent. The turnaround time for issue resolution has notably decreased. Previously, it took others a considerable amount of time to identify the root cause, but with Microsoft Purview, pinpointing issues and finding solutions has become much more efficient.

It has had a significant impact on our capacity to maintain compliance. As a data governance solution, it offers features essential for ensuring that compliance requirements are thoroughly met, and data processing aligns with regulatory standards.

The user interface is highly intuitive and user-friendly.

I appreciate it because it provides a unified solution. Everything can be managed in one place, from scanning sources to making assets available. The access includes comprehensive metadata information, presented in a non-technical manner for easy comprehension of the asset's nature. The visualization it offers is quite clear. Additionally, it creates a lineage based on data processing, allowing for workflow authorization and control over metadata modifications or other activities. 

It caters to the entire micro-ecosystem, providing connectivity and seamless data flow. It allows for scanning, asset discovery, and data coverage. While there are some existing limitations, it's important to note that the tool is continuously evolving. I believe it holds great potential and will become an excellent resource for development in the future.

Purview's data connector platform is designed to facilitate ingestion from non-Microsoft data sources. I've personally applied this feature to one of our sources, an Oracle database. Specifically, we utilized ADA for data permissions and seamlessly integrated it with the Azure Data Factory pipeline. This automated the connection to Oracle, enabling the setup of data extraction and loading processes. Overall, it proved to be a valuable and effective feature.

Enhancing the tool's capability to connect to multiple sources would be valuable. Also, when data is transformed in other systems, the tool should capture the relevant metadata and generate lineage for those systems as well. Thirdly, addressing limitations, such as relying on Apache Atlas for mitigation, should be handled within the Microsoft tool itself rather than external dependencies like Apache Atlas.

I have been using it for approximately six months.

The stability is satisfactory, and I would give it a rating of eight out of ten.

I have utilized it in a cloud environment, and scalability is assured.

I am content with technical support, but for various inquiries, the responses often indicate that the feature is either not available or still in a previous state. I would rate it eight out of ten.

Positive

The initial setup was straightforward. Even individuals with less technical expertise can do it.

Deployment spanned a week and involved six different individuals.

Maintenance becomes necessary when leveraging external APIs and tools, especially concerning access management. However, once the initial setup using MS Purview is complete, ongoing maintenance is minimal. Automation takes over with continuous scanning, automatic data classification, and sensitivity labeling. Workflows can be established and utilized for an extended period, reducing the need for frequent maintenance.

I consider it cost-efficient because of the metrics it provides. With each scan being incremental, avoiding redundant scans of the same object, the tool offers a way to manage costs effectively.

We didn't extensively evaluate other options because Microsoft Purview successfully met the requirements for the specific tasks at hand. However, during implementation, I became aware of more mature tools available in the market that might offer greater capabilities. It seems that Microsoft Purview is still evolving compared to these more established alternatives.

In my scenario, I encountered difficulty connecting to a file system database, especially when it was located on a different server. Additionally, when working with an in-house solution like Azure Data Factory, while Microsoft Purview can successfully bring metrics to tables as assets, it faces limitations in identifying the leading use of those assets. For instance, a database solution handling ETL activities may not seamlessly provide insights into the transformations, sources, immediate obligations, and final targets associated with a specific asset, making it challenging to track its usage directly within Microsoft Purview.

I would strongly recommend Microsoft Purview when utilizing solutions within the Microsoft ecosystem, such as Data Factory, various applications, and databases.

Overall, I would rate it a seven out of ten because several features are still in a preliminary state. Given that it is in preview, it may not be as stable or fully functional yet. Also, the absence of data quality and data profiling mechanisms contributes to this rating.

As a consultant, I work with clients to sell the idea of data governance. In doing so, we do POCs, proof of concepts, and MVPs, which are minimal, viable products. 

For Microsoft Purview, most of the time, it's also associated with other products -whether it's ADS, Synapse, Key Vault, Databricks, storage accounts, Kubernetes, et cetera. 

I also worked on a project to integrate it with processing. I created a data governance accelerator combined into two products, including Synapse, and we sell that to customers.

The data catalog, the data lineage, the data glossary, and the classification are the key features I appreciate, along with the tight security, and role-based security.

There are two flavors of Purview. There's the compliance, which it does the security and all that. And then there's the Microsoft side, which is the data side. I primarily work on the data side. 

I like that Purview can connect to IOS, Mac, Android, and other SaaS apps.

Its data connector platform for supporting ingestion from non-Microsoft data sources works really well. We can use it either through a self-hosted integration runtime or on a VM. Or it can capture data from just about anywhere. There are about 100+ connectors. It's great.

Its natively integrated compliance across Azure Dynamics is a game changer. Back in the day, we never had anything like that. It provides self-service. It provides easy look-up and glossary terms. It also requires a new role called the data steward which we never had before.

It was built to take into account critical regulations from around the world. Now it's no longer something that's nice to have - it's necessary.

Purview helped to reduce the number of solutions we need to interact with each other. If you were to do this custom, it'd be very difficult. It's so easy to use and stand up and configure. There are some configuration requirements that are not self-explanatory. It takes some research; however, we already figured out all those things.

Purview affected the visibility we have into our estate. Now we have a complete ecosystem of where the data is, and it's a lineage. It's a game-changer.

I've used AI and automation in Purview. That's what the scans are. It uses AI to determine the classification. It's built-in. It's under the hood. People don't see it.

Our speed and accuracy of risk detection are good. From a compliance perspective, it helps identify sensitive information by classification. 

The product has helped us save both time and money. From a time perspective, there's an initial upfront cost to stand it up and configure it. However, once it's running, there's very little to do. So there's a one-time hit up front for the implementation in configuration, yet downstream, there's significant time reduction.

Money-wise, it's the same thing. You're only charged for when you run the scan since the storage is minimal. So there are ways to reduce cost, and that is by running it less frequently. Also, there's a whole bunch of out-of-the-box classifications that aren't required. There are ways to increase your cost reduction. Of course, that is not self-explanatory. You have to work with it for a while to know that.

The one thing it doesn't do is data quality. That's its only pitfall. The problem is people think it does. So either they're not marketing it right, or, eventually, it's on the road map, and they haven't got to that part yet.

In order to get data in and out, you have to use custom code using Python. That's an inconvenience, and almost every customer wants that feature. For example, let's say I run some scans on some data, and then that data goes away. This issue is Purview still shows it. There's no easy way to clean up your orphan data. That's a problem.

I've used the solution since 2015.

The stability is very good. Microsoft is solid on the cloud. 

The scalability is quite nice. 

They just changed their model so that you're only allowed one Purview per tenant. So you either get the free one, which is limited, or you purchase the enterprise one, which costs money. However, you only get one per tenant. That's a change they made within the last two months. You can't have three Purviews in the same tenant anymore. That change required a redesign of how people implement it. That said, they are offering it for free. 

I've worked for Microsoft to help a client who was having difficulty. I documented it. We had a backlog where other people were experiencing the same problems. You can reach out via phone or email. 

I did not previously use a different solution.

I was involved with the initial setup. I also can configure it. There is quite a bit of configuration required as you need it to speak with other resources. 

The initial installation is pretty easy. It is like any install on Azure. You just enter a few parameters, and it builds it. Then, if you want to start adding resources, there's a bit of configuration. It only takes about ten minutes. However, you have to know which settings you have to add. 

Only one person is needed to deploy the solution. 

Once it is up, there is very little maintenance going forward.

The cost is pay-as-you-go. It provides easy ramp-up and very little maintenance down the road. If you want to shut it down, you just delete it. It's easy to use, easy to configure, and the costs aren't that great. 

I could see more and more companies using this going forward if they're already in Azure, and it's so easy to set up. It's a requirement now as well since data is the lifeblood of any organization. If you have bad data or you don't know where it is, or suffer from data silos, this will solve all that.

We're a Microsoft Gold Partner. 

I'd rate the solution nine out of ten.

Using the Microsoft unified cloud-based data governance is going to allow users to gather data across the entire ecosystem, classify it, place a glossary on top, and look at the lineage in addition to a whole bunch more. They have self-service policies and DevOps policies. Microsoft is heavily funding this tool, and it's now a requirement, not nice to have. Just about every Azure customer is going to incorporate Purview into their ecosystem, and it's going to help govern their data, which is an asset that will help companies increase sales, reduce costs, and streamline processes.