Skip to main content

Power BI

Needs Votes

Bypass test connection/Ignore failure for Web Sources that depend on authorization header

Vote (144) Share
Elton Sequeira's profile image

Elton Sequeira on 09 May 2017 00:55:48

The power BI service runs a test connection on Web API data sources before pulling data. However for Web Sources whose response depends on a required authorization header fail to authenticate in the power bi service while setting up a scheduled refresh. The source is accessed using Web.Contents and by passing the URL, Relative path and authorization header. This works perfectly fine in Power BI desktop since it executes the GET request along with the authorization header without a test connection. If the same could be done in power bi service by either bypassing the test connection or ignoring failures then a schedule refresh could be setup.

Comments (25)
Elton Sequeira's profile image Profile Picture

37a0f56d 0c6c-4852-9d0d-721823e14363 on 05 Jul 2020 23:39:31

RE: Bypass test connection/Ignore failure for Web Sources that depend on authorization header

This really needs to be fixed. Come on Power BI team!

Elton Sequeira's profile image Profile Picture

1cd10e42 95c0-4a19-b192-8d3e0d23df62 on 05 Jul 2020 23:35:39

RE: Bypass test connection/Ignore failure for Web Sources that depend on authorization header

I have exactly the same problem. Ive implemented Text Analytics and it works fine in Desktop. However, when you go into Datasets Data Source Credentials you get Failed to update data source credentials: Web.Contents failed to get contents from 'https://westus.api.cognitive.microsoft.com/text/analytics/v2.0/keyPhrases' (404): Resource Not FoundHide details Not only does this need to be fixed but Help. What is the workaround?

Elton Sequeira's profile image Profile Picture

9735c3ee 11d9-400c-9187-d4b9bd2f416a on 05 Jul 2020 23:32:58

RE: Bypass test connection/Ignore failure for Web Sources that depend on authorization header

Really disappointed and really need it to be fixed

Elton Sequeira's profile image Profile Picture

26e98242 5715-4dfe-95ae-c05b49a64ecc on 05 Jul 2020 23:30:40

RE: Bypass test connection/Ignore failure for Web Sources that depend on authorization header

...and more than a year later it's still a persisting issue. WHY?! Can't be that hard to fix. It's already working in Power BI Desktop.

Elton Sequeira's profile image Profile Picture

0ccd982f 72d0-4f48-8a3f-6c2140018678 on 05 Jul 2020 23:28:37

RE: Bypass test connection/Ignore failure for Web Sources that depend on authorization header

Can this be fixed, please?

Elton Sequeira's profile image Profile Picture

1c46cd1d 4f87-4222-ad97-1eb188f1be95 on 05 Jul 2020 23:27:24

RE: Bypass test connection/Ignore failure for Web Sources that depend on authorization header

There is a way to "bypass" using the azure proxy but comes at a cost which is not ideal.... This is something that should just work.

https://blog.kloud.com.au/2018/07/23/use-anonymous-authentication-on-web-data-sources-with-a-api-key-in-url/

Elton Sequeira's profile image Profile Picture

a3309361 99be-ea11-a812-000d3a8ddfb2 on 05 Jul 2020 23:23:44

RE: Bypass test connection/Ignore failure for Web Sources that depend on authorization header

Has anyone found a work around for this extremely disappointing issue?

Elton Sequeira's profile image Profile Picture

1d37ae08 80a5-45ec-9e6e-006fb67822ee on 05 Jul 2020 23:22:36

RE: Bypass test connection/Ignore failure for Web Sources that depend on authorization header

'+1, please fix this

Elton Sequeira's profile image Profile Picture

78d6b51f 6aeb-4362-83d7-0a681a23c9e6 on 05 Jul 2020 23:21:12

RE: Bypass test connection/Ignore failure for Web Sources that depend on authorization header

We also need this fixed urgently.

Elton Sequeira's profile image Profile Picture

ce320311 8a99-4942-8278-992a8396d422 on 05 Jul 2020 23:20:45

RE: Bypass test connection/Ignore failure for Web Sources that depend on authorization header

Agree, that a fix for this is needed. I have tried to understand for months why reports created in Desktop using Web API data sources can be refreshed OK, but cannot be scheduled for refresh in PBI service. I finally came across this thread today, and hope that something can be done.