Microsoft Purview Data Governance Reviews

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

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

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

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

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

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

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

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

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

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

We started using Purview in the last six months.

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

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

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

I rate Microsoft Purview eight out of 10. 

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

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

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

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

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

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

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

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

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

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

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

I have used Purview for a year and a half. 

I rate Purview a six out of ten for stability. 

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

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

Neutral

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

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

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

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

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

I'm a cloud consultant and prefer Azure Purview as a governance tool. A few of my clients are in the banking sector, including global and Indian banks. They need a centralized solution for compliance and governance. 

I haven't used Purview much for SaaS or device management, but I have explored the SaaS services and PaaS in terms of other tools that can be integrated with Azure Purview. Our clients often have an ETL solution that's in Azure directly. Most of our clients use Synapse Analytics or Databricks. One of our energy clients in Australia has the same use case for data platform implementation. They have some unstructured data on-premises, and it goes back to the Azure storage account as raw data. They do some transformation with the help of an ETL tool. For agentless forecasting, they do model training with the help of Databricks or Azure machine learning. They'll use Power BI for visualization, but Purview is the centralized governance tool.

Purview improves compliance and governance with data source and auto-scanning features. All those data assets would be in a centralized repo that pulls from different sources and databases that hold the bank data or the customer's data. The solution enhances compliance in terms of security factors and issues like duplication. It scans for new data coming in and older data that already exists. Purview collects the metadata to get a clearer visualization of all the compliance aspects. 

Another benefit is accelerated migration. Purview facilitates smooth migrations by giving clients insights into their data, which data is useful, and what kind of data is non-compliant, so you can classify data based on compliance, priority, and utility. It helps clients decide which data is essential and should be migrated. Identifying non-compliant data can help clients improve security and privacy.

Data analysis and classification isn't a two-day or two-week job. It's a long-term process. It might take two or three months to gather feedback on what kind of data is the most beneficial, like structural data, static data, etc. The data lineage doesn't come in one or two days. It takes some time to get a complete picture of your source and destination and the data cycle from start to finish. You can say that the data was in this phase six months ago, and now it is in this phase. Six months is enough to get a clear picture of the data flow and the kinds of data that are most beneficial.  Purview is helpful for long-term data management and classification.

Purview improves visibility. If I go back to a year ago, when I was learning Purview, my perspective was different. There were fewer features, and Purview has grown at a rapid pace. I was originally a network engineer, but I am now a cloud consultant, so it was challenging to work with the Azure version initially. I started seeing the benefits of its data classification features once I started consulting, seeing everything that comes into a client's bucket, and receiving feedback. Now, I can see the solution's strengths in governance and compliance.

The auto-scanning functionality and automation features in Azure have a positive impact when connecting data sources. When there are multiple data sources, we can make connections and start discovery. Manual discovery will take so long, and we don't know when the new data is coming in, so automation is useful. When new data comes into the databases, Purview triggers that auto-discovery part so the data stays updated. It's more efficient and more accurate.

For example, we have let's say we have data coming in this month. We have a discovery scan, and some new data comes into the databases after a day or two. If we don't run the auto-scanning feature, the data will get outdated. It would affect if we need to present something or calculate something. We can discover data quickly and get accurate data. It isn't completely in real-time. It still takes time to refresh things, but we haven't 

Automated discovery reduces the amount of time needed to take action on insider threats. If discovery is already done, it's easier to classify the data and import it into a data visualization tool like Power BI. We need to complete the discovery before moving on to the data lineage component or the Data Factory pipeline. It reduces the time by about 12 to 15 percent.

My favorite Purview feature is auto-scanning. Once we set up Purview, we can automatically scan multiple data sources when new data comes into specific databases, like SQL and Oracle. We don't need to rediscover the new data or do anything manually because it automatically happens.

Purview also offers some additional integration capabilities if you use the Azure edition. We can seamlessly integrate tools like Azure Data Factory and Synapse Analytics to provide analytics and data transformation services in a customer's ETL pipeline. Organizations want to structure that data, so they use a basic ETL tool, which is commonly Azure Data Factory. Purview provides us with all the connectors needed to integrate these data tools. Another feature I like is data lineage. Purview tracks the data from its source to the destination. 

