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
Convert Standard Lakehouse to Schema Based Lakehouse
When Schema based Fabric Lakehouse's come out of Public Preview, it would be AMAZING and gamechanging to be able to convert a standard lakehouse into a Schema based lakehouse. Right now we organ...dbrugger1 hour agoRegular VisitorNew380Views2likes2CommentsDeployment rules can be used on Dataflows Gen2 (CI/CD)
Hi, We currently have a lot of dataflows gen1. We use 3 environments in our deployment pipelines (DEV - TST - PRD). Our company is investigating to upgrade our dataflows from gen1 to gen2. ...DonHoog1 hour agoAdvocate INeed Clarification491Views7likes2CommentsEnable Managed Identity Authentication for Event Hubs in Event Stream Inputs
Currently, EventStream supports adding Event Hub as an input source using the SAS Key authentication method. Please add support for Managed Identity–based authentication so that EventStream can align...VChimbili1 hour agoMicrosoft EmployeePlanned1.3KViews12likes9Commentsnotebookutils.credentials.getToken: Add more audience keys
Currently, only 4 audiences are listed in the docs: Audience key Resource Use case storage Azure Storage Access ADLS Gen2 and Blob Storage pbi Power BI Call Power BI and Fabric RES...frithjof_v4 hours agoCommunity ChampionNew14Views0likes0Comments