Forum Discussion
Cloud Connection - Semantic Model
- 4 months ago
Hi Mikerhode_44 ,
Thanks for reaching out to Community Forum.The difference you’re seeing in the cloud connection types is expected. In Microsoft Fabric, the semantic model from the Data Warehouse shows Azure Data Lake Storage because that reflects how the data is physically stored in OneLake. When you connect to the same model through Power BI, it appears as an Analysis Services endpoint because that’s the layer Power BI uses to query the data. So even though it’s the same data, the connection types do not need to match. For the issue itself, I recommend checking your setup in Power BI Service. Make sure the semantic model is using an Organizational account OAuth2 under Data source credentials, and confirm it is mapped to a cloud connection and not an on-premises gateway, since Fabric sources do not require a gateway. If the issue still continues, you may try re-authenticating or rebinding the dataset to refresh the connection. Also, if you are using the SQL endpoint, keep in mind it may not update instantly, so you may consider using Direct Lake mode if available, as it avoids refresh and sync delays.
Thank you.
Hi Mikerhode_44 ,
Thanks for reaching out to Community Forum.
The difference you’re seeing in the cloud connection types is expected. In Microsoft Fabric, the semantic model from the Data Warehouse shows Azure Data Lake Storage because that reflects how the data is physically stored in OneLake. When you connect to the same model through Power BI, it appears as an Analysis Services endpoint because that’s the layer Power BI uses to query the data. So even though it’s the same data, the connection types do not need to match. For the issue itself, I recommend checking your setup in Power BI Service. Make sure the semantic model is using an Organizational account OAuth2 under Data source credentials, and confirm it is mapped to a cloud connection and not an on-premises gateway, since Fabric sources do not require a gateway. If the issue still continues, you may try re-authenticating or rebinding the dataset to refresh the connection. Also, if you are using the SQL endpoint, keep in mind it may not update instantly, so you may consider using Direct Lake mode if available, as it avoids refresh and sync delays.
Thank you.
Thank you very much. Updating the settings worked. I also added the Entra ID / single sign on check and it resolved everything.