I am really glad to see the preview of the new Task Flow feature. That said, in the age of Fabric (and even before), workspaces contain artifacts that support far more than just one task flow/proces...
treyu33
2 years agoRegular Visitor
I concur, it will be very important to be able to create multiple task flows per workspace.
Otherwise, people are going to be creating one workspace per task flow, which will create more workspaces than what is truly necessary, adding additional workspaces that you need to be governed.
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 INew299Views47likes2Comments