Databricks previews publishing Unity Catalog metric views directly to Power BI semantic models
The private preview translates governed metric definitions into DAX measures one way only, so edits made in Power BI are not written back and access control depends on the query mode.

Databricks has announced Publish to Power BI, a capability that pushes Unity Catalog metric views into Power BI semantic models. It is in private preview, available through account teams.
According to Databricks, each metric view becomes one table in the Power BI model: dimensions become columns and measures are translated into DAX. Power BI queries the metric view itself, so joins and calculations run in Databricks and no Power BI relationships need rebuilding. Teams can publish on demand from Catalog Explorer or add a Power BI task to a Lakeflow Job to republish on a schedule or after upstream refreshes.
Publishing runs one way only; edits to a published measure in Power BI are not written back. Databricks says DirectQuery honours Unity Catalog access controls, row filters and column masks, while in Import mode the loaded copy follows Power BI permissions.
Editor’s note: This article is based solely on Databricks’ own blog announcement.
Why it matters
Organisations with many Power BI workspaces often hold divergent copies of the same KPI; this approach makes the Unity Catalog metric view the single owned definition, so metric ownership and change control need to sit with whoever maintains it. Teams should note that governance guarantees differ by mode: Import copies data into Power BI under Power BI permissions, outside Unity Catalog masks and row filters. Because Power BI edits are not synced back, stewards should consider how to prevent or detect local measure changes that silently diverge from the governed definition.
Status: Preview. Private preview; access via Databricks account teams
Sources
Was this useful?
Thanks. What was the problem?
Thank you — this helps us choose what to cover. If you spotted an error, please tell us what it is.
Prepared with AI assistance and reviewed by the editor before publication. Spotted an error? Tell us — see our editorial policy and methodology.
Governance areas
Who should care
- CDO
- Data stewards
- BI and analytics leads
- Data platform architects