Salesforce Disabling TLS 1.0 -- Power BI Connections

[gbrown05]

Hi All,

Salesforce is disabling TLS 1.0 in early 2017. Power BI connects to Salesforce using TLS 1.0. Is there a plan to upgrade the Salesforce connector (Reports + Objects) to use TLS 1.1/1.2? Otherwise, my understanding is that the Salesforce connectors won't work after March 4, 2017.

On all of my Salesforce orgs' login logs, I see that all Power BI connections using TLS 1.0. However, I am also able to connect to a sandbox, which supposedly had TLS 1.0 disabled in June -- so it may be possible that the logs are incorrect and the connector actually uses TLS 1.1+?

Thanks!

[ReportRanger]

Hi @gbrown05 were you able to find a solution? As a workaround, maybe you can try to test your connection with a 3rd party connector, which pulls data directly from the SF objects API and has no issues when making the connection. I've tried windsor.ai, supermetrics and funnel.io. I stayed with windsor because it is much cheaper so just to let you know other options. In case you wonder, to make the connection first search for the Salesforce connector in the data sources list:

After that, just grant access to your Salesforce account using your credentials, then on preview and destination page you will see a preview of your Salesforce fields:

There just select the fields you need. It is also compatible with custom fields and custom objects, so you'll be able to export them through windsor.  Finally, just select PBI as your data destination and finally just copy and paste the url on PBI --> Get Data --> Web --> Paste the url. 

[jaschro]

This issue is marked as "Solved" but I can't tell what the solution is.  I have several PBI pbix files which I publish to Service and refresh from there.  How do I tell whether they're using TLS 1.0 or TLS 1.1? 

[gbrown05]

Hi jaschro,

I was also disappointed when it was marked solved because the solution isn't clear. Either there's a problem with Salesforce logs, or Power BI is still using TLS 1.0. The reason I don't think it's the latter is because I can connect to an org that has TLS 1.0 disabled. Still, it would be helpful if folks from Microsoft or Salesforce could jump in to clarify why connections from Power BI show up as using TLS 1.0 in all the logs.

I just reopened this question.

George

[jaschro]

Agreed.  In my case, I admit that I can't even spell TLS.  I certainly don't know what it means or what to do about it.  From the prior statements in this thread, it seems like the TLS issue will take care of itself with Salesforce.  But I'm not sure if that's actually true.  And I certainly don't know how to tell which I'm using.

[Anonymous]

Hi @gbrown05,

As stated in this blog, when Salesforce disable TLS 1.0, users who use Connect for Office are strongly encouraged to transition to Microsoft Power BI as an alternative. It indicates that Power BI supports to connect to Salesforce using TLS 1.1.

In addition, according to the above blog, as of June 25 2016, Sandbox instances no longer allow for TLS 1.0 access, and in March 2017, production will no longer allow for TLS 1.0 access. Thus, if you connect to Production org, it still use TLS 1.0 now.

Thanks,
Lydia Zhang

[gbrown05]

Thanks for your response, Lydia! I guess I am just confused by the (sandbox) logs showing TLS 1.0 for Power BI logins, even in sandboxes that no longer accept requests over TLS 1.0.

Looks like everything should be fine from Power BI.