Microsoft Purview Data Governance Reviews

Microsoft Purview has several built-in solutions, including data loss prevention, e-discovery, life cycle management, and information protection. It functions as a DLP tool and includes a compliance portal that enables integration with various other solutions to ensure compliance. Therefore, it provides readily available integrations.

The solution deployed as a SaaS.

It is crucial for Microsoft Purview to offer data protection across various cloud platforms because many customers are now utilizing cloud technology. It is not always the case that everyone will use Azure exclusively, as many customers may have multiple cloud vendors. Therefore, it is essential to support multifunctional or multi-vendor flows to meet the needs of these customers.

To ensure proper functionality and data security, we need to accommodate a wide range of operating systems. Therefore, our solution must support multiple vendors or be multi-tenant, allowing us to have visibility over all devices within our network.

It is important that Microsoft Purview is globally compliant. The solution comes with pre-defined rules and policies, providing us with a wide range of capabilities to manage multiple geolocations simultaneously.

Microsoft Purview's data loss protection feature is helpful in remediating policy violations as it provides extensive forensic data. This includes information such as the user, the activity performed, the starting point, and the flow path of the activity. Additionally, the tool has forensic analytics capabilities that enable us to identify and prioritize policy violations effectively.

Educating users on data loss protection can be straightforward. For example, Microsoft's product includes integrated guides on the console. Whether the user is an individual or an administrator, if they are unsure how to use the product, there are supported guides and links available to assist them. This makes the experience easier and ensures that best practices are followed when managing data loss protection.

It was important that Microsoft extended Purview's data loss prevention to Mac OS endpoints because it enables us to manage all devices on our network through a single console.

Microsoft Purview has simplified my work with its effortless deployment.

Microsoft Purview has decreased the need for multiple solutions to communicate with each other. If we were to discuss other DLP solutions, an additional agent would need to be installed. However, Purview utilizes Defender, which enables it to capture data and obtain all necessary information without requiring the deployment of any other agents. Therefore, there is no need for any additional agents to be installed.

The solution provides visibility into the state of our organization by giving us inventory details and maintaining an updated version or list of the inventories that are currently in use. This allows us to have clear visibility of the devices we are using, specifically end devices. It also enables us to easily manage non-active or disconnected devices.

Microsoft Purview enables us to show our compliance in real-time. 

Microsoft Purview includes multiple predefined sets of compliance rules that can be compared to our specific compliance requirements. We can then map these rules to our policies.

The agent saves us the time and effort of manual reporting. When the device is active, the agents also become active and start reporting. The reporting process takes the same amount of time regardless of which policy we use.

Microsoft Purview helps us to maintain compliance by providing a checklist of tasks that need to be completed, along with mapping.

The ease of integration with other Microsoft solutions is the most valuable feature. 

The availability of pre-designed policies tailored to specific geolocations and customer requirements is also a valuable feature.

The Microsoft Purview data connector platform, which supports ingestion from non-Microsoft data sources, can be somewhat complex. For instance, when using Linux or Mac OS, additional agents are required. However, deploying these agents can lead to high resource consumption, such as increased CPU, hard disk, and RAM usage.

The performance has room for improvement. 

I have been using the solution for three months.

Microsoft Purview is a SaaS platform, so its stability is very good.

The scalability is all based on the license. 

The initial setup is straightforward. For our implementation strategy, we began by collecting inventory details. We then identified the supported devices by their operating systems, separating them into Windows, Mac OS, and Linux. For Linux devices, we created software packages offline and deployed them to the IT assistance team. After the agents started reporting on the console, we restarted the Linux devices. For Windows devices, we were able to connect directly. First, we were in the POC phase, testing a few devices and developing the rules and policies, followed by applying the rules to all the devices.

The number of people required for the deployment depends on our infrastructure and the size of our environment.

The implementation was completed in-house.

I give the solution a seven out of ten.

As a consulting firm, we utilize several Data Loss Prevention solutions such as Symantec DLP, Forcepoint DLP, and Microsoft Purview. Our recommendations to clients are based on their specific needs and financial plan.

Microsoft Purview comprises various solutions, and I recommend acquainting oneself with all of its aspects to make the most of the tool.

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.