I haven't seen many challenges with integrating or supporting native Microsoft solutions like Office 365. We haven't come across anything in Microsoft 365 that's unsupported out of compliance with HIPAA regulations in the health sector or banking and finance regulations. It conforms to PCI DSS compliance methodology or GDPR.

We have multiple clients in the energy and banking sectors. Purview is vital in data platform implementation projects involving ETL transformations and model training. It's our default tool for governance when we're pitching our organization during presales. However, our smaller customers often don't need that much governance, or they're good with Azure Monitor. They may also prefer some other governance tool or might have an on-premise tool that they are already using. They don't want to change it despite the integration and features. Our big customers may have existing governance tools, but they want to use Purview because it offers additional features. It provides them security, compliance, and the flexibility to integrate with third-party and Azure native tools. 

Two features are unsupported—custom insights and the DLP component—that would be beneficial to me as a consultant and for the customer in terms of security and monitoring. Regarding security, DLP would provide a more granular level of data masking. Custom insights would offer more detailed monitoring and alerts that can notify customers of failures or anything requiring urgent action. 

DLP is not a part of Purview. Our larger customers require some advanced features, such as dynamic data masking, encryption, and decryption. For example, some of our projects in Dubai involve machine learning use cases and encrypted critical data on-premise. It varies. Data encryption and masking are not priorities for some customers.  

Microsoft has some built-in data masking tools. Some customers believe that masked data is safe, and they don't want to move it. We tell the clients that Purview doesn't move the actual data, only the metadata. The customer is convinced that DLP is not part of Purview, but that is not a concern because it's all about metadata. The original data is not transferred from on-premise to Azure. Purview is not storing the actual data. It takes the data to perform discovery and provide better data classifications. If DLP is added, then Purview will be stronger.

When I talk to clients about these DLP features, they say it still lags behind in data integration and support. It does not affect the sales side or prevent us as consultants from convincing them to switch because of these two unsupported features. However, Purview does need some improvements in data security and third-party integrations.

I have worked with Purview for a year. 

I rate Purview six out of 10 for stability. It is stable, but they're constantly adding new features, so it needs more stability in the future. 

Purview is a scalable solution because Microsoft manages everything on the back end. We don't need to handle any databases or servers. We can talk about the general scalability of Azure services, not Purview specifically. The SLA gives an uptime of 99.99 percent. I have not had any scalability issues with Azure services, and this goes for Purview as well.

I rate Microsoft support seven out of 10. They respond quickly and follow up fast after the issue has been closed to see if the problem is resolved. 

Neutral

I have not used GCP, but the AWS centralized governance tool lags in terms of authentication and authorization. AWS also has features like data lineage it can provide. However, Purview stands out for security protections and role-based access control. Purview offers better granularity compared to the AWS or GCP governance tools. The access control list enables granular levels of access to its users. 

Deploying Purview isn't too complex. The initial installation takes about eight hours. Setting up a data governance solution involves configuring the networking components. The networking part can be done in parallel with deploying other services. However, you must completely implement the data platform before connecting the data sources and performing data discovery. Later, you can begin the data analysis and classification on Purview. 

The data deployment and networking configuration is similar to deploying other Azure services. I imagine on-prem Purview requires more time to set up. If we are giving a client an estimate of the time it would take to complete the project, the deployment and networking part would not additional time. However, the data discovery, classification, lineage, and data source connectivity, require two more weeks. The total deployment takes five to eight weeks plus an additional two weeks for the discovery phase.

The networking engineer who deployed Databricks, Azure Data Factory, Synapse Analytics, etc. can easily deploy Purview because it's the same. However, we require a dedicated Purview engineer for the discovery phase. We haven't had to do much maintenance so far. 

Microsoft Purview is priced in the middle. It isn't the cheapest, but it isn't the most expensive. It's affordable compared to other public cloud services. Purview costs about 20 percent less than AWS, but it is still expensive compared to other Azure services and governance tools. 

I rate Microsoft Purview seven out of 10. I recommend Purview over other governance features because it has multiple features that make it stand out from the rest. Once it is updated with features like DLP and custom insights, Purview will be a market leader. These additional features will help the solution earn more enterprise-scale customers. 

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

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

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

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

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

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

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

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

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

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

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

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

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

