Forum Discussion
Advocate IIDual mode doesn't work with directQuery with gateway connection
Hi dmkblesser - if you are using Dual storage mode in Power BI alongside an on-premises data gateway and Azure Databricks is likely due to limitations in how the gateway handles import mode and DirectQuery hybrid configurations when SSO (Single Sign-On) via Azure AD is involved.
Azure AD SSO is specifically designed for DirectQuery mode. When you introduce Import Mode (even partially), the dataset relies on the gateway for managing refresh operations for imported data, which operates differently from DirectQuery.
In Dual mode, dimension tables in "Dual" may act as cached tables (imported) when used for aggregation, and these need a proper configuration for the gateway to refresh successfully.Your setup uses Azure AD SSO for DirectQuery, but Import mode queries require explicit authentication through the gateway (e.g., username/password or OAuth).
Skipping the "Test Connection" might have bypassed validation, but during refresh, Import mode queries can't authenticate due to missing credentials.If incremental refresh is configured on fact tables in Import mode, the gateway will need to handle these operations. When the dataset is set up with Dual storage mode, Power BI Service may face issues switching contexts between Import and DirectQuery during refresh.
Super UserHi dmkblesser - if you are using Dual storage mode in Power BI alongside an on-premises data gateway and Azure Databricks is likely due to limitations in how the gateway handles import mode and DirectQuery hybrid configurations when SSO (Single Sign-On) via Azure AD is involved.
Azure AD SSO is specifically designed for DirectQuery mode. When you introduce Import Mode (even partially), the dataset relies on the gateway for managing refresh operations for imported data, which operates differently from DirectQuery.
In Dual mode, dimension tables in "Dual" may act as cached tables (imported) when used for aggregation, and these need a proper configuration for the gateway to refresh successfully.
Your setup uses Azure AD SSO for DirectQuery, but Import mode queries require explicit authentication through the gateway (e.g., username/password or OAuth).
Skipping the "Test Connection" might have bypassed validation, but during refresh, Import mode queries can't authenticate due to missing credentials.
If incremental refresh is configured on fact tables in Import mode, the gateway will need to handle these operations. When the dataset is set up with Dual storage mode, Power BI Service may face issues switching contexts between Import and DirectQuery during refresh.
dmkblesserHi Raj, thank you for your response! I will try to use the username and password instead of the SSO just to test it out. In the end, we'd still like to use SSO to utilize the security settings we have from the source. Will do this for experimental purpose. Will update the results later in the post.