TLS 1.2 or newer needed for this#6428
Conversation
I just solved the case where this functionality didn't work because TLS 1.0 was used. More info here: https://powerbi.microsoft.com/en-us/blog/deprecating-tls-1-0-and-1-1-support-in-power-bi/ So to make it work Framework 4.7 or newer needed, or, if framework 4.6 installed, change the registry according to this: https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls#systemdefaulttlsversions
|
@eldarku : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
Note that publishing in this repository is suspended until Tuesday, May 25. Merging will resume Tuesday. Authors can still review and sign off on PRs in the interim. Thanks. |
maggiesMSFT
left a comment
There was a problem hiding this comment.
please accept my edit, then merge.
|
#sign-off |
Hi @maggiesMSFT - Merging is paused in this repo until Tuesday, May 25. I can do it on Tuesday; OK? |
|
Hi, @ktoliver -- OK, thanks! |
Co-authored-by: Maggie Sparkman <maggies@microsoft.com>
|
@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
I just solved the case where this functionality didn't work because TLS 1.0 was used.
More info here:
https://powerbi.microsoft.com/en-us/blog/deprecating-tls-1-0-and-1-1-support-in-power-bi/
So to make it work Framework 4.7 or newer needed, or, if framework 4.6 installed, change the registry according to this:
https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls#systemdefaulttlsversions