Fabric Key Vault Item (Native, fully SaaS Vault offering within a Tenant or Workspace)

[sean_ms]

Promoting the idea for Microsoft Fabric to develop a native SaaS Key Vault item. Currently, there are plans and limited existing integration with PaaS Azure Key Vault, however this is promoting a Hybrid architecture. To fully realize a SaaS workload, we need a Fabric Native item to allow for the secure storage and retrieval (native integration with other items, Pipelines, Notebooks,ect.) of Secrets and Certificates.

[frithjof_v]

Great idea. This is necessary because Fabric users typically don’t have permission to create their own Key Vaults in Azure. Creating a Key Vault requires Azure-level permissions, which many Fabric users don’t have. This creates a misalignment between Fabric and Azure: users can build data solutions in Fabric, but they must rely on external Azure administrators to provision and manage secrets. Instead, users should be able to create and manage a Key Vault directly within Fabric. The billing for secret operations should be handled through CUs, just like other Fabric workloads.

[LW07]

Using Oauth2 is standard for me as a data engineer using SSIS. But accessing anything Azure is locked down, so I have no method for secure storage. While I'm trying to develop and recreate SSIS pipelines this is a major blocker because I have to engage other people across multiple teams to arrange AKV and it's very low priority for those teams.