It's very stable. 

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

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

Positive

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

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

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

I'm a customer. 

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

I'd rate the solution nine out of ten. 

I use their information protection labels. 

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

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

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

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

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

The labeling is excellent.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Negative

We did not use anything previously. 

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

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

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

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

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

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

We're a Microsoft customer.

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

I'd rate the solution seven out of ten. 

Microsoft recently changed the name of this solution. It was previously called Microsoft Compliance Center. Purview has multiple functions, but I primarily use it for records management. I also use the Audit Center for getting audit details about various aspects of the Microsoft 365 platform.

Purview protects against litigation by meeting our compliance requirements and helping us manage the reports. You can realize the benefits once it's set up correctly. Every day, you'll get new audits and inputs from the tool and access the data quite easily. 

The organization didn't have any solution in the first place, so that's a huge challenge. From the perspective of Indian compliance use cases, we see a lot of benefits from Purview's storage. 

This custom solution gives you more power compared to what it used to. Previously, all the other data and SaaS products were running in silos. Having this customized environment and a single pane improves the smoothness of the experience. The visibility has improved greatly in terms of the scalability and elasticity of the content. Purview enables us to demonstrate compliance in real time.

Purview has helped us deal quickly with insider threats because we can implement extended file solutions and see what's happening with raw shared content from various users. We can get a sense of what's being deleted and take action. At least 80 percent of our cases are getting solved.

The audit log has been a lifesaver for a lot of reasons. Historically, when using SaaS products, there were always questions about how the audit was going and whether we were sufficient out of the box. Purview has many capabilities available through centralized reporting that provide a view of a specific segment. 

The audit log capability enables us to observe things like changes in file sizes. At the same time, it simplifies management and control over the entire infrastructure, but it's specifically effective for Microsoft platforms. 

Purview's coverage of multi-cloud environments is essential. In today's world, we cannot stick to a single cloud provider because each one has a different set of benefits and advantages over the other. Many organizations typically try to interconnectivity and a cross-cloud platform, so it makes sense to have a single centralized compliance center and repository where you can track all activity at once. 

You can integrate iOS, Mac, and Android devices and data in other SaaS apps, which is important because we have a plethora of users using various devices across various operating systems. It makes a huge difference to have a centralized data solution for us. Purview natively integrates compliance across Azure Dynamics 365 and Office 365, which is quite important because Office 365 represents the new digital transformation. Purview covers the complete ecosystem, encompassing a lot of use cases and custom applications.

The solution takes into account critical regulations from around the world, which is vital for global organizations operating in countries that each have separate sets of rules and regulations, like GDPR. 

Running eDiscovery once a day takes quite a long time because it has to fetch your data. I also want the eDiscovery results to be improved. At the same time, I would like to get a centralized page where I could see records management applied to my Office 365 tenant visualized instead of waiting for a custom script to run through the complete tenant. 

I want to see how many records there are,  how many files will be affected when we apply a change, and when the next retention cycle is going to run again. It would be helpful to have that integrated into the process.

I have used Purview for around four years now.

Purview is 99 percent stable. 

Purview is highly scalable.

I rate Microsoft support seven out of 10. The response times could be quicker. 

Neutral

We had previously used custom solutions, but Purview is quite effective for the problems we are trying to solve. 

Setting up Purview is straightforward. The deployment steps depend on the features you are using and what you want to target. I don't recall any major challenges setting this up. It takes a couple of engineers.

Purview is reasonably priced. We're working with so much data, and there are many jobs on the back end that might increase the cost, but it isn't a problem right now. 

I rate Microsoft Purview seven out of 10. It's important to consider how your end users will integrate and establish a process for your data. 

We use it for the creation of enterprise PSA, as well as for our enterprise data catalog and data governance.

This is a type of pilot project or proof of concept. Our organization wants to see how it works, how complex the maintenance side will be, and how effective and efficient it will be.

It enables us to show compliance in real-time. However, because it is a pilot project for us, we are not showing the information to other parties yet.

