Microsoft Purview Data Governance Reviews

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.

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.

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

We are a partner and work with different organizations. We go through a number of activity phases, such as initial discovery, understanding their data to see what is and is not sensitive, and then using Microsoft Purview. 

We use Microsoft Purview to provide sensitive information in building out a roadmap in terms of classification, protection, and lifecycle management. We then determine what kind of use case is most common for other work we would look for and fill in the gaps with the customer. Microsoft Purview's vast features and capabilities really depend on what we learn in those workshops and where that organization is looking to go over a period of time. So if one of the key areas is the mitigation or prevention of data breaches, we can help with that. 

We can also help protect content, especially when it is sensitive and involves individuals. We can also help businesses change their processes to help ensure users know what their preferences are and how to use the user tools.

Microsoft Purview's ability to deliver data protection across multi-cloud and multi-platform environments, including AWS and GCP, is very important. It helps organizations realize the investments they have already made and how they can further expand those investments to another remote type of Microsoft workflow. Microsoft Connect has been used to centralize these workflows, and the ability to import existing records management processes and policies into the file plan in Microsoft Purview allows organizations to bring compliance into a central location. This helps to manage costs and improve efficiency, as users can go to one area to leverage basic facilities without having to use separate tools.

It is important for our clients that Microsoft Purview can connect to iOS and Android devices. With many people now working from home and using their own devices, there is a need to manage these devices. Microsoft Purview's conditional access and endpoint management capabilities help organizations to protect their data, regardless of the device being used.

Purview's natively integrated compliance across Azure Dynamics 365 and Office 365 is important. However, it is also important to ensure data privacy with its data as a whole from a compliance perspective. This means ensuring that we can meet the requirements of 2701 controls and that people know the processes, technology, and relevant skills. CRM controls information about potential customers and opportunities, so it is important to ensure that we are compliant when handling this data. We also need to make sure that updates to Purview are made as needed and that our team is able to stay on Office 365. Having a strong compliance program is essential for any organization that handles sensitive data. By taking the necessary steps to ensure compliance, we can protect our data and our customers.

It is critical that Purview is built around global regulations. This is because we have different types of customers, some of whom operate slowly. There is a rack with some regulations, and we have the US. We also have a rack with different regulations that are up-to-date, but they are only safe in some areas. This means that we need to be able to control, face, or bank on system regulations. This is very important to me and the customer because they can be very tricky.

Purview's DLP can be used to remediate policy violations. A number of kinds of DLP rules can be leveraged, such as sensitivity labels, data classification, and sensitive information protection plans. This means that it is not enough to simply provide people with the technology, they also need to be trained on how to use it effectively. Through the use of an ERP system, a number of policies can be set up. This insight can then be used to make meaningful decisions about how to rate the data on the system. This will help to understand how the data is costing the organization. If the organization does not have the necessary internal controls in place, new protection and encryption measures may need to be implemented. This is primarily becoming step one in the process of working policies, understanding how the data is being used, making decisions about how to protect it, and then building a protection layer on top of that.

Data loss prevention education for users is important because it can help them to understand how to best protect sensitive data. This can be done by providing users with training on how to use DLP tools and policies, as well as by educating them about the risks of data loss. DLP tools can help to prevent data loss by monitoring user activity and blocking unauthorized access to sensitive data. DLP policies can help to define what constitutes sensitive data and how it should be protected. By educating users about DLP and the risks of data loss, organizations can help to create a culture of data security. This can help to prevent data breaches and protect the organization's data assets.

Purview helped reduce the number of solutions we need to interact with each other. I used the solution that crosses between Endpoint Data Loss Prevention, Microsoft Defender for Data, and Conditional Access to block specific types of information at different workloads. This made it easier to manage sensitive information. For example, if I have sensitive information today, I can easily block people from uploading it to Teams, SharePoint, or OneDrive.

The reduction in the number of solutions we need to interact with each other has had a significant impact on our pricing. In the past, we had to use a variety of different solutions to manage our portals, which was time-consuming and expensive. Now that everything is coming into Microsoft Purview, we are able to simplify our technical and environmental environment. This allowed us to reduce our costs and improve our efficiency. In addition, Microsoft Purview provides us with a central location to manage our data governance. This made it easier for us to comply with regulations and protect our data. Overall, Microsoft Purview has been a major asset to our organization.

Microsoft Purview expanded our visibility into our state by allowing us to see what is labeled, relabeled, and what is not classified. There are a number of different areas where Purview improved capability and overall cost. These are all different aspects of Purview, which is helpful for organizations. Purview has a point-in-time view, and it also has the ability to explore more granular data from the logs.