We are using Microsoft Purview for Azure Information Protection and DLP to create automatic labeling and policies for sensitive labels. We are also using Insider Risk Management, Communication Compliance, and Records Management for our client.

Microsoft Purview provides data protection across multi-cloud and multi-platform environments, which is essential. Some of our clients require these measures because their systems must be secure and their data must be protected from loss for auditing purposes. Therefore, the client is requesting that we enable all of these features for the system.

It is important that Microsoft Purview was built taking into account critical regulations from around the world.

The data loss protection helps remediate policy violations.

Data loss protection helps educate users on how to handle sensitive data.

It improved our visibility into our environment.

Microsoft Purview helps us show our compliance in real time.

Microsoft Purview helps reduce our time to action against threats. It takes some time for the initial configuration, but it detects as soon as the configuration is enabled.

Microsoft Purview integrations with non-Microsoft products have room for improvement.

The technical support has room for improvement.

I have been using Microsoft Purview for four months.

Microsoft Purview is generally stable, but some of our clients occasionally experience accessibility issues when connecting to the cloud.

Microsoft Purview is scalable.

From a technical support standpoint, I have raised many tickets to date. Within this format, I have raised more than fifteen tickets for various purposes. I feel that few technical team members have a good understanding of the problems we are trying to explain. The rest of them waste our time. Typically, they say they will get back to us after two or three days, but then they come back to the same place they left off. Only a few technical team members are knowledgeable about Microsoft Purview. We still have tickets that are open to this date.

Neutral

The price is reasonable because most of our clients already have an E3 license, which makes implementation easy. For other clients who do not have an E3 license, the cost is higher because they must purchase the package.

I would rate Microsoft Purview seven out of ten.

Maintenance is done by the vendor.

I recommend Microsoft Purview for organizations with an existing E3 license, rather than spending money on a third-party DLP.

We use it for the text of emails. We use it to keep track of groups as well. We also use it to go through the mailbox of a former employee to retrieve the mailbox for a new employee. We use it for e-discovery and content search in emails across our organization.

We use it internally for just a few use cases. I know there are a lot of connections between it and other Microsoft applications and multiple clouds, but we don't have those use cases currently.

We carry out implementations for customers on these particular solutions. For example, if we're selling a Microsoft 365 solution to them, we use it to secure their data, especially their emails through backup, and SharePoint.

It has improved our ability to retain data and retrieve the data that we need at a future date.

We are also able to see how sensitive data flows across the organization, so it has been very helpful in telling us where that data is originally from and where it is being sent to. We have the ability to track it and control and restrict it from going outside our organization. We've benefited from that a lot.

Purview also enables us to show compliance in real time. We can see what the requirements are and then we can apply them across the organization. That has been very helpful.

It has also helped us to stay updated and make sure that we are not out of compliance. It keeps us updated with any new policies that are required for organizations like ours. That's of great value to us.

Another advantage is that it has definitely reduced the time-to-action on insider threats, although we don't measure that at the moment. But from experience, we can tell how much it is saving us in investigations, compared to before we had the solution.

The most valuable feature is the information protection, the way we're able to retain emails.

Another aspect that is very important is that Purview has been built to take critical regulations from around the world into account. It gives us trust that all of the compliance requirements are being met and that we just have to take care of our data. We don't have to worry about whether the regulations are being met around the infrastructure and we can just focus on our data. It's very important to us to have that level of trust in our systems.

Also, Purview's data loss protection for remediating policy violations is very good. It gives you the opportunity to know your data and apply policies around it. If those policies are flouted, you can always track what's happening. You have options such as alerting the person who is committing that action, or you can take automatic action by blocking, for example, an email that is being sent externally. It's very useful.

I've been using it since as far back as when it was Security and Compliance Center, before there was a separation between compliance and security. That happened around 2019, so I've been using it since 2019.

The stability is great. Like every SaaS application, there are infrastructure issues, maybe once a year. Overall, it's good.

The scalability is also great.

The service level agreement is excellent and the support follow-up is also great. They have good knowledge.

Positive

In terms of ROI, my bosses take care of that calculation, but I know we are getting benefit and value from Purview.

