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

[elton1]

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.

[thomas_lok]

Really need this! Otherwise no dashboard or report with the text analyses from the Cognitive services!

[geoff_richardso]

This is pretty terrible. Has anyone got a workaround to make it work in the Power BI Service?

[hieulatrung]

This is indeed required to fix urgently. Please fix it !!!

[fyodor]

Hi We have the same problem. We are using Web data source with authorization header and it works in PowerBI desktop version, however it doesn't work in PowerBI web (app.powerbi.com)

[sebastien_Roche]

This feature is really missing in power bi service. It does not allows us to publish and Schedule reports using API such as Microsoft cognitive services.

[jklassen]

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.

[benjamin_j_ford]

We also need this fixed urgently.

[michael49]

'+1, please fix this

[pbiideas1]

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

[Rusty_M]

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/