One of my clients is using Key Vault to retrieve secrets, which is a good thing.
They also want to move to the integrated options, removing the need for them to use a private link that takes time to become available and slows down development and data processing. The main reason they can't do this is because Key Vault doesn't support RBAC yet, it's only ACL authentication. ACL is something the good people of Azure are advising against.
Please enable RBAC support for this feature, using the Fabric workspace identity 🙂
No CommentsBe the first to comment
Recent ideas
Allow 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 ...PeterDaniels2 hours agoAdvocate IIINew177Views0likes2CommentsMake 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...TeemuMultanen3 hours agoAdvocate INew292Views47likes2CommentsSupport Encrypted Sensitivity-Labeled Excel Files in Power Query
Description Currently, Power Query Online and Power Query in Excel are unable to access encrypted Excel files. Excel files with sensitivity types other than Public or Non-Business can be encrypted a...ewarstdhyjugkhi3 hours agoMicrosoft EmployeeNew17Views6likes0Comments