Most Web.Contents() custom connectors stopped working in Pro workspaces

[ParkerOhno]

I have several dataflows that use a custom connector to a datasource, in various forms over 10-15 dataflows. In one workflow they are still up and running, however, in all the others any use of Web.Contents with headers/etc causes it to not refresh and indicates that I must use premium to refresh it.

I've isolated this to it still occuring in a single query dataflow with all code past a single API code being removed.

Ideas?

[v-prasare]

@ParkerOhno as we haven’t heard back from you, we wanted to kindly follow up to check if the solution we have provided for your issue worked? or let us know if you need any further assistance here?

Your feedback is important to us, Looking forward to your response. 

Thanks,

Prashanth Are

MS Fabric community support.

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query.

[v-prasare]

@ParkerOhno, as we haven’t heard back from you, we wanted to kindly follow up to check if the solution we have provided for your issue worked? or let us know if you need any further assistance here?

Your feedback is important to us, Looking forward to your response. 

Thanks,

Prashanth Are

MS Fabric community support.

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query.

[v-prasare]

Hi @ParkerOhno 

Hope your doing well.

@Poojara_D12  thanks for your prompt answer

@ParkerOhno , as we haven’t heard back from you, we wanted to kindly follow up to check if the solution we have provided for your issue worked? or let us know if you need any further assistance here?

Your feedback is important to us, Looking forward to your response. 

Thanks,

Prashanth Are

MS Fabric community support.

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query.

[Poojara_D12]

Hi @ParkerOhno 

The issue arises because Power BI limits the use of Web.Contents with custom headers or complex configurations in non-premium workspaces, requiring a Premium license for such refreshes. Here's a summary:

Why It Happens

1. Authentication Complexity: Custom headers or advanced API interactions aren't fully supported in non-premium workspaces.
2. Premium Dependency: Microsoft restricts advanced API operations to Premium workspaces.
3. Custom Connector Issues: Inconsistent handling of authentication or queries in the custom connector.

Solutions

1. Test in a Premium Workspace: Move failing dataflows to a Premium or PPU workspace.
2. Simplify Web.Contents: Use a basic API call without custom headers to identify the issue.
3. Check Connector Setup: Ensure your custom connector handles authentication correctly.
4. Use a Gateway: Connect dataflows via an on-premises gateway to bypass some restrictions.

Workarounds

• Migrate API logic to Power BI Desktop and publish the dataset.
• Use Azure Data Factory or similar to stage API data, then connect dataflows to the staged source.

Did I answer your question? Mark my post as a solution, this will help others!
If my response(s) assisted you in any way, don't forget to drop me a "Kudos" 🙂

Kind Regards,
Poojara
Data Analyst | MSBI Developer | Power BI Consultant
Consider Subscribing my YouTube for Beginners/Advance Concepts: https://youtube.com/@biconcepts?si=04iw9SYI2HN80HKS