Purview - Data Quality - UI

Question

Purview - Data Quality - UI

Todd Spurling 0

Purview is a great product.

The Data Quality UI could be easier to use. It's a lot of mouse clicks to get from a managing a Data Product (adding data assets) to the data quality rules for the same.

Rule: A rule lives under a data asset so if you want to change a rule to point to say a new view instead of a table, you have to delete the rule, go to the new asset and recreate again.

The UI would require much less effort if the Data Product offered a tab with a rules TABLE view where the columns are

RuleName, Dimension, DataAsset, Data Element, RuleFormulaPreview, ... , Score

and the user can sort on any column; and upon editing the rule the user can change the data asset & element it applies to.

Can this suggestion be considered for voting?

Ganesh Chelluri 190 Reputation points Microsoft External Staff Moderator

2026-08-03T05:53:16.18+00:00
Hi @Todd Spurling ,

Thanks for the detailed write-up the click-depth issue and the rule-to-asset binding are both fair points, especially having to delete and recreate a rule just to repoint it from a table to a view.

Microsoft Q&A doesn't have a voting mechanism for feature requests, so this thread won't reach the product team. The right place is the Microsoft Purview feedback portal at https://feedback.azure.com post it there and it becomes votable, and the Purview team reviews and triages items from that portal directly.

Worth splitting it into two separate items when you post, since they'd likely be handled by different parts of the team:

A rules table view on the Data Product with sortable columns

Allowing a rule to be repointed to a different data asset or element on edit

Separate items usually track better and pick up votes more easily than one combined request.

Your answer

Ganesh Chelluri 190 Reputation points Microsoft External Staff Moderator

2026-08-03T05:53:16.18+00:00

Hi @Todd Spurling ,

Thanks for the detailed write-up the click-depth issue and the rule-to-asset binding are both fair points, especially having to delete and recreate a rule just to repoint it from a table to a view.

Microsoft Q&A doesn't have a voting mechanism for feature requests, so this thread won't reach the product team. The right place is the Microsoft Purview feedback portal at https://feedback.azure.com post it there and it becomes votable, and the Purview team reviews and triages items from that portal directly.

Worth splitting it into two separate items when you post, since they'd likely be handled by different parts of the team:

A rules table view on the Data Product with sortable columns

Allowing a rule to be repointed to a different data asset or element on edit

Separate items usually track better and pick up votes more easily than one combined request.