Please make it possible to run a notebook as the Workspace Identity, instead of running as a user identity.
This means the notebook (and the notebook's security context, i.e. the notebook's authentication to data connections) will not depend on any single user but use the Workspace Identity instead.
3 Comments
- blhart216Regular VisitorThis is a must have!
- BIDannyFrequent VisitorYou just need to take your notebook and make a .py file out of it and turn it into a Spark Job Definition. Those run as the Workspace Identity.
- PeterDaniels
Advocate III
Hoping this would be the answer to using Workspace Identity to access Azure Key Vault in notebooks simply and securely
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 IIINew185Views0likes2CommentsMake 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