It has definitely helped us reduce our time to action on insider threats. Finding proper data is always challenging in a big organization and this is a really positive aspect of Purview.

The first thing that we were particularly interested in is data lineage. It makes it pretty easy to connect and scan data sources, and do any kind of additional steps like Synapse or SSIS processing.

Overall, I would laud its ease of use, intuitive interface, and easy navigation. It's a very user-friendly product that is easy to work with.

In addition, we considered the issue of multi-cloud and multi-platform environments when we were trying to identify the best tools that would serve all the requirements of our organization. Currently, we are not directly pulling data from AWS. We are working with Azure. But we have the potential in the future to consider such options. This feature is very valuable because we are planning to establish automated data-pulling from AWS.

And the solution's data connector platform for the ingestion of data from non-Microsoft data sources is very easy to use. I investigated what data sources it can work with. It's certainly easy to work with all Microsoft data sources like SQL Server, Synapse, and data lakes, but it also has great functionality working with Oracle. And of particular interest to us is the ability to pull data from Excel, CVS files, and other types of flat files.

Another particularly nice feature is its integration with other services. This is one of the biggest advantages of the solution. For example, if you need to store a key for database access, it's easy to integrate with key vault services.

And a feature that is very important to us is the fact that Purview was built taking into account critical regulations from around the world. Before we started working with Purview, we put great effort into evaluating its capabilities and functionality. We created a comparative matrix with other tools and this was one of the factors we included. We considered it a big positive for Purview.

The scanning of data sources can be scheduled to execute automatically. That is the only automation we are using within the solution.

One area for improvement is the detection of data types. This is really important. It has some of that functionality, but I consider it very limited. Maybe they can add some custom programming, or machine learning could be particularly useful for the detection of the nature of the data.

If it could tell us, for example, when a given type of data is a social security number, that would be helpful. Currently, we need to open it and determine what the format is. We would like to know if a given type of data is PII data.

I have been using Microsoft Purview for almost two years.

I found some defects, through my interaction with the solution, in the reporting system. Purview has its own reporting and I found a function that apparently is not working. There are some bugs in that section, but other than that, everything looks okay. It works well.

We haven't experimented with scaling it, but my perception is that it's very scalable.

We haven't had to contact Microsoft's tech support.

We didn't have a previous solution.

The setup was pretty straightforward. It took us about one week, but a lot of the dependencies are not directly related to Purview. We had to obtain a password and user and that takes some time.

Microsoft takes care of patching, so I haven't seen any need for maintenance by us. It's on the cloud and they take care of it. We don't need to worry about that part at all and that is one of the big advantages of a cloud system.

We did everything in-house. I had architecture and administrative support, but I did the actual work with Azure alone.

I'm handling the proof of concept work. No other organizations have access to it. We don't want people to start using something that is not really complete yet.

Because this is a proof of concept, we haven't seen direct cost savings, but we see it having a positive impact on development work, particularly for BI folks who are interested in self-service and building reports for themselves. This is a very good exploration tool.

Microsoft Purview is the best option I have encountered when it comes to price. Maybe some of my information is outdated, but Microsoft offered it so that you could use it almost without paying. This was a really nice aspect. 

I don't know how Microsoft's pricing stands today, but for us, it was very cheap and effective. We are still paying some money but it's not significant. 

They should look to keep the pricing moderate in the future.

We compared Purview with other solutions, but not on a practical level. We only compared it with the information we were able to find on the internet, including the documentation and the functionality, but we did not install or do anything with the other solutions.

For a large enterprise, it's very important to have tools like this. It's especially useful for IT people who are dealing with data science or who need to find or investigate data or find out what data an organization has. It's also useful for those who maintain a central data warehouse and for people who want self-servicing business intelligence.

At this point, Purview has not reduced the number of solutions we interact with. In the future, we will consider that option. At this point, it operates as a standalone for us, because it is a pilot project in our organization.

Microsoft Purview is not yet a leader in data cataloging or data governance, but I'm pretty sure it will be, given how the tools are evolving and the functionality it already has. At the same time, I'm certainly looking for some of its functionality to improve, including easier integration with Microsoft Power BI.

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

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

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

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

I have been working with it for approximately two years.

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

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

Neutral

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

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

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

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