AshishChougala
Microsoft Employee
Microsoft EmployeeStatus:
New
Enable Seamless Dataflow Gen2 Refresh Across Users Without Ownership Transfer
Description
Currently, Dataflow Gen2 in Power BI does not allow refresh operations on flows targeting a Warehouse unless the user performing the refresh is the owner of the dataflow. Even users with full workspace permissions (Admin/Member) and Fabric capacity rights cannot refresh unless ownership is transferred.
This limitation creates operational challenges, especially in enterprise environments where multiple users manage refresh schedules. In contrast, when the destination is a Lakehouse, refresh works without requiring ownership transfer, which is the expected behavior.
Proposed Enhancement
- Allow any user with sufficient workspace and Fabric permissions to refresh Dataflow Gen2, regardless of ownership.
- Ensure consistent behavior between Lakehouse and Warehouse destinations.
- Optionally, introduce a service principal or delegated refresh capability for automation and enterprise scenarios.
2 Comments
- ToddChitt
Super User
My opinion, for what it's worth, is that object OWNERSHIP in Power BI and Fabric gets in the way of a LOT of stuff. The abject/artifact should be 'owned' by the Workspace, and NOT by any one single person or SPN inside the workspace. 
BrubakerMAdvocate I
"Optionally, introduce a service principal or delegated refresh capability for automation and enterprise scenarios." Service principal should not be optional. This is a requirement for enterprise automation.
Recent ideas
Visual header icon improvements: Options for permanent visibility on per-icon basis, weblinks etc.
Current problem: Visual header icons like the 'Help tooltip' icon are potentially incredibly useful, however they rarely pass muster for our needs as so many of our report owners/authors insist on th...
