AshishChougala
Microsoft Employee
11 months agoStatus:
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. - BrubakerM
Advocate 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
Allow NotebookUtils getSecret() to authenticate with Workspace Identity
Current behavior In Microsoft Fabric, notebookutils.credentials.getSecret() authenticates against Azure Key Vault using the identity of the user who executes the notebook. This behavior appli...tmihara1 hour agoNew MemberNew16Views1like1CommentAllow us to rename fabric data agents published to m365
If we use deployment pipelines to promote fabric data agents between dev, test/UAT, and prod fabric workspaces, we need to keep the name of the fabric agent the same in each workspace. If we want to ...PeterDaniels8 hours agoAdvocate IIINew184Views0likes2CommentsMake workspace and item session persistence optional
Description The new persistent session behavior in Microsoft Fabric should be optional rather than forced. Currently, Fabric remembers the workspaces and items that were open in my previous session...TeemuMultanen9 hours agoAdvocate INew297Views47likes2Comments