Issue with Azure Databricks Connector in Power BI via VPN and Remote Desktop

[mh2587]

Dear All,

I hope you're all doing well. I'm encountering a peculiar issue in Power BI. When I connect via VPN and use Remote Desktop, the Azure Databricks connector is not visible. However, when I access Power BI locally (without using Remote Desktop), the connector appears as expected.

Has anyone experienced a similar issue or know the potential root cause?

Thank you

[Anonymous]

Hi @mh2587 ,

Did Ritaf1983 reply solve your problem? If so, please mark it as the correct solution, and point out if the problem persists.

Best Regards,
Adamk Kong

[mh2587]

Not Solved but we used the alternative connector

[Ritaf1983]

Hi @mh2587, unfortunately, I’m not very knowledgeable when it comes to IT issues my expertise is in creating charts, for better or worse 🙂

But I asked our group in the WhatsApp communities I manage, and these are the options that came up as potential causes and solutions you might consider:

1. Network Policies and Permissions: The VPN connection may restrict certain services or network traffic, which could prevent Power BI from detecting or displaying the Azure Databricks connector. Check with your IT team to see if any firewall rules or network restrictions might be affecting this.

2. Remote Desktop Configuration: Some configurations in Remote Desktop might limit access to certain resources on your local machine, which could interfere with how Power BI accesses its connectors. Ensure that all local resources (especially for network and internet) are enabled when using Remote Desktop.

3. Power BI Version and Installation Location: If Power BI is installed on the remote server rather than on your local machine, the environment on the server may not have the required access to the Azure Databricks connector. In this case, try installing Power BI on your local machine and accessing it through the VPN instead.

4. Credential Issues: Sometimes, VPN connections can interfere with credential passing or authentication. Make sure that your authentication credentials are being passed correctly through the VPN and that there are no issues with single sign-on (SSO) or multi-factor authentication (MFA).

Hopefully it helps.

If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly

[zohaib_altaf]

I am facing the same issue since a week and I am unable to found a solution to this thing. As an alternative I am using ODBC connection but that is not as much simple to use.

[mh2587]

Anyone, Kindly help me in this 
@Ritaf1983
@amitchandak