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
Get Secret from Azure Key Vault using Fabric Workspace Identity
Users can access key vault secrets using notebookutils.credentials.getSecret. This is based purely on the user's access (or object owner's access, if the notebook is being run in a pipeline). In larg...sean_cochran10 minutes agoResolver INew3.2KViews14likes4CommentsPer-visual Data Freshness Badge with configurable staleness alerts
Problem: Report consumers can’t tell whether the data behind a specific visual is current. Page-level “last refreshed” workarounds ignore that different tables refresh on different schedules, which l...gopinathtk8 hours agoNew MemberNew1View0likes0CommentsNative Master Data Management Solution
Microsoft Fabric currently lacks a native Master Data Management (MDM) capability, creating a gap for organizations that need to manage and govern business-critical reference data such as customers, ...bradcoles9 hours agoRegular VisitorNew311Views1like4CommentsAllow Power BI subscriptions to use a no-reply sender instead of the subscription owner's mailbox
Following the migration to the new email delivery platform, subscription emails now appear to come from the subscription owner. This generates large volumes of Out of Office replies, auto-replies, an...tm8210 hours agoNew MemberNew90Views19likes3Comments