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

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