The categorization within the licensing could be improved. There are a lot of solutions within Microsoft Purview. If the licensing could be a bit clearer and the solutions could be better categorized according to function and across multiple environments, that would be excellent. The licensing is very confusing.

The pricing, for the solutions and value being provided, is fair. But that ties back to what I said about the licensing. There are a lot of standalone solutions you can get, and there are different licensing options for them. Depending on what you need, you can have a cost-effective solution; you can figure out your cost and benefit. It's affordable.

We are still exploring whether Purview can help reduce the number of solutions that we have interacting with each other. There are a lot of solutions within Microsoft Purview, but we still have some data that is on-prem and we are still looking at how we can expand and connect to those areas. It's something that is in progress.

In terms of maintenance, it's a SaaS solution, so the applications are automatically updated. There's almost zero maintenance. We do have to take care of configuration and updating preferences. I am able to handle that myself.

My advice is to develop a clear use case and a roadmap, perhaps from a consultant if you don't have the time, or spend some time doing research on it, because there are a lot of great solutions within Microsoft Purview. You need to have a strategy for the way you combine the solutions together.

The primary purpose is to catalog all the different data sources. The idea is to get insight into what is available and, more importantly, to document and better understand the data quickly and easily. You're not doing any manual work, you're just scanning sources, which means you can automate it. It automates the majority of the documenting process.

The most important benefit is its data documentation and the data catalog. It saves a lot of time compared to doing those things manually. Normally, when you want to describe your sources and get an overview of what is available, it takes a lot of time for data engineers and other people in the company to document the data. That whole issue is eliminated by using Purview.

Also, the fact that you can easily view your metadata helps with data exploration. A lot of the time, there are so many sources at a company that at some point, most people don't even know what is available anymore. A really key feature is that not just one person but lots of people can access it for the same price, to do data exploration. They can all see what is available and decide what they want to see in a company report, for example.

The beauty of Purview is that it's all about a central location where everyone goes. I wouldn't recommend creating multiple Purview instances, although you might have one for production and non-production. But, ideally, you would just have one Purview for your entire organization and then provide access to multiple people to make use of it.

On the documenting side, in particular, it saves a lot of time, and time is money, especially when you are dealing with people entering data and information into Excel. That can be replaced by Purview and that saves a lot of time. Purview also gives you information that you can act upon. Instead of finding out too late, you can act earlier, and save money in that sense.

What I like the most about Purview is the fact that you can really easily connect to data sources and retrieve the metadata in a batch manner. Instead of having to manually write down which tables and columns exist and then describe them, you can do that process in one go, by simply connecting to a source. That's a huge time-saver and a great benefit of Purview.

The solution takes into account critical data compliance regulations from around the world and that is one of the most important aspects of Purview. New laws are being enforced for data compliance and a lot of companies have a great interest in this feature of Purview. I think Microsoft is going to be focusing on that for the next couple of years to help organizations improve on data compliance.

In terms of reducing time-to-action, if you set up a clever rule that gets applied to your scan—it would just take some time to create that rule—in theory, whenever you are scanning your data you could identify something that is going on and act upon it. But I haven't seen that in practice yet.

The fact that Purview delivers data protection across multiple platforms, including AWS and GCP, is really important, but I feel the tool can mature further in that area. You can set up rules and scan your data and then you can figure out whether your data is secure and compliant, but feel that Microsoft could improve on this and add more features to the tool. I think they will do so over time. The solution has only been generally available since last year, so it's still quite early in terms of maturity. The multiple platforms feature is very important and there is potential there.

A bit of a downside is that although you can explore the data, that creates a great interest in data lineage or the data flow. How does it go from a source to a platform to a Power BI report, for example? It is possible, to some extent, to see that with Purview, but the lineage feature requires some manual work on the development side or more work from Microsoft to improve on it.

The data lineage is effective and useful when you are using all Microsoft products, but as soon as there's any complexity or you have a different tool in between, like Databricks for data transformations in your platform, for example, the lineage isn't going to be added in Purview because there is no connection to it. On the lineage side, a lot more can be done, but there is a lot of potential.

