Forum Discussion
Power BI Service Web Connector Issue
- Anonymous1 year ago
Hi the below solutions didnt help . I actually worked with my network team and they are using a third party application that had for some reason put one of these urls in the blocklists and hence i was not able to access the URL from the subnet . The issue is resolved now after the IT / Network team inspected the traffic and whitelisted it since . However i thank all for promptly coming up with suggestions .
Hi Anonymous,
Thank you for reaching out to the Microsoft Fabric Forum Community.
The issue arises because Power BI Desktop and Power BI Service handle web connections differently, especially when it comes to custom headers like the Authorization: Bearer token. While Power BI Desktop allows these headers in Web.Contents() without issue, the Power BI Service does not retain or honor custom headers unless they are part of a supported pattern, such as within a custom data connector.
The specific error you're encountering typically indicates that the Service-side request is missing required authentication headers, causing the API to reject the connection. A recommended and scalable solution is to build a custom Power Query connector which encapsulates the authentication logic securely and works seamlessly with the on-premises gateway.
Make sure the API endpoint supports TLS 1.2, as Power BI Service enforces it and any mismatches can also lead to abrupt connection closures. If the API supports query parameter–based token authentication, that could serve as a short-term workaround, though it comes with security trade-offs.
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you.