A bundle of related data assets, such as tables, files and Power BI reports, packaged for a defined use case with owners and a business description, so others can discover and request access to it.
A data product is a bundle of related data assets, such as tables, files and Power BI reports, packaged for a defined use case. It carries named owners and a business description, so that other people in an organization can discover it and request access to it. The idea shifts attention from individual technical objects to a collection that is organized around a business purpose and presented in terms that business users can understand.
The concept is closely tied to the Unified Catalog in Microsoft Purview, and the official documentation describes how data products are created and managed there. According to the episode "Microsoft Purview Data Map - Simply Explained", the Unified Catalog offers a more business-oriented discovery experience in which users can search for understandable data products rather than relying exclusively on technical names. In that setting, a data product acts as the unit that people look for, evaluate and ask to use.
The same episode gives an illustrative example. Finance could publish a pricing analytics data product that contains relevant source information, cleaned data in Microsoft Fabric, and the approved reporting assets used for monthly analysis. Instead of employees hunting through folders and asking colleagues which spreadsheet is correct, the data product gathers the relevant assets in one place and presents them with a description and responsible owners. This is what makes the packaging useful: the owners and the business description tell consumers what the data is for and who stands behind it.
The episode "Microsoft Purview Data Governance for Information Architects" describes the roles and steps needed to set data products up. Users are assigned the governance domain creator role, which allows them to build governance domains. At least one governance domain is created and a governance domain owner is assigned. Data product owners are then assigned, and at least one data product is created within the governance domains. To let others explore the results, users are given Unified Catalog reader permissions, which allows them to view and explore data products within the governance domain. The episode also notes that a unified catalog helps consolidate five catalogs into one, and it lists better scale, higher adoption and faster time-to-insight among the benefits.
Data products also appear as an organizing principle in Microsoft Fabric guidance. The episode "Fix Wrong Copilot Numbers in Microsoft Fabric" recommends using one workspace per data product unless specific constraints justify otherwise. It pairs this with documenting the default pattern and approved exceptions, and with educating teams on the intent of governance, not just the rules. Similarly, "Secure Microsoft Fabric Data Pipelines" says that one workspace per data product gives moderate isolation, while multiple workspaces with strict separation of duties give high isolation, and that data products should be consolidated only when necessary.
In practice, decisions around a data product concern its scope, its ownership and its boundaries. Teams decide which related assets belong together for a use case, who is accountable as owner, and how the product is described so that it can be found. They also decide how it maps to Fabric workspaces and how much isolation sensitive workloads require. Taken together, the sources treat a data product as both a discovery unit in the Unified Catalog and a structuring unit for governance and workspace design.
Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.
Data rarely stays in one app: it is copied, exported, renamed and forgotten across Outlook, Teams, SharePoint and Fabric. This episode is for Microsoft 365 admins, data owners and compliance teams who need a plain-English map of Microsoft Purview. You learn…
Microsoft Purview is already in your tenant, and that ease is exactly why so many data governance rollouts end in permission sprawl and an unused catalog. This episode shows data governance and platform teams how to roll out Purview use case first, with a…
Questions marked with AI were written with AI from the facts on this page.
What does a data product contain? (AI)
It is a bundle of related data assets, such as tables, files and Power BI reports, packaged for a defined use case. It also has owners and a business description so others can discover it and request access.
Where are data products managed in Microsoft Purview? (AI)
They are created and managed in the Unified Catalog, within governance domains. The episode on Purview Data Governance says data product owners are assigned and users receive Unified Catalog reader permissions to view and explore them.
How do data products relate to Microsoft Fabric workspaces? (AI)
Episodes on Fabric recommend one workspace per data product unless specific constraints justify otherwise. They describe this as moderate isolation, with multiple workspaces and strict separation of duties for high isolation.
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Experts and companies for this topic
Nobody has listed this topic yet. Add it to your profile.