Forum Discussion
New limits in Power BI Data Flows
To whom it may concern,
I would like to make a complaint regarding the new measure implemented by Microsoft, in which the update hours of Data Flows per user are limited. I find it outrageous and quite mean to make this kind of change when there are companies that already have their models set up, based on conditions that have existed for years. These limits (8 hours of updates per user) force us to pay for premium areas and accounts for hundreds of workers, a measure that takes advantage of users and forces us to buy something that we did not know we would have to change at the beginning. I find it outrageous and a reason for us to look for alternatives to this company. Totally disappointed.
Hi SJover,
Thank you for reaching out to the Microsoft Community Forum.
We are sorry for the inconvenience. I can completely understand why this feels frustrating. Many companies built their Dataflow and refresh setup years ago based on the limits and licensing model that existed at the time, so changes like this can have a real operational and financial impact later on. Microsoft does document the refresh and shared capacity limitations in their official docs and a lot of the larger-scale refresh capabilities are now tied to Premium/Fabric capacities. But from a customer perspective, it’s understandable that teams feel disappointed when an existing solution suddenly requires redesign changes or additional licensing costs just to continue operating at the same scale.
Below are the documents for your reference:
Dataflows Considerations and Limitations (legacy) - Power BI | Microsoft Learn
Data refresh in Power BI - Power BI | Microsoft Learn
Premium features of dataflows (legacy) - Power BI | Microsoft Learn
Semantic model modes in the Power BI service - Power BI | Microsoft Learn
Thank you.
3 Replies
v-sgandrathiCommunity Support
Hi SJover,
Thank you for reaching out to the Microsoft Community Forum.
We are sorry for the inconvenience. I can completely understand why this feels frustrating. Many companies built their Dataflow and refresh setup years ago based on the limits and licensing model that existed at the time, so changes like this can have a real operational and financial impact later on. Microsoft does document the refresh and shared capacity limitations in their official docs and a lot of the larger-scale refresh capabilities are now tied to Premium/Fabric capacities. But from a customer perspective, it’s understandable that teams feel disappointed when an existing solution suddenly requires redesign changes or additional licensing costs just to continue operating at the same scale.
Below are the documents for your reference:
Dataflows Considerations and Limitations (legacy) - Power BI | Microsoft Learn
Data refresh in Power BI - Power BI | Microsoft Learn
Premium features of dataflows (legacy) - Power BI | Microsoft Learn
Semantic model modes in the Power BI service - Power BI | Microsoft Learn
Thank you.- v-sgandrathi
Hi SJover,
I wanted to follow up on our previous suggestions regarding the issue. We would love to hear back from you to ensure we can assist you further.
Thank you.
- v-sgandrathi
Hi SJover,
Following up to check whether you got a chance to review the suggestions given. If the issue still persists please let us know. Glad to help.
Thank you.