What is your primary use case for Microsoft Azure Purview?

We are using Microsoft Purview Information Protection. We want to do loss protection for our unstructured documents.

As a Microsoft partner, we specialize in selling Microsoft products to our clients. Microsoft Purview serves as a typical data cataloging tool within our data governance projects.

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

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.

Our data landscape includes cloud-based resources, Software-as-a-Service applications, and on-premises deployments. To ensure consistent governance across this entire environment, we leverage Microsoft Purview for unified data management.

Our IT team, data engineering team, and data science team all rely on Microsoft Purview for a unified data repository. We maintain a table for storing sensitive data with segregated access. To readily understand the data types within, anyone can simply leverage Microsoft Purview's classification system. By selecting a specific classification, users gain access to relevant table details.

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.

We use the solution to defend endpoint workloads and prevent data loss. We also use it for governance.

We have got all kinds of things to include in it. Specifically, we are looking at the data classification piece and the data protection piece that goes into it. Those are the two immediate cases. We have got ECIF partners helping us with it, and Microsoft is heavily involved. These are the two initial ones, but as we continue to expand, we are going to bring more functionality under the purview of Purview. Those are the broader use cases right now, but the idea behind it is to simplify the landscape.

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.

My organization had a large amount of sensitive data stored primarily in SharePoint Online. We also operate in a highly regulated industry. Therefore, we wanted to take advantage of some of the features offered by Microsoft Purview. Initially, we focused on sensitivity and retention labels, but we later expanded to include data loss prevention and benchmarking our data against the built-in regulations offered by Purview.

I am a system integrator for Microsoft Purview. I have assessed some customers who already have Microsoft Purview because of their E5 license. However, they are not aware of Purview's capabilities. Purview is a relatively new product that provides an end-to-end data security lifecycle solution. It allows us to review our data with a data governance solution, classify it, protect it, and prevent data breaches. I have worked on almost all aspects of Purview. We have assessed some customers and provided them with use cases such as using Purview to protect confidential data recovery. This allows them to manage their own workflow for vendors on a contractual basis. We have multiple use cases for Purview.

I see many customers these days looking into Microsoft Purview syntax and mainly using the solution for data lineage and data governance. The customer wants to be able to understand data a bit more within the organization and be able to classify and protect sensitive data and understand what it is. My company works with the healthcare and financial sectors. Microsoft Purview can give good information on the cause of the breach, and that comes into the forefront of many organizations nowadays to know how to protect data not only from external sources but also internally as well.

The use cases for the solution include data governance, metadata management, creating business grocery, doing data lineage out of the data within the entire data stack and technology stack, and, at the same time, creating data stewardship using the policy procedures. We're implementing the policy procedures, and using workflows for automating the task.

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

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.

We use Microsoft Purview to protect and govern our information.

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

We use it for the text of emails. We use it to keep track of groups as well. We also use it to go through the mailbox of a former employee to retrieve the mailbox for a new employee. We use it for e-discovery and content search in emails across our organization. We use it internally for just a few use cases. I know there are a lot of connections between it and other Microsoft applications and multiple clouds, but we don't have those use cases currently. We carry out implementations for customers on these particular solutions. For example, if we're selling a Microsoft 365 solution to them, we use it to secure their data, especially their emails through backup, and SharePoint.

It is our data governance solution. It has been very helpful for the data discovery and data governance part.

We use the platform to comply with regulations, and our specific use cases are information protection, information governance, data loss prevention, and insider risk mitigation.

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.

We need to catalog and assign terminology to all of our data to find all the personal information that we have within our copy systems. Over the last three years or so, we have been using Kafka and nesting queues a lot. We wanted to bring in an orchestration engine to integrate seamlessly with our nesting system. We had a lot of legacy applications that are not that old, and we did not want to rewrite software components that we own to get the benefits of orchestration. That's where there is a need. One of the factors that will decide if the use of Camunda will spread out to more use cases in our company is the ease of integration.

We are using it for governance on the cloud data migration. When people want to see legacy application Hadoop to Azure, we use the solution to gain some governance aspects and integrate it with Synapse on the final layer, which is the transform layer of the data lake. Purview was included at a single location in eastern Canada. There are close to 1,000 users.

We're building a new system from scratch for our clients and wanted to include the data governance. Their solution is hosted in Azure and it seemed logical to go with something that fits with that. I'm a solution specialist and we are partners with Microsoft.