Forum Discussion
Fabric Power BI Semantic model refresh
Dear Experts,
For an existing Warehouse connection, can we reuse it for new semantic model to refresh replacing the SSO. Currently, the new semantic model is unable to select existing connection and expecting a new connection. Is this bug or we have to create new connection everytime we create a new semantic model. Please suggest. ("The existing connections are visible but unable to select to new semantic model.")
Thanks in advance.
This is by design, not a bug. In Fabric, a PBI semantic model cannot reuse an existing Warehouse connection if the auth context (SSO vs non-SSO / different identity binding) does not match. Even though the existing connections are visible, they are intentionally disabled for selection when creating a new semantic model if SSO settings differ. Each semantic model stores its own connection + credential binding, so when you replace or change SSO, Fabric forces creation of a new connection. You must create a new connection per semantic model when SSO or auth context changes; reuse is not supported today.
To avoid connection explosion:
-
Use SPN: Fabric Warehouses support SPN authentication. This is the cleanest way to replace SSO and ensure the refresh doesn't break when a dev's password changes.
-
Connection Sharing: Create a "Production Warehouse Connection" object and share it with your "Creators" group with User permissions. This allows them to "pick" that connection for their new models without seeing the credentials.
-
API Automation: For a truly scalable CoE approach, use the Datasets - Bind To Gateway (or Cloud Connection) REST API to programmatically point new models to your standard shared connection.
-
-
-
3 Replies
- Vinodh247
Super User
This is by design, not a bug. In Fabric, a PBI semantic model cannot reuse an existing Warehouse connection if the auth context (SSO vs non-SSO / different identity binding) does not match. Even though the existing connections are visible, they are intentionally disabled for selection when creating a new semantic model if SSO settings differ. Each semantic model stores its own connection + credential binding, so when you replace or change SSO, Fabric forces creation of a new connection. You must create a new connection per semantic model when SSO or auth context changes; reuse is not supported today.
To avoid connection explosion:
-
Use SPN: Fabric Warehouses support SPN authentication. This is the cleanest way to replace SSO and ensure the refresh doesn't break when a dev's password changes.
-
Connection Sharing: Create a "Production Warehouse Connection" object and share it with your "Creators" group with User permissions. This allows them to "pick" that connection for their new models without seeing the credentials.
-
API Automation: For a truly scalable CoE approach, use the Datasets - Bind To Gateway (or Cloud Connection) REST API to programmatically point new models to your standard shared connection.
-
-
- svenchio
Great answer Vinodh247 thanks for sharing! Just a quick additional note for any one interest in this topic that I very recently got myself aware, in fabric there's also a new interface announced in Oct 2025 Announcing a new Fabric REST API for connection binding of semantic models | Microsoft Power BI Blog | Microsoft Power BI as described "We are releasing a new Fabric REST API for configuring connection bindings for semantic models. A connection binding defines what data connection a semantic model will use to connect to an underlying data source. In scenarios where data sources change—such as moving from development to production environments, migrating infrastructure, or switching connection details" Hope it further contributes to this or similar scenarios, it was very useful on mine 😉 Best of lucks and regards
Thanks Vinodh.
I tried with existing secret key and created new connection to map the semantic model refresh. It worked!!
-
