Fabric LH/WH Encryption with PBI Desktop

[CeeVee33]

Hi Experts -

I'm reaching out for a weird action by Fabric Lakehouse & Warehouses.

In SSMS -

• when I am at home on VPN, I connect to them with "Mandatory" Encryption.
• when I am in office on corp network, I need to change it to "Strict(SQL Server 2022 and Azure SQL)" encryption.

At the end, I connect to them. I have no issues. No complains.

However, I cannot work on my PBI Desktop reports connected to the LH/WH when I am in office. Even if I select the "Encrypt" connections in PBI data source settings, still no success.

I'm not a technical expert in network, but I can envisage that IT needs to enable a port or something.

Please advise how do I get past this issue in PBI Desktop.

Thank you

[v-tsaipranay]

Hi @CeeVee33 ,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[CeeVee33]

Hi @v-tsaipranay  - no I'm still working with my IT Teams on this one. It is a slow process. I do not want to mark it as a solution and let others chase their tail, if it doesnot work for me. 😞

[v-tsaipranay]

Hi @CeeVee33 ,

Thank you for the update. I completely understand  it’s important to ensure the solution works reliably before marking it as resolved.
Please take your time, and feel free to reach out if there’s anything I can assist with in the meantime.
We encourage you to continue using the Microsoft Fabric Community Forum for any further updates or questions.

Thank you.

[CeeVee33]

Good point, @SamsonTruong . I should have mentioned what all have I tried.

Yes, I've tried connecting using the OneLake Catalog option and Direct SQL Server Option. Both do not work. I get the below error

[v-tsaipranay]

Hi @CeeVee33 ,

Thank you for reaching out to Microsoft fabric community forum. Also thank you @SamsonTruong  for your input.

Also thanks for confirming and providing screenshot of the error. The error you’re encountering typically indicates a network-level interruption. This is often caused by firewall rules, proxy settings, or port restrictions within your corporate network environment.

Please check with your IT team to ensure that the necessary ports particularly 1433 (used for SQL connections) and 443 (used for HTTPS/OneLake connections) are open and unrestricted.

Additionally, please confirm that TLS 1.2 or higher is supported and that all required Microsoft root certificates are trusted on your machine. As a quick diagnostic step, you might also try connecting from a different network, such as a personal hotspot, to verify whether the issue is network specific.

Hope this helps. Please reach out for further assistance.

If this post helps, then please consider to Accept as the solution to help the other members find it more quickly and a kudos would be appreciated.

Thank you.

[CeeVee33]

Thanks @v-tsaipranay for the inputs. 

I will have to talk to the IT teams to get this fixed. I am sorry, I think I'll not accept as a solution until IT teams can fix as per your advice.

My biggest concern is same destination gets access by different encryption method on company and non-company networs. So there is something amiss. A destination should be open on only one method.

I'll get back soon.

[v-tsaipranay]

Hi @CeeVee33 ,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[v-tsaipranay]

Hi @CeeVee33 ,

Thanks for the update, totally understandable that you'd want to check with your IT team first.

You’re right to be cautious about the same destination using different encryption methods on different networks. That does sound like something worth looking into. Once your IT team has had a chance to review, feel free to reach out. I’m happy to help you.

Thank you, and please keep using the fabric community forum.

[SamsonTruong]

Hi @CeeVee33 ,

When you are connecting to the LH/WH in Power BI Desktop, are you using the SQL Server connector and using the SQL Analytics Endpoint?

If so, can you try accessing the LH/WH through the OneLake catalog instead and see if it still generates an error when attempting to connect?

If this helped, please mark it as the solution so others can benefit too. And if you found it useful, kudos are always appreciated.

Thanks,

Samson