Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hello,
We are using Power BI desktop with a Snowflake database. The Snowflake database is integrated with Azure Active Directory for the authentication process. This was achieved with the setup a Service Provider initiated SSO (SAML v2.0) protocol. The protocol starts by opening a web browser window/tab to allow the user authentication process. The issue is when using the Power BI with this architectural model.
Scenario 1:
The Power BI connector that comes with PBI Desktop it seams that doesn't support the configuration. So we've tried another approach to the achieve the authentication through Azure AD, using the Snowflake ODBC and it works, but it will ends with the scenario 2.
Scenario 2:
The SPI SSO starts by opening a web browser window/tab to allow the user authentication process. The issue is the amount of tabs/windows that are opened when using the Power BI Desktop. For a basic model with 5 tables within the same connection it opens 23 different sessions, each one of them with a different session ID and respective token. With the complex models I didn't even try it. This could be solved if PBI Desktop didn't open a new session/connection for every existing query when using the same configuration in this case the same ODBC.
When using the Navigator wizard window to select the objects we need, for every expand click it makes a new authentication and opens a new browser window/tab.
Is there a way to allow PBI to use the same session/connection for all the queries in a data model?
Thanks,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.