Data product
Concept
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.
함께 자주 다루는 주제
Data product 관련 에피소드에서는 Microsoft Purview도 자주 다룹니다.
Description
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.
| Type | Concept |
|---|---|
| Documentation | Data product – Microsoft Learn learn.microsoft.com |
Articles about Data product (2)
Data product을(를) 다룬 글:
- Microsoft Purview 활성 용어집 용어: 데이터 거버넌스 정책 자동화
· Mirko Peters
Microsoft Purview 활성 용어집 용어가 데이터 거버넌스 정책, 보안 규칙, 그리고 엔터프라이즈 데이터 제품 전반의 규정 준수를 어떻게 자동화하는지 알아봅니다. - Microsoft Purview Active Glossary Terms: Automating Data Governance Policies
· Mirko Peters
Discover how Microsoft Purview active glossary terms automate data governance policies, security rules, and compliance across enterprise data products.
Community wiki
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.
Sources
- Data product – Microsoft Learn learn.microsoft.com
- RSS 피드: Data product
- Articles on this topic: 2
Maintained by Mirko Peters (Microsoft MVP) · Last updated: