Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount.
Register nowThe Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.
I have seen this posted in some other topics, but so far, didn't find any sort of awnser.
Here's my deal: i'm feeding the data via HTTPS and using a self-signed certificate.. in a regular web browser, you can just ignore the alerts and proceed with it, but in Power BI it completely stops the imports.
"Could not establish trust relationship for the SSL/TLS secure channel." - this is the error it gives me back.
My question is .. is there any sort of way we can "ignore" this specific alert and use a self-signed certificate to be able to test our data source properly?
Until this moment, I have not found this information.
Any help or guidance via links that can help will be much appreciated.
I managed to get self signed certificates working with the method below. It only works with the downloaded Desktop version not the Windows Store app. You can't modify files in a Windows Store app.
Update the file C:\Program Files\Microsoft Power BI Desktop\bin\Microsoft.Mashup.Container.NetFX45.exe.config to:
<configuration> <system.net> <settings> <servicePointManager checkCertificateName="false" checkCertificateRevocationList="false" /> </settings> </system.net> </configuration>
Restart Power BI.
I've been looking for this solution for a long time. Thanks! No solution was found for a Windows Store app?
Use http instead?
If HTTP was a valid option for what I pretend to do , I would. In this case it is not, the information is sensitive.
Anyway, so far, if you install a domain certificate you need to add that certificate's supplier onto your certificate store.
That means the computer where you are running Power BI must trust a certificate supplied by A.
So in that computer, you add "A's Certificate" to your local machine certificate store.
This way you can at least test your project.
But anyway, it still seems to be too much of an extensive workaround when so many browsers already surpass this issue other than the warning.