This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
We have Power BI embedded reports in a .NET web application running on framework 4.5.2 and with Power BI API 2.4
Since yesterday those reports start to failed. The error is in the authentication process with the API, specifically on this line:
var authenticationResult = await authenticationContext.AcquireTokenAsync(ResourceUrl, ClientId, credential);
The error is not giving much information: "The underlying connection was closed: An unexpected error occurred on a send."
I tried to setup a project with the new API v.3.11.1 and the exact same code is running without any issues, the problem is that we will need to updagrade the whole project to framework 4.7.2 and that could take a considerable effort. Are you aware of any possible workaround to keep using v2 until we succesfully upgrade the project?
Hello @carlosmunoz ,
The issue is not caused by the new API v.3.11.1. In the next release of the framework the SecurityProtocolType enumerator got extended with the newer Tls protocols, so if your application can use th 4.5 version you can also use Tls11 and Tls12. So if you are on .net framework 4.5,change the SecurityProtocol .
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls |
SecurityProtocolType.Tls11 |
SecurityProtocolType.Tls12;
Best Regards
Check out the May 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |