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
• Exploring the Microsoft Purview portal
• LAB: Preparing an Azure environment

Data Map Domains 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. Data Map Collections can be grouped into Data Map Domains.

• Introducing the Microsoft Purview Data Map
• Working with Domains
• Creating Collection hierarchies
• Collection Roles
• 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.

• Using the Data Map Solution
• Supported Sources
• Registering Sources
• Registering Fabric (Power BI) 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
• Full versus Incremental 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 Synapse Analytics
• 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.

• What is a Governance Domain?
• Creating Governance domains
• Assigning roles to Governance Domains
• Setup Data Products
• LAB: Setup a Governance Domain

Glossary and Other 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
• Editing the catalog items
• Bulk import into glossaries
• LAB: Creating and using Glossaries in the Unified 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 thresholds can be set. Actions are offered to improve the data health were necessary.

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

Controlling data access

When users consult the meta-data they often discover data sources to which they don't have access. Via Purview, users can ask for access to the data.

• Access requests versus Access policies
• Requesting Access
• Configuring Access Policies
• Approving and Provisioning Requests
• Automating with Workflows
• Revoking 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.

• Integrating Purview in your Application
• Creating App Registrations and working with Bearer Tokens
• Purview and Apache Atlas API
• Calling the Unified Catalog API
• LAB: interacting with Microsoft Purview via REST API