Forum Discussion
Dataset refresh via Power Automate Flow - clarifications
Hi mollycat ,
Unfortunately, there’s no sneaky way around this one in Premium capacity, anything that refreshes your dataset via Power Automate (or any other API) does count toward the 48-per-day limit for that dataset, even if you trigger it manually with a button inside the report. The only refreshes that don’t count are when you (or someone with permission) click REFRESH NOW in the Power BI Service. The good news is you can add a Power Automate button in the report so end users can kick off a refresh themselves it just means each click will still eat into that 48-refresh daily quota. If you really need more than 48 automated/API refreshes a day, the only real workaround today is to go through the XMLA endpoint, which doesn’t have the same cap.
More details here in Microsoft’s official documentation: Data refresh in Power BI - Power BI | Microsoft Learn
Hope that clears things up. If the above solution works for you, please accept it as the solution so that other community members with similar issues can benefit.
Regards,
Akhil.
Hi mollycat ,
That screenshot says it all really appreciate you sharing it! Seeing all those Data Factory refreshes running every couple of minutes and completing successfully is a great confirmation that the pipeline approach works differently than the standard refresh mechanism.
I’m with you on the thought that this might be a Preview behavior but if Microsoft decides to keep it this way when it goes GA, it could completely change the game for scenarios where frequent refresh is critical.
One thing I’d suggest (just to be safe) is keeping an eye on capacity utilization in the Fabric Admin metrics, especially if you plan to keep those 2-minute intervals running in production. Even if there’s no hard refresh limit here, resource consumption will still matter.
Thanks again for circling back with the details and proof this is going to be super helpful for others.
Regards,
Akhil.