Today, only Oauth 2.0 (user account) is supported as authentication option when setting up an Azure Key Vault reference.
Please add support for
- Workspace Identity
- Service principal
- User assigned managed identity
8 Comments
- This is a good idea, Service principal or user assigned managed identity will be a great help. Workspace identity will be difficult i think because it is a global key vault reference and not workspace specific.
- We REALLY need a way to set up Azure Key Vault references without using a regular user/member account. Please. WI would be even better, but a service principal/app-reg would be a great start.
- Without this organizations are not feeling that keyvault references are the answer and are turning more towards notebooks and calling keyvault via api’s. Microsoft would benefit from a larger adoption of the feature in a faster manner and could get better feedback from partners.
- Anyone at Microsoft, can you please solve this basic problem before adding more bells and whistles?
- Upvoting for different authentication methods as my token randomly expired earlier this week and broke a lot of pipelines that had connections using secrets from this key vault reference.
