Dataset With Missing Credentials Error

[ruisoaress]

I recently started using PowerBI and my goal is to generate a report with the data I want to obtain through my backend. In other words, I want to connect my backend's API (http://localhost:5012/FaturacaoAnual/evolucao-fauracao) to PowerBI. That said, I'm having great difficulty scheduling updates since I get the following error:

Data source error: Scheduled refresh is disabled because there is at least one data source with missing credentials. To start the refresh again, go to the settings page for this dataset and enter the credentials for all data sources. Then, re-enable scheduled refresh.

Cluster URI: WABI-NORTH-EUROPE-redirect.analysis.windows.net

Activity ID: a52196f4-0a28-451d-b729-8d8473c31dde

Request ID: bf03823f-e38e-8596-6c3b-4ba62f078386

Time: 2025-03-23 ​​17:38:41Z

I've looked a lot and haven't been able to find a solution.

[v-mdharahman]

Hi @ruisoaress,

Thanks for reaching out to the Microsoft fabric community forum.

It looks like you are facing issues when using scheduled refresh for the data you are getting through backend API. As @lbendlin and @AmiraBedh already responded to your query, please go through it and mark the helpful reply as solution.

I would also take a moment to thank @lbendlin and @AmiraBedh, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.

If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

Best Regards,
Hammad.
Community Support Team

If this post helps then please mark it as a solution, so that other members find it more quickly.

Thank you.

[v-mdharahman]

Hi @ruisoaress,

As we haven’t heard back from you, so just following up to our previous message. I'd like to confirm if you've successfully resolved this issue or if you need further help.

If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. If you find a reply particularly helpful to you, you can also mark it as a solution.

If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.
Thank you for your patience and look forward to hearing from you.

[v-mdharahman]

Hi @ruisoaress,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution so that other community members can find it easily.

Thank you.

[v-mdharahman]

Hi @ruisoaress,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[AmiraBedh]

If your API runs on a local server (like your dev machine), you’ll need to install the On-Premises Data Gateway.

You can download from here: https://powerbi.microsoft.com/en-us/gateway/ and install it on the machine where your API is running.

In Power BI Service, go to: Settings > Manage Gateways > Add Data Source.

Then add your API URL and choose authentication method (Anonymous, Basic... depending on your API).

In Power BI Service: Settings > Datasets > Gateway Connection and assign the dataset to use the gateway and the registered data source.

 If you're using localhost, you may need to expose it as http://<your-machine-name>:5012/... in the gateway instead of using localhost, as localhost from the Power BI Service refers to the gateway machine.

If you want to avoid using a gateway, you need to host your backend API on a publicly accessible domain (Azure App Service, Render, Vercel).

Then, in Power BI, update the data source URL to the public one.

In Power BI Service, go to Settings > Datasets > Data source credentials and set them (Anonymous, Basic Auth, or OAuth depending on your API). Scheduled refresh should now work.

[lbendlin]

You cannot use "localhost".  Use the machine's FQDN and make sure the gateway cluster members have free line of sight to the machine and the port.