Microsoft Purview · Unified Catalog Governance
Data Product Owner
Create, update, and read data products within governance domain. Build relationships with concepts across domains.
Scope: Data product management within assigned governance domain
Permissions
- Create data products within assigned governance domain
- Add data assets to data products (requires Data Map permissions)
- Update data product metadata, descriptions, and documentation
- Build relationships between data products and glossary terms
- Configure data product access policies
- Publish data products for catalog users
- Read and reference concepts from other governance domains
Common use cases
- Product manager curating Customer 360 data product
- Analytics lead creating Sales Performance data product
- Data engineer building Customer Churn Prediction dataset product
- Business analyst assembling Marketing Campaign Analytics product
- Data scientist creating ML Training Data product
- Domain team packaging business-ready data for consumers
Best practices
- Create data products aligned to business use cases, not just technical datasets
- Include rich metadata: descriptions, documentation, sample queries
- Add relevant glossary terms to improve discoverability
- Configure access policies for self-service data access
- Publish only when data product is complete and documented
- Regular review and update of data product quality and relevance
- Gather feedback from data consumers for improvements
- Use data profiling and quality features before publication
Security considerations
- Can configure access policies affecting who can request data
- Must have Data Map permissions to view/add assets
- Data products define self-service access patterns
- Should coordinate with data owners before publication
- Access policies must align with data classification and sensitivity