Forum Discussion
Helper IUpdating a Semantic Model to use a different Workspace
I had a call with Microsoft and resolved this issue.
Open Deployment Pipeline’s “Rules”
Chose “Data source rules”
“Server”
Navigate to the Workspace you want the Semantic Model’s data to come from
Click the three dots against the Lakehouse you need to use > Settings
Copy the SQL analytics endpoint > SQL connection string into the “Server” section of the Data source rule
“Database”
Navigate to the Workspace you want the Semantic Model’s data to come from
Click into the SQL analytics endpoint of the Lakehouse you need to use
Copy the GUID after mirroredwarehouse in the URL into the “Database” section of the Data source rule, i.e. the "Artifact ID" in a URL that looks like this https://app.fabric.microsoft.com/groups/<Workspace ID>/<Artifact type>/<Artifact ID>/
In Fabric / Power BI, the Gateway & Cloud connections are basically the configuration that tells the semantic model where to get its data in each environment. In Dev, you might not have explicitly set anything because it can auto-connect to your Lakehouse, but in Prod you’ll need to make sure it points to the right endpoint.
The process usually involves:
1. Go to the semantic model in Fabric → click Settings → Gateway & Cloud connections.
2. You’ll see the list of data sources the model uses (for Direct Lake, this is usually the SQL endpoint of your Lakehouse).
3. Update the connection to point to your Prod Lakehouse endpoint. For cloud sources, this might involve selecting or adding a cloud connection or credentials that have access to Prod.
4. Save changes — the semantic model now queries Prod data, while keeping all your measures, calculated tables, and DAX logic intact.
Basically, the connection settings are just pointers to the right data source, and that’s the only thing you need to change when moving from Dev → Prod.
Helper I1. Go to the semantic model in Fabric → click Settings → Gateway & Cloud connections.
2. You’ll see the list of data sources the model uses (for Direct Lake, this is usually the SQL endpoint of your Lakehouse).
3. Update the connection to point to your Prod Lakehouse endpoint. For cloud sources, this might involve selecting or adding a cloud connection or credentials that have access to Prod.
4. Save changes — the semantic model now queries Prod data, while keeping all your measures, calculated tables, and DAX logic intact.
Basically, the connection settings are just pointers to the right data source, and that’s the only thing you need to change when moving from Dev → Prod.
Doesn't this go against what you said previously?
The GUID you see in dev is automatically regenerated in prod, so each environment’s semantic model has its own internal ID — you don’t need to—and shouldn’t—try to set it manually.
In Settings → Gateway & Cloud connections, I don't see what I _can_ change other than the GUIDS