Forum Discussion
Super UserIssue when mapping the connections on PBI Service - composite model
I have a PBI semantic model where I used live connection to an SSAS tabular model deployed on Azure.
I wanted to add an Excel file, so I had to add a local model and the connections were switched as described here Use composite models in Power BI Desktop - Power BI | Microsoft Learn
The connection changed to Direct Query on the PBI file.
The problem now is when I publish the datasource got disconnected :
What I have already configured?
A cloud connection created on the PBI service for SSAS tabular model but I noticed in the screenshot it is forcing me to switch to an On-prem connection while it still in the last section shows the cloud connection.
Why am I having this behavior ?
Hello AmiraBedh
When combining a cloud-based SSAS connection with a local Excel file in a Power BI composite model, a standard on-premises gateway is required for the Excel component due to Power BI’s architecture and security
The behavior occurs because composite models with mixed data sources (cloud SSAS + local Excel) require a standard on-premises gateway for the Excel component, even
By isolating the gateway requirement to the Excel file and validating SSAS’s cloud configuration, the conflicting UI behavior should resolve
hope this is helpful
When combining a cloud-based SSAS connection with a local Excel file in a Power BI composite model, a standard on-premises gateway is required for the Excel component due to Power BI’s architecture and securityIt's much worse than that. If you are combining these data sources then your cloud source must now also use the gateway. MUST !!! And there is no going back! Unless you delete everything and start over.
3 Replies
- nilendraFabric
Hello AmiraBedh
When combining a cloud-based SSAS connection with a local Excel file in a Power BI composite model, a standard on-premises gateway is required for the Excel component due to Power BI’s architecture and security
The behavior occurs because composite models with mixed data sources (cloud SSAS + local Excel) require a standard on-premises gateway for the Excel component, even
By isolating the gateway requirement to the Excel file and validating SSAS’s cloud configuration, the conflicting UI behavior should resolve
hope this is helpful
- lbendlin
When combining a cloud-based SSAS connection with a local Excel file in a Power BI composite model, a standard on-premises gateway is required for the Excel component due to Power BI’s architecture and securityIt's much worse than that. If you are combining these data sources then your cloud source must now also use the gateway. MUST !!! And there is no going back! Unless you delete everything and start over.
- AmiraBedh
Thank you for your answers ! That was my thought indeed ! 🙂
