Power BI Embedded cannot acquire a token (working nice before day 26). You are using TLS version 1.0

[gluizqueiroz]

I have a Power BI Embedded using C# lib with AD, working nice for many years, but before yesterday, the embedded stop working and I receive the following message:

{"error":"invalid_request","error_description":"AADSTS1002016: You are using TLS version 1.0, 1.1 and/or 3DES cipher which are deprecated to improve the security posture of Azure AD. Your TenantID is: eba41816-__________________. Please refer to https://go.microsoft.com/fwlink/?linkid=2161187 and conduct needed actions to remediate the issue. For further questions, please contact your administrator.\r\nTrace ID: d090b1b8-59b4-4ea4-be41-208f71caa500\r\nCorrelation ID: 72af2747-0d23-484e-b625-18c95882b7e3\r\nTimestamp: 2022-07-28 13:31:48Z","error_codes":[1002016],"timestamp":"2022-07-28 13:31:48Z","trace_id":"d090b1b8-59b4-4ea4-be41-208f71caa500","correlation_id":"72af2747-0d23-484e-b625-18c95882b7e3"}

I have tried to install some updates in my .NET software, some Windows Updates and nothing works.
The craziest thing about this is:

If I made the same request using Postman, it works properly and I can receive the token. 
And the plus craziest thing is, if I use another cliend_id, username and password in my C# application, it works nice, so, I dont know if the problem is my C# application or my account or my app registered in Active Directory.

Problem in C# application? = If I use a different client_id, username and password, it works!
Problem with account? = I can receive the token in Postman
Problem with app registered on AD? = I can receive the token in Postman
Problem with my tenant? = I have some another Power BI Embedded working nice, using C# lib others using Javascript lib.

So, I dont know what I should do now, its kinda confusing.

[DizzyDan77]

Had the exact same issue for a legacy application running on .Net Framework 4.0.

Despite everything else around this application supporting TLS 1.2 - we had to upgrade to .Net Framework 4.6 in order for the OAuth authentication between the server and Azure (for Power BI EC) to actually send as TLS 1.2.

In our situation - only when we upgraded to 4.6 was it able to authenticate using TLS 1.2.

[Anonymous]

Hi @gluizqueiroz ,

Based on the error message, it appears that the problem is caused by TLS1.0... As mentioned in the blog post: As of June 2020, Power BI will begin deprecating TLS 1.0 and 1.1 in worldwide environments for commercial customers and in GCC environments for GCC customers. for GCC customers.

You can try to upgrade TLS to TLS1.2+ by referring to the blog link below, and then see if you can get the token properly.

Enable support for TLS 1.2 in your environment for Azure AD TLS 1.1 and 1.0 deprecation

Upgrade the TLS version of your Power BI application to TLS 1.2

Best Regards