An additional feature I would like to see is in the following scenario. Suppose you have your sources scanned and you have all the tables listed in Purview. Right now, to update and label them, or to group them, would take a lot of time because you have to manually click on the assets and the tables that you have. But given that a database can have hundreds of tables, it would be helpful if you could update the assets in batch and, possibly, multi-select them. That would be a nice addition.

I have been involved with Microsoft Purview from the private preview stage, which was about two or three years. At that stage, it was only being shared with certain companies and nothing could be shared externally. In that phase, I got to share what I learned from the tool with Microsoft.

I haven't used it all the time since then, but more recently, I got to work with it for a few months so I got to see the latest update and changes that were made.

It is quite stable in terms of the scans running and not failing. It's not going to be slow or not function when you do an action inside of Purview. The stability is great.

It's really scalable, just like most things in Azure. You can add to it but it gets more expensive. You can add as many sources as you want, and the scanning of sources goes quite quickly, even for really big databases. The reason is that you're not copying any actual data, you're only getting the metadata, meaning a description of the tables and the schema, et cetera.

I haven't had to use Microsoft's technical support for Purview.

From my experience with other Microsoft Azure tools, the support is not bad, but it might take some time. Once you get someone working on it, an issue always gets resolved, but it can take a bit of time to get the right person involved to help you out.

For documenting data I have used Excel. I've seen huge Excel files with lots of data descriptions, and they took a lot of time to create. 

Also, on the data quality side of things, I have used an Azure data platform: an SQL database and a Power BI report. For example, if you're scanning data and you apply a rule to check if a column is empty so that you can classify it as "empty column," that would be a data quality rule. Instead of using Purview, I have used Azure.

It's very straightforward. There are not that many fields to fill in initially. Connecting sources, the first step, didn't take a long time. You really quickly get to see things, especially when it comes to Azure sources. It's all integrated so you can connect really easily. You just need to have authentication rights assigned. So connecting is quite fast.

The deployment is all-cloud. It's all Azure, which makes it really easy to deploy the tool really quickly. And if you have other data in the cloud, you can really easily connect to it.

The second part that takes a bit longer is defining the data, just like you would normally describe your tables and your columns and all your data definitions in Excel. In Purview, that also takes a bit of time. You have to find the way to describe it most easily. You can use the rules while scanning your data and automatically label or classify the data. But creating those rules takes a bit of time: How are you going to scan the data and what rules do you apply?

Getting the resources going just takes a day or two. But to connect to them and make things functionally available takes more time.

It's a one-man job. Even for connecting to resources, all you need is an admin who can grant you all the rights that you need for those sources and you can really easily scan them. The part where you need more people is on the business side because you need to describe, understand, and classify your data. That takes a lot more people because one person might know something about the customer database and a different person might know something about the finance database.

There is an investment of time involved, but once you set up those rules and you have the sources to scan, it automatically checks your data. It takes time to set it all up, but over a longer period of time, you will actually save time and see a return on investment. How fast that happens depends on your organization and how many data sources you have, as well as on how many people are using Purview and how efficiently.

You pay a minimum amount every month for the data map. You scan your sources and the metadata gets saved and then you pay for what is stored, which makes sense. However because there is a minimum amount, in the beginning, you might pay for more than you are using. That's something that some of my clients didn't like. That's why I say it's quite pricey; you're always paying a certain amount.

It would be nice if it went to entirely pay-per-use. For example, on Azure, when you have storage accounts, you pay for exactly how much you store. That would be nice to see in Purview as well. And while it's pay-per-use, you pay for features as well. For example, you pay for the cataloging part, including describing your data and adding labels and classifications. I would like to see a standard price and exact pay-per-use. 

I understand, in practice, that might not happen, but the pricing may be a bit overwhelming for some clients. They will say, "Hey, I'm already paying this much and now something else comes with another cost? Why is that?" It raises questions.

I'm working at a company that is a Microsoft partner, so it's all Microsoft-first.

We did do a quick analysis for a few other companies and there is some competition out there, but the other solutions are quite expensive. They are enterprise tools that are a bit more mature but the license costs $100,000 for some of them. Purview is pay-per-use and a lot of companies are interested in that. It's still quite expensive compared to most Azure components, but compared to the alternatives it costs less. That may be because it's not that advanced yet.

My advice is to involve people from the business side who can describe data and describe business terms. That's what is most important. Otherwise, it's just going to stay a technical implementation and it won't be used, which would be a huge waste. From the start, involve the people with a mandate who can actually start using it in the future.

Regarding its data connector platform for ingestion from non-Microsoft data sources, there are so many sources in the world that they have a ways to go there, but I do feel, especially in the last year, that the solution has grown a lot in that area. All the big, and most-used data sources, like Amazon, SAP, and many other sources, have been added, which is a great step. But if you work with sources that are more unique, the kind that are not used by many other companies, those are not available and you would have to write code in Purview for them. You can use the API that is available and you could insert metadata and lineage information into Purview, but that is a manual process. You would have to develop that for specific sources.

Purview's natively integrated compliance across Azure, Dynamics 365, and Office 365 is also quite important, but I haven't worked on that myself.

In my experience, Purview hasn't come far enough yet to help us reduce the number of solutions that interact with each other. We use Purview right next to all the other tools, which is okay. It takes a lot of time for a company to adapt to using Purview. You can scan data quite easily and figure out how to apply rules and classify and document your data, but you still need people to adapt and make use of it. I haven't really seen that last part very much in practice yet. It takes a bit of change management to get people to make use of it properly. As a result, it hasn't replaced tools yet for me.

Purview doesn't enable you to show compliance in real-time, but you can schedule how often you scan your sources. When the sources are scanned and added to Purview, they become visible and you can see if you're compliant or not, but that's not real-time. You can schedule scans daily, for example, but then you have daily data sets rather than real-time data.

Overall, the potential for this solution is really large. Data management is extremely important and Microsoft is investing very heavily in Purview. Right now, it's not quite there yet.

Our client was looking to do data governance and we decided to implement Microsoft Purview for them. The client did not have very specific requirements, because they had no idea what to do with data governance and they wanted someone who could kick-start things. We implemented the basic functionalities for them.

Our client was impressed because they now understand how much sensitive data they hold. They now know they have to assign someone who can work as a data steward, someone who will manage and protect the sensitive data to make sure that no one else can access it.

It has also helped our client save time when compared with doing data governance manually. It could be up to 80 percent faster because, if we had to do it manually, it would take a lot of time to create a script to scan all of the data in the data repository. With Purview, we can configure the connectors and just hit the button and it will do the rest.

Overall, Purview is quite good for helping you stay on top of compliance.

One of the best features is the classification rules, especially the scan rule sets. They are really useful, especially when we need to understand the current data the company has to ensure that all the problematic data can be put under someone's responsibility.

Also, although it is not automatic, managing the business glossary terms is valuable. If we have to work with other people who are also data governors, it's important to understand how the current data catalog is going to work with the business. We can do it manually to flag the business terms that we would like to handle.

It is also important that Purview delivers data protection across multi-cloud and multi-platform environments. Microsoft has built-in tools that can scan risky data that could be sensitive. It also provides connectors to other data platforms or clouds. These abilities are important for anyone who wants to see whether their organization has sensitive data, and how much.

In my understanding, because most of the connectors only scan databases or data lakes on multiple clouds, it is certainly not going to provide direct protection on other platforms, like iOS or macOS.

Also, Purview has no data ingestion capability. Of course, it can scan, but it won't import any data into Purview, just metadata. That is still important but it doesn't do data ingestion.

Another area for improvement is in managing the business glossary terms. If they could provide the same type of method that we use to configure the scan rule sets, that would be helpful. Currently, there is no option like this, so we have to do it manually. Automatic detection would be great.

I would also like to see third-party plug-ins. For example, there are several data quality or data management options on the market. Because Purview is not a 100 percent data governance solution, it would help if we could pick some of the good capabilities of other products. If we could plug Purview into the AI option from Ataccama, it would be enhanced immeasurably.

We implemented Microsoft Purview for a customer's company about two or three months ago.

It's stable. There were no weird glitches.

I think it's scalable, although Microsoft hasn't mentioned this explicitly. But it's a serverless solution, so it would scale. It just depends on how much data we need to scan.

We haven't had a chance to talk with Microsoft support because we haven't encountered any problematic situations.

