Azure Purview
Author: Ronald Fung
Creation Date: 30 May 2023
Next Modified Date: 30 May 2024
A. Introduction
Microsoft Purview is a family of data governance, risk, and compliance solutions that can help your organization govern, protect, and manage your entire data estate. Microsoft Purview solutions provide integrated coverage and help address the recent increases in remote user connectivity, the fragmentation of data across organizations, and the blurring of traditional IT management roles.
Microsoft Purview combines the former Azure Purview and Microsoft 365 compliance solutions and services together into a single brand. Together, these solutions help your organization to:
Gain visibility into data assets across your organization
Enable access to your data, security, and risk solutions
Safeguard and manage sensitive data across clouds, apps, and endpoints
Manage end-to-end data risks and regulatory compliance
Empower your organization to govern, protect, and manage data in new, comprehensive ways
For more information about the Microsoft Purview release, see The future of compliance and data governance is here: Introducing Microsoft Purview security blog announcement.
B. How is it used at Seagen
As a biopharma research company using Microsoft Azure, Seagen could use Azure Purview to manage and govern their data assets across their organization. Azure Purview is a unified data governance service that helps organizations discover, understand, and manage their data assets. Here are some ways Seagen could use Azure Purview:
Data discovery: Azure Purview allows Seagen to discover data assets across their organization, whether they are located on-premises or in the cloud. This can help Seagen understand the scope of their data assets and identify potential data quality issues.
Data classification: Azure Purview allows Seagen to classify data assets based on sensitivity, compliance requirements, or other criteria. This can help Seagen apply appropriate controls to protect sensitive data and ensure compliance with regulations.
Data cataloging: Azure Purview allows Seagen to catalog data assets, including metadata and lineage information, in a centralized repository. This can help Seagen understand the relationships between data assets and identify potential data quality issues.
Data governance: Azure Purview allows Seagen to implement data governance policies and controls to ensure compliance with regulations and protect sensitive data. This can include policies for data retention, data access, and data sharing.
Integration with other Azure services: Azure Purview is integrated with other Azure services, such as Azure Data Factory and Azure Synapse Analytics, which can enhance the data management capabilities of Seagen.
Overall, Azure Purview provides a comprehensive solution for managing and governing data assets across Seagen’s organization. Its ability to discover, classify, catalog, and govern data assets, as well as integrate with other Azure services, makes it a valuable tool for organizations that require effective data governance to ensure compliance, protect sensitive data, and drive insights from their data.
C. Features
Azure Purview is a unified data governance service that provides a wide range of features to help organizations discover, understand, and manage their data assets. Some of the key features of Azure Purview include:
Data discovery: Azure Purview allows users to discover data assets across their organization, whether they are located on-premises or in the cloud. This can help users understand the scope of their data assets and identify potential data quality issues.
Data classification: Azure Purview allows users to classify data assets based on sensitivity, compliance requirements, or other criteria. This can help users apply appropriate controls to protect sensitive data and ensure compliance with regulations.
Data cataloging: Azure Purview allows users to catalog data assets, including metadata and lineage information, in a centralized repository. This can help users understand the relationships between data assets and identify potential data quality issues.
Data governance: Azure Purview allows users to implement data governance policies and controls to ensure compliance with regulations and protect sensitive data. This can include policies for data retention, data access, and data sharing.
Data lineage: Azure Purview allows users to track the movement of data across their organization, including where data came from and where it has been used. This can help users understand how data is being used and ensure compliance with regulations.
Integration with other Azure services: Azure Purview is integrated with other Azure services, such as Azure Data Factory and Azure Synapse Analytics, which can enhance the data management capabilities of users.
Data privacy: Azure Purview provides features for managing data privacy, including data masking and data encryption. This can help users protect sensitive data and comply with regulations.
Data scanning: Azure Purview provides features for scanning data assets to identify sensitive data, such as personally identifiable information (PII), and help users apply appropriate controls to protect this data.
Overall, Azure Purview provides a comprehensive solution for managing and governing data assets across an organization. Its ability to discover, classify, catalog, and govern data assets, as well as integrate with other Azure services, makes it a valuable tool for organizations that require effective data governance to ensure compliance, protect sensitive data, and drive insights from their data.
D. Where Implemented
E. How it is tested
Testing Azure Purview involves several steps that include:
Creating a test environment: The first step is to create a test environment that is separate from the production environment. This ensures that any issues or bugs discovered during testing do not affect the live system.
Configuring Azure Purview: The next step is to configure Azure Purview for the data assets that need to be governed. This involves setting up data sources, registering data assets, and configuring data classification and governance policies.
Testing data discovery: Once Azure Purview is configured, the next step is to test data discovery. This involves verifying that Azure Purview can discover data assets across the organization, whether they are located on-premises or in the cloud.
Testing data classification: After testing data discovery, the next step is to test data classification. This involves verifying that Azure Purview can classify data assets based on sensitivity, compliance requirements, or other criteria, and apply appropriate controls to protect sensitive data.
Testing data cataloging: Once data classification is tested, the next step is to test data cataloging. This involves verifying that Azure Purview can catalog data assets, including metadata and lineage information, in a centralized repository.
Testing data governance: After data cataloging is tested, the next step is to test data governance. This involves verifying that Azure Purview can implement data governance policies and controls to ensure compliance with regulations and protect sensitive data.
Integration testing: After Azure Purview has been tested, it must be integrated with other systems and applications to ensure that it works seamlessly with other components.
User acceptance testing: Finally, Azure Purview must undergo user acceptance testing to ensure that it meets the requirements of the end-users.
Overall, testing Azure Purview involves a comprehensive testing approach that covers all the functionalities of the solution and ensures that it meets the requirements of the end-users. Testing should include both functional and non-functional testing, such as performance testing, security testing, and scalability testing. It is also important to test the integration of Azure Purview with other systems and applications to ensure that it works seamlessly with other components. It is recommended to test Azure Purview in a test environment before deploying it in a production environment to minimize the risk of issues during production use.
F. 2023 Roadmap
????
G. 2024 Roadmap
????
H. Known Issues
Like all software products, Azure Purview may have some known issues. Here are some of the known issues of Azure Purview:
Limited support for certain data sources: Azure Purview may have limited support for certain data sources, such as databases that do not support JDBC or ODBC drivers. This can limit the ability of users to discover, classify, and govern data assets in these data sources.
Performance issues: Azure Purview may have performance issues when processing large volumes of data or when performing complex queries. This can impact the ability of users to discover, classify, and govern data assets in a timely manner.
Integration issues: Azure Purview may have integration issues when integrating with other systems and applications. This can impact the ability of users to use Azure Purview in their existing data management workflows.
Security issues: Azure Purview may have security issues, such as vulnerabilities in the data scanning or data classification features. This can expose organizations to security risks and data breaches.
Complexity: Azure Purview can be complex to configure and manage, especially for organizations with large and complex data environments. This can require significant technical expertise and resources.
Overall, while Azure Purview is a powerful solution for managing and governing data assets across an organization, users must be aware of these known issues and take steps to mitigate their impact. This may include addressing performance issues, ensuring compatibility and integration with other systems and applications, monitoring security vulnerabilities, and providing training and support to users to effectively use and manage Azure Purview. It is recommended to carefully plan and test the use of Azure Purview in a test environment before deploying it in a production environment to minimize the risk of issues during production use.
[x] Reviewed by Enterprise Architecture
[x] Reviewed by Application Development
[x] Reviewed by Data Architecture