โ05-13-2025 03:38 AM - edited โ05-13-2025 03:39 AM
In Power BI, there's an "Azure Databricks workspace" connector which, unlike the "Azure Databricks" connector, allows you to connect using a service principal defined in Azure Entra ID (rather than within Databricks).
While I can create this connector, it's unclear how to use itโand why it exists as a separate connector type.
Help?
โ05-14-2025 09:26 AM
Hey @Malthe ,
You're right in that the main difference is the workspace connector is designed for service principal access. There's a few reasons one might want to use this option instead of user-based auth, mainly that it aligns better with some security policies and is better practice as a credential for scheduled refreshed. If you don't need to use an SP, I would just use the user-level standard connector.
โ05-14-2025 01:56 PM
But then how would you get a Power BI semantic model to use the connection created via a service principal (Azure Databricks workspace)?
โ05-15-2025 05:20 AM
Agree with @seun_adigun, there is no obvious way to actually use this connector. Neither just by clicking around or reading the documentation.
โ05-15-2025 09:09 PM
The "Azure Databricks Workspace" connector in Power BI allows authentication using a service principal from Azure Entra ID, providing more secure and scalable access management compared to the traditional personal token-based "Azure Databricks" connector. It is ideal for automated workflows and enterprise environments where centralized access control is needed.
Passionate about hosting events and connecting people? Help us grow a vibrant local communityโsign up today to get started!
Sign Up Now