The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
I have a small REST API running as a service in Azure that I would like to use in the Power BI Service. It is protected by a Bearer Token that is provided as a header parameter in the query. The connection uses Anonymous credentials.
When I connect to this via Power BI Desktop, it works and I can retrieve the data. After publishing to the Power BI service, the data refresh fails. I can see the URLs in the connections, and the credentials are also set anonymously as I expected. However, in the connections view, these URLs are turning up in areas I did not expect, and consequently I think my reports are try to refresh from the wrong endpoint.
Why are the URLs appearing in both On-Premises Gateway and Cloud connections? What can I do to correct the situation? I realise I may not have included all information, but I am not sure what is needed to diagnose the problem. See image below (sensitive data redacted).
Thanks!
Solved! Go to Solution.
Hi @JasonBurdetts ,
The Power BI service has limitations on dynamic data sources, which can cause refresh failures. Ensure that your REST API URL is static and not dynamically generated.
Also, choose to skip authentication when the gateway creates the connection.
Hope it helps!
Best regards,
Community Support Team_ Scott Chang
If this post helps then please consider Accept it as the solution to help the other members find it more quickly.
Hi @JasonBurdetts ,
The Power BI service has limitations on dynamic data sources, which can cause refresh failures. Ensure that your REST API URL is static and not dynamically generated.
Also, choose to skip authentication when the gateway creates the connection.
Hope it helps!
Best regards,
Community Support Team_ Scott Chang
If this post helps then please consider Accept it as the solution to help the other members find it more quickly.
To clarify, I do not known why the two "Web" urls are appearing in the data gateway.