Forum Discussion
Unable to pull data from Databricks through Dataflow Gen 1
Hi,
In Dataflow, I am unable to pull data from Databricks, with gateway option selected as None. I am receiving error: "[Microsoft][ThriftExtension] (8) Authentication/authorization error occurred. Error details: Bad status with no error message: Unauthorized/Forbidden: Status code : 403." My personal access token in Databricks is valid.
When I am trying to pull the same data from Databricks through Power BI desktop using the Databricks connector, its working fine.
Any help in this matter will be highly appreciated.
Hi adipta
here are the troubleshooting steps for Power BI Dataflow Gen 1 – Databricks 403 Error. Please try these and let us know if the issue still persist.
- Verify Authentication Method : Dataflow Gen 1 in Power BI Service commonly requires OAuth/service principal (Databricks Client Credentials) authentication. Using a Personal Access Token (PAT) may not always work for Dataflows, even if it works in Power BI Desktop. Switch to OAuth or service principal if possible
- Double-Check Token and Permissions : Ensure your Databricks user/service principal has the necessary permissions on the SQL Warehouse and that the token is still valid. If using PAT, regenerate and update it in Dataflow credentials, but prefer OAuth for cloud refreshes
- Review Network and Firewall Rules: Confirm that your Databricks workspace or SQL Warehouse allows access from Power BI Service IP ranges. Add necessary exceptions if needed.
- Use the Correct Gateway Option : If Databricks is not exposed publicly or requires a secure connection, use an On-premises Data Gateway or VNet Gateway. Do not set Gateway = None unless Databricks is accessible from the cloud.
- Validate Connection Details : Double-check the SQL Warehouse hostname and HTTP path. Ensure there are no typos and the correct cluster/database is being targeted
- Test in Power BI Desktop : Always confirm the same connection parameters (hostname, HTTP path, authentication type) work in Power BI Desktop before configuring in Dataflow, but remember that authentication context differs between Desktop and Service.
- Update to Dataflow Gen 2 (if possible) : Migration to Power BI or Fabric Dataflow Gen 2 is recommended, as it has improved Databricks connector support and more flexible authentication.
🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.
💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.
🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.
🔗 Curious to explore more? [Discover here].
Let’s keep building smarter solutions together!
5 Replies
Your Databricks PAT works in Desktop but fails in Dataflow Gen1 because cloud-to-Databricks isn’t supported without a gateway → hence 403 error.
Fix:
Use an On-prem gateway for Gen1, or
Move to Dataflow Gen2 (supports direct Databricks).
👉 Root cause: Gen1 requires gateway, Gen2 doesn’t.
Hi adipta
here are the troubleshooting steps for Power BI Dataflow Gen 1 – Databricks 403 Error. Please try these and let us know if the issue still persist.
- Verify Authentication Method : Dataflow Gen 1 in Power BI Service commonly requires OAuth/service principal (Databricks Client Credentials) authentication. Using a Personal Access Token (PAT) may not always work for Dataflows, even if it works in Power BI Desktop. Switch to OAuth or service principal if possible
- Double-Check Token and Permissions : Ensure your Databricks user/service principal has the necessary permissions on the SQL Warehouse and that the token is still valid. If using PAT, regenerate and update it in Dataflow credentials, but prefer OAuth for cloud refreshes
- Review Network and Firewall Rules: Confirm that your Databricks workspace or SQL Warehouse allows access from Power BI Service IP ranges. Add necessary exceptions if needed.
- Use the Correct Gateway Option : If Databricks is not exposed publicly or requires a secure connection, use an On-premises Data Gateway or VNet Gateway. Do not set Gateway = None unless Databricks is accessible from the cloud.
- Validate Connection Details : Double-check the SQL Warehouse hostname and HTTP path. Ensure there are no typos and the correct cluster/database is being targeted
- Test in Power BI Desktop : Always confirm the same connection parameters (hostname, HTTP path, authentication type) work in Power BI Desktop before configuring in Dataflow, but remember that authentication context differs between Desktop and Service.
- Update to Dataflow Gen 2 (if possible) : Migration to Power BI or Fabric Dataflow Gen 2 is recommended, as it has improved Databricks connector support and more flexible authentication.
🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.
💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.
🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.
🔗 Curious to explore more? [Discover here].
Let’s keep building smarter solutions together!
Hi adipta,
We would like to confirm if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.
grazitti_sapna & Shahid12523 Thanks for your prompt response
Thank you for your patience and look forward to hearing from you.
Best Regards,
Prashanth AreWe would like to confirm if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.
Thank you for your patience and look forward to hearing from you.
Best Regards,
Prashanth AreMay I ask if you have resolved this issue? If so, Can you please share the resolution steps here. This will be helpful for other community members who have similar problems to solve it faster.
If we don’t hear back, we’ll go ahead and close this thread. For any further discussions or questions, please start a new thread in the Microsoft Fabric Community Forum we’ll be happy to assist.
Thank you for being part of the Microsoft Fabric Community.
