Start Here: Microsoft Purview Data Products, Data Assets and Ownership

If you are new to Microsoft Purview, start here.

This page explains the relationship between three concepts that are easy to confuse: Microsoft Purview Data Products, Microsoft Purview Data Assets and Data Asset Ownership.

The simplest way to think about them is:

Data Product = the business-facing concept.

Microsoft Purview Data Assets = the underlying data or information resources represented in Purview.

Data Asset Ownership = the business accountability for those assets.

How the three concepts fit together

Business purpose or use case → Microsoft Purview Data Product → Related Microsoft Purview Data Assets → Accountable Data Asset Owner + Stewardship → Governance Baseline Met → Trusted business use

This relationship matters because a Data Product is not simply a database, table, file or report, and the person who owns the Data Product does not automatically become the owner of every Data Asset associated with it.

1. Microsoft Purview Data Product

A Microsoft Purview Data Product is a business-facing concept. It brings together related Microsoft Purview Data Assets around a defined business purpose or use case and adds the business and governance context needed to help people discover, understand, assess and appropriately use the data.

The important starting question is:

Why does this Data Product exist, and what business purpose or use case does it support?

A Data Product should therefore not simply reproduce the technical structure of the organisation's data estate.

Read: What Is a Microsoft Purview Data Product? — Data SkyLab Studio Definition

2. Microsoft Purview Data Asset

A Microsoft Purview Data Asset is the metadata representation of a data or information resource within Microsoft Purview Data Map.

Depending on the source and supported asset type, this can represent resources such as databases, schemas, tables, views, columns, files, documents, Databricks assets, Microsoft Fabric assets and Power BI assets.

The underlying data normally remains in its source system. Microsoft Purview stores and uses metadata about the resource so that it can be discovered, understood and governed.

A Data Product can contain or be associated with multiple Microsoft Purview Data Assets, and the same Data Asset can legitimately support more than one Data Product.

Read: Data Asset, Information Asset, Dataset and Microsoft Purview Data Asset

3. Data Asset Ownership

A Data Asset Owner is the business role with clear accountability and sufficient decision authority for the Data Asset, including its meaning, fitness for purpose, appropriate use, governance and lifecycle.

Ownership should follow business accountability and authority, not simply technical custody.

A database administrator, data engineer, report developer, platform team or frequent consumer does not automatically become the Data Asset Owner merely because they build, host, administer or use the asset.

Do not begin with: “Who can we put in the Purview Owner field?” Begin with: “Where does accountability for this data actually sit?”

Data Product Owner and Data Asset Owner are not the same role

This is one of the most important distinctions in the model.

The Data Product Owner is accountable for the Data Product.

The Data Asset Owner remains accountable for the underlying Data Asset.

The same person may hold both roles where the accountabilities genuinely align, but this should be an explicit governance decision rather than an assumption.

Associating a Data Asset with a Microsoft Purview Data Product does not transfer accountability for that Data Asset to the Data Product Owner.

Discovery does not equal governance

Microsoft Purview can discover and register technical assets before the organisation has completed the governance work around them.

Within the Data SkyLab Studio approach:

Discovered → Business Accountability Identified → Accountable Data Asset Owner Identified → Stewardship Established → Governance Baseline Met → Data Product Ready → Associated with Data Product(s) → Continuously Governed

Discovery does not equal governance.

What should you read next?

Use the following learning path in order:

1. What Is a Microsoft Purview Data Product?
   Understand the business-facing concept, purpose, value, relevance and trust.
2. Data Asset, Information Asset, Dataset and Microsoft Purview Data Asset
   Understand the assets that sit underneath the Data Product and how the terminology differs.
3. Microsoft Purview Data Asset Ownership Policy
   Understand the rules for accountability, stewardship and governance readiness.
4. How to Identify a Microsoft Purview Data Asset Owner — Guidance
   Learn how to identify the correct accountable business owner.
5. Microsoft Purview Data Asset Ownership Decision Tree
   Apply the ownership decision consistently to real Data Assets.

The relationship in one sentence

A Microsoft Purview Data Product brings together relevant Microsoft Purview Data Assets around a business purpose, while each Data Asset retains its own accountable business ownership and appropriate stewardship.

Once that relationship is understood, the rest of the Microsoft Purview governance model becomes much easier to apply consistently.