Our client did not have a previous solution. They had no idea which one to go with. They just wished to have data governance and that's why we came up with Purview for them.

The initial deployment might seem complicated at first, but Microsoft has a guide with basic documentation on how to start and it's quite clear. Newcomers would need to understand the documentation first before they could implement this.

For example, for the resources in Azure, it might require the subscription owner to turn on some features. And in terms of the connectors, they would require an additional resource to store the data connection credentials called Key Vault. We had to implement all the resources to work along with Microsoft Purview.

It took about a week to get things up and running, but that was for the pilot solution. We did not have any very complex data to scan. We had to gather the information from the client about how much of the data they wished to scan, and when we got all the information, we started with the resources. 

We had three people involved in deploying it. One was responsible for most of the Azure connections and permissions. Another was the data governance operator who decided what to scan. The third was a data curator who made sure that all data was in the correct classifications.

It took about two weeks, after we implemented Purview, to realize the benefits of the most important features. The way that we implemented it, it was natively Microsoft-based, so there were not many other solutions to consolidate.

Compliance is not shown in real time because it might take some time to scan, but it depends on the amount of data involved. It's going to take some time to compile everything and show compliance.

Purview itself is on the cloud, but there is an on-premises database server that we need to connect with. Currently, there is no maintenance involved. It is done automatically.

The pricing is moderate. It's not too expensive, but it's not the most competitive.

In terms of additional costs, there is an option for advanced data lineage for lineage visibility with Power BI, but because our client did not have Power BI we didn't use this.

Although I haven't had a chance to work with Dynamics 365, I can see that Purview could be connected to that too, and I think it is important. And as far as I know, the classification rules built-in by Microsoft only apply to EU GDPR, as well as American and Canadian sensitive data protection. For all other regions, there are no options just yet.

If an organization wishes to do data governance that is not too advanced or sophisticated, Microsoft Purview could be the perfect fit for them, but they should, of course, do a PoC first.

We use the product to prevent the loss of personal information across Microsoft 365. 

You can set up automated dates to alert on internal data. 

I don't see any issues with the product's scalability. 

The tool's support is good and very responsive. The first and second lines of support need to improve. 

Microsoft Purview Data Loss Prevention is not cheap. 

We are heavy on the use of iOS. 

It is nice that the product delivers data protection across multiple cloud and platform environments. Azure is our primary cloud. 

We are happy with Microsoft Purview Data Loss Prevention's security and visibility. 

I rate it a five out of ten. 

I use the solution as a data catalog, to scan databases and report data insights. 

I use the tool in projects as a medium to provide information as reports to the stakeholders. 

I am impressed with the product's search and data catalog features. 

The product needs improvement to edit the number of assets. It needs to be more inuitive as well. 

I have been using the product for one and a half years. 

I haven't encountered any serious stability issues. 

The product is scalable. 

We split the data into dedicated customer-specific internal tools. My company made the business decision of choosing the solution which helped to manage data catalog, reports and connect databases in one place. 

The product's deployment was complex because it involved the connecting of different elements within the framework. I have been partly involved in the tool's deployment. I worked with the business requirements and user acceptance testing phase. I worked as a business analyst. There were the engineering team, DevOps team, and data engineers working on the project. We have a team who maintains the consistency of the data logs and data scans. 

I would rate the product a seven out of ten. 

I am a Windows user and connect the tool to the Azure platform to work on it. I have never used it on iOS and Android. I am sure that the multi-platform ability is a good feature of the product. I also find it important for the tool to be connected to data protection platforms. I think that it's a benefit to have the tool get data information from other cloud providers and platforms. It is also important that the solution was built taking into account critical regulations from all around the world. 

In my opinion, the tool has reduced the number of tools that I need to interact with. There was a project requirement from a customer where we were supposed to use a complete platform with the Azure framework. The solution has the potential to be used as a governance tool which helps to know where the data is placed, how it flows through the system, etc. I may use the AI and automation in Purview sometime later. 

I believe that the product speeds up compliance and Microsoft has documentation that can help with the same. The solution has helped me save time. For the tool's reporting part, we didn't need to rely on other tools and sort through manual files storing the information.