Forum Discussion
Managed Identities Security
Hi Marshyp
Thanks for following up.
You are exactly right—currently, when creating Azure Key Vault references OAuth2 (user-delegated) is the only supported Authentication Method.
My best suggestion is to create the references to your Key Vaults using a service account and share it with security groups. This keeps maintenance to a minimum, following the same governance approach as personal cloud connections.
Alternatively, you can suggest other auth methods (like Managed Identity) for Key Vault references here: Fabric Ideas.
I do suspect the MS team is already looking into adding more auth methods, though!
Br,
Asger
Resolver IHi Marshyp (Phil)
Just so I get your question right, you are trying to create a cloud connection to e.g. a storage account and are setting the authentication method as Service Principal and then using the Azure Keyvault setting for fethcing the Service Principal Secret?
Br
Asger
Hey AsgerLB,
Apologies for not being clear, but you are correct - When we create a cloud connection and set the authentication method to Service Principle, we cannot fetch the secrets from Key Vault as the Service Principle, but only as the user making the connection (via OAuth2). There doesn't appear to be any option to use Service Principle, Managed Identity, etc.
- AsgerLB
Hi Marshyp
Thanks for following up.
You are exactly right—currently, when creating Azure Key Vault references OAuth2 (user-delegated) is the only supported Authentication Method.
My best suggestion is to create the references to your Key Vaults using a service account and share it with security groups. This keeps maintenance to a minimum, following the same governance approach as personal cloud connections.
Alternatively, you can suggest other auth methods (like Managed Identity) for Key Vault references here: Fabric Ideas.
I do suspect the MS team is already looking into adding more auth methods, though!
Br,
Asger
