Forum Discussion
Issue connecting Databricks to Power BI Service
- 6 months ago
Hey vamshikrishna20 ,
The phrase “Or enable trusted public access for Power BI Service IP ranges” refers to allowing the Power BI Service (which runs in Microsoft’s cloud) to reach your Azure Databricks workspace over the internet, even if your workspace is normally restricted inside a VNet (Virtual Network).
Here’s what it means in simpler terms:
- Azure Databricks in a VNet: Often, organizations deploy Databricks inside a private network for security. This means it cannot be accessed directly from the public internet. Only devices inside the VNet (or connected via VPN/ExpressRoute) can reach it.
- Power BI Service: When you publish a report to the cloud, the Power BI Service needs to connect to Databricks from Microsoft’s servers. If your Databricks workspace is private, it cannot connect by default, leading to “unresponsive” errors.
- Trusted Public Access: Microsoft publishes the IP ranges used by Power BI Service. By configuring your network/firewall to allow incoming connections from these IP ranges, you let Power BI Service access Databricks securely without opening it completely to the internet. Essentially, you’re whitelisting the Power BI Service servers.
In short: It’s a way to let Power BI Service reach your private Databricks workspace without making it fully public, by trusting only Microsoft’s IP addresses.
If this solved your issue, please mark it as the solution so others can find it easily.
If it helped, a quick Kudos is always appreciated it helps highlight useful answers for the community.
Thanks for being part of the discussion !!!
Hi MohdZaid_ -
can you help me understand this - enable trusted public access for Power BI Service IP ranges?
- MohdZaid_6 months agoSuper User
Hey vamshikrishna20 ,
The phrase “Or enable trusted public access for Power BI Service IP ranges” refers to allowing the Power BI Service (which runs in Microsoft’s cloud) to reach your Azure Databricks workspace over the internet, even if your workspace is normally restricted inside a VNet (Virtual Network).
Here’s what it means in simpler terms:
- Azure Databricks in a VNet: Often, organizations deploy Databricks inside a private network for security. This means it cannot be accessed directly from the public internet. Only devices inside the VNet (or connected via VPN/ExpressRoute) can reach it.
- Power BI Service: When you publish a report to the cloud, the Power BI Service needs to connect to Databricks from Microsoft’s servers. If your Databricks workspace is private, it cannot connect by default, leading to “unresponsive” errors.
- Trusted Public Access: Microsoft publishes the IP ranges used by Power BI Service. By configuring your network/firewall to allow incoming connections from these IP ranges, you let Power BI Service access Databricks securely without opening it completely to the internet. Essentially, you’re whitelisting the Power BI Service servers.
In short: It’s a way to let Power BI Service reach your private Databricks workspace without making it fully public, by trusting only Microsoft’s IP addresses.
If this solved your issue, please mark it as the solution so others can find it easily.
If it helped, a quick Kudos is always appreciated it helps highlight useful answers for the community.
Thanks for being part of the discussion !!!