Data estate health actions in Microsoft Purview (Preview)
Data estate health actions give you and your users steps to take to improve data health and governance across your data estate. These actions correspond to the checks made to calculate a data product's data governance health control score. Addressing these actions raises your health score and promotes an overall more useable and discoverable data catalog.
Prerequisites
- You need data health reader permissions to be able to view Data Estate Health information.
- You need data health owner permissions to be able to update and assign health actions
View data estate health actions
- Open the Microsoft Purview governance portal and select the Data Catalog.
- Select the Data estate health drop-down.
- Select Health actions
Now you're on the main actions page, where you can see a list of actions, how long they've been active, the target for the action, and the owner.
You can search by keyword, or filter these actions by many values, including: assigned to, business domains, active since, action types, and more.
You can also group actions by selecting the Group by drop-down, to view actions by:
- Severity
- High
- Medium
- Low
- Finding types and subtypes
- Finding subtype
- Finding name
Tip
If you're not seeing the actions you expect, check the applied filters and group.
Available actions
Available actions are determined by metadata quality rules established in Data Estate Health or by data quality rules.
For more information about data quality actions, see the data quality actions article.
For more information about metadata quality, see the metadata quality article.
Here's a list of actions that are available out of the box from metadata quality:
Finding type | Finding subtype | Finding Name | Severity |
---|---|---|---|
Access and use | Compliant data use | Missing terms of use on data products | Medium |
Self-serve access enablement | Missing access policy on data products | Medium | |
Discoverability | Data cataloging | Data product not linked to data assets | High |
Missing description on data products | High | ||
Missing published glossary terms on data products | High | ||
Missing use case on data products | High | ||
Data products connection | Data product not linked to data assets | Medium | |
Estate curation | Classification and labeling | Missing classification on data assets | Medium |
Health observability | Data estate health monitoring, alerting, and insights | ||
Metadata quality management | Data product usability | Business domain description length is fewer than 100 characters | Medium |
Data product description length is fewer than 100 characters | Medium | ||
Published glossary term's description length is fewer than 25 characters | Medium | ||
Linked assets | Data product description length is fewer than 100 characters | Medium | |
Missing published glossary terms on data product | High | ||
Trusted data | Data product certification | Data product isn't endorsed | Low |
Data product ownership | Missing owners on data assets | High | |
Missing owners on data products | High | ||
Data quality enablement | Missing data quality scores on data assets | Medium | |
Value creation | Business OKRs alignment | Missing OKRs on data products | Medium |
Tip
If the actions you're seeing don't match up with these values and severities, check metadata quality. Your organization may have implemented custom checks and severities.
Action details
To see an action's details, select it. Here you'll see the actions owners, the associated data product and business domain, as well as it's reason and any potential recommendations for resolving it.
Resolve an action
To resolve an action, you should:
- Assign owners who will take steps to resolve the recommendations.
- The owners should investigate the issue based on the provided information and recommendation.
- The owners should update the status to reflect their current progress.
- When they've made the suggested updates, the action's status should be updated to Resolved and the action should be saved.
As the entire data estate health refreshes in the next scheduled run, all resolved actions from the catalog will be reconciled. In case an action is artificially marked as 'resolved' but the issue in the catalog remains, the action status will be changed and added back to the health actions queue.