What are the different ways to authenticate to Azure Key Vault?
[Note: As we migrate from MSDN, this question has been posted by an Azure Cloud Engineer as a frequently asked question]
Source: What are managed identities for Azure resources?
What are the different ways to authenticate to Azure Key Vault?
[Note: As we migrate from MSDN, this question has been posted by an Azure Cloud Engineer as a frequently asked question]
Source: What are managed identities for Azure resources?
There are three ways to authenticate to Azure Key Vault:
1. Managed Identities
Managed Identities are assigned to Azure resources which needs access to Azure Key Vault. This is the recommended approach as Azure automatically rotates the identity and app/service doesn’t have to manage the secret.
Refer to What are managed identities for Azure resources? to know more about managed identities.
2. Service Principal and Secret
You can use a Service Principal and a secret to access a key vault. However, not recommended as it is hard to automatically rotate the secret used to authenticate to Key Vault.
3. Service Principal and Certificate
You can use a Service Principal and associated certificates to access key vault. The application owner/developer is required to rotate the certificates.
Source: What are managed identities for Azure resources?
4 people are following this question.
Will Microsoft see my keys in Azure Key Vault?
What are Azure Key Vault's soft-delete and purge protection features?
What is the limit of number of key vaults per subscription?
What is the difference between a key and a secret in Azure Key Vault?
How do I decide whether to use Azure Key Vault or Azure Dedicated HSM?