When deploying Direct Lake semantic models via Deployment Pipelines, the Lakehouse source is incorrectly treated as an external SQL source. This results in broken lineage and prompts for credentials.
Even when using deployment rules to update the SQL endpoint and database ID, the semantic model does not re-bind to the Lakehouse in the target environment.
Expected behavior:
Deployment Pipelines should natively support Direct Lake re-binding, maintaining proper lineage and avoiding unnecessary credential prompts.
Current workaround:
Using the semantic-link-labs library to rebind the semantic model programmatically post-deployment.
lbendlin
on:
Fabric Copy Activity Upsert Needs Native Audit Col...
on:
Power BI Subscriptions enhancements sorely needed
on:
Ragged Hierarchy Display options in Matrix Visual
miguel
on:
Personalized Source List in Get Data