Guidance for Azure Key Vault — securely storing and managing secrets, keys, and certificates with RBAC, network isolation, managed identity access, soft delete / purge protection, and rotation. Covers when to use standard Key Vault vs Managed HSM (FIPS 140-3 Level 3), one-vault-per-app blast radius principle, and Key Vault references in App Service / Functions. WHEN: Azure Key Vault, store secrets, manage certificates, encryption keys, secret rotation, Key Vault RBAC, purge protection, soft delete, private endpoint Key Vault, managed identity access secrets, Managed HSM, Key Vault references, BYOK CMK. DO NOT USE for certificate authority design (use pki-design), entra app credentials only (use entra-id), or PaaS networking topology (use azure-network-security-design).
$npx -y skills add kilo-org/kilo-marketplace --skill azure-key-vaultInstalls into the current project.
Run `npx skills use "https://github.com/kilo-org/kilo-marketplace" --skill "kilo-org/kilo-marketplace/azure-key-vault"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/kilo-org/kilo-marketplace" that are relevant to the current task. Run `npx skills add "https://github.com/kilo-org/kilo-marketplace"` and select the relevant skills, then follow their instructions.