This chapter covers Azure Key Vault for storing secrets. AZ-900 tests under 2.5.
Jump to a section
A simple way to picture Azure Key Vault
A physical vault keeps valuables secure. Azure Key Vault keeps digital secrets (passwords, API keys, certificates) secure and accessible only to authorized applications.
Key Vault stores secrets, keys, and certificates, controlling access and enabling secure retrieval by applications. It's the place to store sensitive information instead of hardcoding it in applications.
Create a Key Vault
A vault is created in an Azure region.
Store secrets
API keys, passwords, certificates are stored in the vault.
Grant access
Applications are granted permission to retrieve specific secrets.
Applications use secrets
Apps retrieve secrets from the vault as needed, not from code.
An application retrieves its database password from Key Vault at runtime instead of storing it in code, improving security.
Objective 2.5 expects understanding of Key Vault as a secrets storage solution.
Key Vault stores secrets securely.
Controls access to sensitive information.
Applications retrieve secrets at runtime, not from code.
It's a service for storing secrets, keys, and certificates securely, controlling access and enabling secure retrieval by applications.
You've just covered Azure Key Vault — now see how well it sticks with free AZ-900 practice questions. Full explanations included, no account needed.
Done with this chapter?