Data Governance with Microsoft Purview

What is Microsoft Purview?

This module introduces the basic features of Microsoft Purview.

• The need for a metadata catalog
• Purview features
• Quick comparison with Azure Data Catalog
• The new Purview portal

Setting up a Purview account

In this module students learn how to setup and configure an Microsoft Purview account

• Creating an account via the portal
• Inspecting the Purview account in the portal
• Purview cost
• LAB: Provision a Microsoft Purview account

Microsoft Purview Portal and Collections

Microsoft Purview Portal is the web portal from which the Purview resources can be controlled and queried. Collections are the hierarchical grouping of sources, but they also provide the hierarchy of permissions that Purview users can have on the collected data.

• Exploring the Microsoft Purview Governance Portal
• Creating Collection hierarchies
• Collection permissions
• LAB: Setup a collection hierarchy

Registering Sources

A very important step in building a Purview solution is register all the sources that can be scanned. This module walks you through the different types of sources that can be registered as well as the registration process itself.

• Supported sources
• Registering sources
• LAB: Registering sources in the Purview portal

Scanning data

To automate the process of collecting and updating the meta-data stored in Purview, scans need to be scheduled. Scanning on-prem data requires an extra step of configuring a self-hosted integration runtime.

• Setting up a scan
• Defining scan sets
• Scheduling a scan
• Using Azure Key Vault
• LAB: configuring data scan

Scanning on-premises data

On-premises data sources require extra setup to scan them. They are normally shielded from Internet access by firewalls and other protection. So in order to scan them a self-hosted integration runtime needs to be setup.

• Integration runtimes
• Setup a self-hosted integration runtime
• Configure scans with a self-hosted integration runtime

Query the Purview catalog

Once the Purview catalog has been setup and scanned the meta-data, business users as well as Azure Data Engineers want to be able to query the collected data, but with different tools.

• Query from the portal
• Inspecting lineage information
• Integrating with Azure Data Factory
• Integrating with Azure Purview
• LAB: Query the Purview catalog

Working with Governance domains

To keep the governance effort manageable, the resources can be split up into Governance domains. Each of these can have their own access policies, glossary terms and data products.

• Creating Governance domains
• Working with Governance domains
• Setup Data products

Glossary and other relevant governance data

Not all important data for governance can be automatically extracted. This module goes into the process of manually enriching the scanned data with information only business users can provide. A business glossary is a first important piece of information: It defines the crucial concepts such as products, customers etc. But scanned resources can have additional properties as well, such as owners, experts etc. One can even define and add custom attributes.

• Building glossaries
• Creating Term Templates
• Editing the catalog items
• Working with custom attributes
• LAB: enriching the Purview catalog

Purview Health Management

After collecting and storing metadata in the Purview catalog, it is important to keep track of the health of the data. Health management contains built-in controls, on which tresholds can be set. Actions are offred to improve the data health were necessary.

• Health Management
• Inspecting the Health Controls
• Configuring the Data Quality settings
• Inspecting the Actions and Health Reports

Data Shares

Sometimes you want to share data with other players: audits, or support from external consultants are such typical scenarios. Azure Data Share is a service that can help you share this data, but you can control this from within Purview.

• The need for Data Share
• Setup Data Share using Purview

Controlling data access

When users consult the meta-data they often discover data sources to which they don't have access. To grant them permissions, Purview allows (for a limited set of sources) to grant these permissions from the Purview portal directly.

• 3 types of granting data access
• Setup data access policies
• Configuring Self-service access policies
• Setup approval workflows
• LAB: Controlling data access

Purview REST service

If you want to integrate Microsoft Purview in your custom application, you can use the REST interface to interact with Purview. But if you are not into REST coding, there are other techniques available as well, such as a command-line interface (CLI) and a PowerShell package

• Purview and Apache Atlas API
• Calling the API from PowerShell
• LAB: interacting with Microsoft Purview via REST API