DataFlow Gen2 cannot be triggered using a service principal which is crucial and necessary for companies using the officially supported and joined project fabric-cicd which is a library to deploy workspace items via the official REST API. Because Microsoft did disable deployment using normal user accounts, recommending Service Principals for that, everything is deployed and therefore owned/modified by the same Service Principal. This leads to the obvious problem that pipelines trying to call/refresh DataFlow Gen2 will faile because refresh via SP is not supported.
This is a very frustrating situation to be in because normal user deployment was disabled without thinking about the crippling of functionality like this.
No CommentsBe the first to comment
Recent ideas
Separate Download and Publish Permissions for Power BI Workspaces
Idea / Feature Request Introduce more granular permissions in Power BI to independently control report download and report publishing permissions at the workspace level. Business Scenario We have ...ewarstdhyjugkhi38 minutes agoMicrosoft EmployeeNew14Views7likes0CommentsSupport Fabric SQL Database with workspace-level inbound Private Link
Fabric SQL Database supports tenant-level Private Link but not workspace-level Private Link. Securing a small number of databases therefore requires enabling Private Link across the entire tenant, in...WorkFull222 hours agoAdvocate INew29Views1like1CommentPaste values in slicers for hierarchy data
Hierarchical slicers are widely used in enterprise reports (for example Product RCN > SKU Key, Region > Country > City, or GPP > Division > RCN > SKU). Users often need to bulk-filter by pasting valu...eddieisking20003 hours agoFrequent VisitorNew0Views0likes0Comments