You are configuring a new Azure Function App that must retrieve secrets from Azure Key Vault. According to your organization's security policy, you must ensure that no credentials, tokens, or connection strings are stored directly in the Function App's configuration settings or code. Which Azure feature should you enable for the Function App to authenticate and gain access to the Key Vault?
- AA user-assigned managed identity assigned directly to the Key Vault resource
- BA Key Vault reference configured in the application settings without configuring access policies or roles
- A system-assigned managed identity for the Function AppAnswer
- DA Shared Access Signature (SAS) token with full read and write scopes stored in the configuration settings
Answer
A system-assigned managed identity for the Function App
Enabling a system-assigned managed identity creates a security principal in Microsoft Entra ID that is uniquely tied to the Azure Function App. The Function App can use this identity to authenticate to Key Vault and other Azure services without needing to store or manage credentials in settings or code.
Step-by-Step Solution
Key Concept
Configuring managed identities for Azure Functions to secure resource access
Estimated Time:1m 0s