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
Custom visuals: allow same-tab navigation & reduce confirm-navigation friction for trusted links
Description: Custom visuals (e.g. Deneb) that trigger navigation via href currently have two limitations that create friction for legitimate, author-controlled use cases: Links always open in a ne...AlexSenEON49 minutes agoNew MemberNew5Views0likes0CommentsSeparate 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 ...ewarstdhyjugkhi1 hour agoMicrosoft EmployeeNew19Views8likes0CommentsSupport 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...WorkFull223 hours agoAdvocate INew31Views1like1Comment