Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Be one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now

Reply
rgouette
Frequent Visitor

undefinedPowerBi to API SSL/TLS error

I'm trying to connect to a Web Datasource for a REST API call.

I am using the Bearer Header, with token, taken from Postman(the API is known good)..

But when I try to connect, I get:

rgouette_0-1731438854352.png

 

 

Ideas?

I see someone in 2019 post the same issue, with no follow-up resolution

Kind thanks,

Rich

1 ACCEPTED SOLUTION

Hi, @rgouette 

Thank you for your swift response.

 

You are correct, which is why I recommend using version 1.2. There has indeed been some discussion regarding the compatibility of Power BI with TLS 1.3. According to the latest information, Power BI primarily supports TLS 1.2, while the support for TLS 1.3 remains unclear.

 

For further details, please refer to:

Adjust communication settings for the on-premises data gateway | Microsoft Learn
Azure updates | Microsoft Azure
 

If you encounter any authentication issues related to TLS while using Power BI, I suggest ensuring that both your environment and client are configured to use TLS 1.2 for optimal compatibility.

 

Below are responses to similar queries that I hope you find helpful:

 Re: Does PowerBI support TLS 1.3? - Microsoft Fabric Community
Solved: TLS version of powerBI desktop - Microsoft Fabric Community

Of course, if you have any new discoveries or questions, please feel free to get in touch with us.
 

Best Regards,

Leroy Lu

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

View solution in original post

6 REPLIES 6
rgouette
Frequent Visitor

"If want to connect from Power BI to a REST API that uses OAuth2 authentication then you need to build a custom connector. You can find documentation on how to implement an OAuth2 flow in a custom connector here."

from:
https://blog.crossjoin.co.uk/2021/08/29/connecting-to-rest-apis-with-oauth2-authentication-in-power-...

Hi, @rgouette 

Thank you for your contribution. If there are any new developments, we welcome you to share them with us.
If my response has been helpful, I would appreciate it if you could consider accepting it as a solution. This would assist other community members with similar queries in finding the answer more quickly.

vlinyulumsft_0-1731982873508.png
Of course, if you have any new discoveries or questions, please feel free to get in touch with us.
 

Best Regards,

Leroy Lu

 

rgouette
Frequent Visitor

Question: I'm seeing in places online that TLS 1.3 may not be compatible with PowerBi as far as authenticating..
Thoughts?

Thanks,
Rich

Hi, @rgouette 

Thank you for your swift response.

 

You are correct, which is why I recommend using version 1.2. There has indeed been some discussion regarding the compatibility of Power BI with TLS 1.3. According to the latest information, Power BI primarily supports TLS 1.2, while the support for TLS 1.3 remains unclear.

 

For further details, please refer to:

Adjust communication settings for the on-premises data gateway | Microsoft Learn
Azure updates | Microsoft Azure
 

If you encounter any authentication issues related to TLS while using Power BI, I suggest ensuring that both your environment and client are configured to use TLS 1.2 for optimal compatibility.

 

Below are responses to similar queries that I hope you find helpful:

 Re: Does PowerBI support TLS 1.3? - Microsoft Fabric Community
Solved: TLS version of powerBI desktop - Microsoft Fabric Community

Of course, if you have any new discoveries or questions, please feel free to get in touch with us.
 

Best Regards,

Leroy Lu

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

rgouette
Frequent Visitor

I just discovered the Custom Connector, which allowed me to gain access to  a number of things such as Functions, Gateways, Workspaces etc.. So far don't see my teams workspace, but I'll keep at it

Hi, @rgouette 

Thank you for sharing the issues you’ve encountered with us and for keeping us updated on your progress. Regarding your concerns, you might try the following steps:

 

1.Firstly, ensure that Power BI is using a supported TLS version (such as TLS 1.2).

Below are relevant screenshots from the documentation:

vlinyulumsft_0-1731467045282.png

For further details, please refer to:

Deprecating TLS 1.0 and 1.1 support in Power BI | Microsoft Power BI Blog | Microsoft Power BI
 

2.Secondly, if the API uses a self-signed certificate, Power BI may not be able to verify it.

You could try disabling the relevant settings in the Desktop application:

vlinyulumsft_1-1731467045283.png

For further details, please refer to:

Certificate revocation check, Power BI Desktop - Power BI | Microsoft Learn

 

3.Finally, here’s a link to similar issues that others have faced, which I hope will be helpful to you:

Solved: Power BI Desktop & Self-signed certificates - Microsoft Fabric Community

 
Of course, if you have any new discoveries or questions, please feel free to get in touch with us.
 

Best Regards,

Leroy Lu

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

Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!

Dec Fabric Community Survey

We want your feedback!

Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.

ArunFabCon

Microsoft Fabric Community Conference 2025

Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.

December 2024

A Year in Review - December 2024

Find out what content was popular in the Fabric community during 2024.