Microsoft Purview Data Governance: Updates & Roadmap
summary
Purview claims a real roadmap: 56 sources are public-preview or GA and four private-preview connectors (AWS Redshift, Tableau, datawverse and Databricks Unity Catalog) roll out next, with Unity Catalog metadata in private preview and lineage ingestion planned via Databricks APIs. The platform moves to an always-attached tenant model with automatic attach for Microsoft cloud services, exposes relevance APIs and saved-search/rating features for catalog discovery, adds Teams integration and Power BI embedded for customizable data-state insights, and already ships sharing lineage for tenant-level in-place shares.
AI-written summary · about
chapters (16)
- 0:00Purview Data Governance intro
- 2:03Hybrid data integration approach
- 3:31Expanding data sources
- 5:22Tenantization model
- 7:50Always attached strategy
- 10:20Consent model alternatives
- 12:46Tenant-level account upgrade
- 15:16Always governed strategy
- 17:23Catalog browse improvements
- 23:42Data stewardship updates
- 28:40Business workflows in catalog
- 32:32Versioning and auditing
- 36:26Data State insights reports
- 39:15Policy access management updates
- 41:42Roadmap timeline
- 43:06Q&A on SQL governance
related talks
54mData Governance using Azure Purview
52mConnect your data artifacts with Azure Synapse Analytics and Azure Purview
15mEvolving Data Governance With Unity Catalog
23mKeynote Analysis
32mHow Vista is moving away from centralized data for good
11mMicrosoft & Power BI
52mWhat's new on the Power BI Roadmap
26mMeeting The Evolving Data Intelligence Expectations