Purview helps to reduce the time it takes to take action on insider threats by around 50 percent. It requires planning and configuration, as well as two weeks of setup. The technical configuration is used to identify users and the types of activities they are performing. For example, users who sign into hundreds of documents within a few minutes of each other or delete large numbers of documents can be quickly identified and flagged. This allows security teams to send high-priority emails to the appropriate people in a timely manner.

Purview helps save our clients between 30 to 40 percent of time and money. 

Microsoft Purview's most valuable feature is its ability to identify content across a number of prescribed regulatory frameworks, including Microsoft, GDPR, PII, and UCC Financial. It can also help organizations identify content that is important to them but not specifically regulated. This is done by creating trainable classifiers and sensitive information types. The protection controls components are based on the perspective of the device. Microsoft Purview has been growing in popularity over the past few years, and it offers a number of tools that can help organizations manage their data.

Purview's data loss prevention for macOS endpoints has some limitations, and the end-user experience of recovering from a failure is lacking.

I would like to be able to search for labels using Purview to see what items are affected and the time periods in which they will be active. This would allow us to export the results for specific business areas, which would make our lives a lot easier. We could also use this information to identify sensitive information types and reduce false positives.

The utility system format, the policy tips and user descriptions of sensitivity labels, and the overall policy tips that are shown in the loss prevention policy have room for improvement.

I have been using Microsoft Purview for three years.

The stability of Purview has been good. It takes a bit of time for someone to configure it, but once it is configured, it is responsive. However, there are sometimes delays due to the speed of users' devices and their home network connections. This can be especially true for mobile devices and when users are using multiple apps at the same time. Microsoft also sometimes experiences delays in processing requests, which can lead to further delays in Purview. Overall, Purview is a stable platform with good uptime and resilience.

In terms of scaling Microsoft Purview, there are two main challenges: network load and data ingestion. Network load can be a problem if there are too many requests coming into the system. This can be addressed by adding more servers to handle the load. Data ingestion can also be a challenge if the company is generating a lot of data. This can be addressed by using virtual machines to store and process the data. As the amount of data grows, the number of VMs can be increased to keep up.

Our clients vary in size from 100 all the way up to 6,000.

Each setup is different. We have thousands of workshops, configurations, and design agreements followed by a baseline to mitigate of about 30 percent which we build on top of. The deployments can take anywhere between a few hours to a few months. We need to understand each organization to ensure that they understand the type of people process that is in place. Then, depending on the technology, we need to make sure that they have access to 365. This is implemented as a baseline, and our target operating model is also needed to ensure that they have the necessary functions. This will allow me to deal with the environment. We need a team of people to manage the deployment.

We implement the solution for our clients. Microsoft Purview is managed in a single location.

Microsoft Purview does not require any maintenance.

Our client's have seen a 100 percent return on investment. 

The pricing depends on the client's requirements and the number of applications.

I give Microsoft Purview an eight out of ten.

It is difficult to assess how much AI and automation affect our speed and accuracy of risk detection. This is because the effectiveness of AI and automation depends on how we train the system. There are a lot of sensitive information types that are prescribed by Microsoft. There are also a number of types that fit within another structure of sharing information. So potentially, we have a number of false positives, which means that we are relying solely on the information provided by the system. This is not something that I would push on an organization. Once we start updating the system, we need to make sure that we understand and compare the number of activities to identify and fine-tune the system. We need to do this a number of times before we can be really sure that the system knows our data. We also need to consider the AI side of things, which obviously allows for some risk. The identification of risk seems to be a matter of realizing confidence in the system's predictions.

It is difficult to assess how Microsoft Purview's AI and automation affect the quality of insights that we have. We have run this process effectively a number of times across different organizations, but this has raised some doubts. This is a bit of a shame, especially with the out-of-the-box solution from Microsoft. We are then asked to hold a number of workshops to review the results. This is because the system can operate with different accuracy levels and false positives. It is important to consider how we portray these insights and what the next steps will be. As a result, there are mixed reviews.

Currently, Purview does not enable us to view our compliance in real-time without some additional work to enable us to show compliance. This is because the visual displays rely on the time it takes to update the Microsoft SQL database, which can be delayed. We have seen cases where the displays do not reflect the actual data, and we have had to manually update the database to correct the issue. However, we can clearly see what data is due for disposition, deletion, and retention based on our policies. While it is not always easy to see this information, we have made improvements to make it easier. Overall, it is not a straightforward process, but we are working to improve it.

I recommend Microsoft Purview, but organizations should always conduct a proof of concept to ensure that their requirements can all be met before implementing the solution.

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. 

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.

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.