Tag Key Vault

Using RBAC Permission Model for Azure Key Vault

This post discusses the Role-Based Access Control (RBAC) model for Azure Key Vault, which Microsoft recommends to strengthen security by clearly separating security responsibilities from administrative tasks. RBAC ensures that users holding 'Contributor' roles cannot grant themselves unauthorized access, and offers advantages such as a unified access approach across Azure services. I also provide a detailed table showing the necessary IAM roles required for accessing keys, secrets, and certificates in Azure Key Vault, concluding with my opinion on transitioning existing vaults.

[Azure] Key Vault Access Troubleshooting 101: Access Policy and Network

This post discusses the two common root causes that block access to Azure Key Vault: Access Policy and Network. In my experience, 90% of Key Vault access issues can be resolved by addressing these two factors. Simply put, to determine if an identity (user or application) can retrieve the stored data, the Key Vault checks: (1) if related permissions have been granted to the identity; and (2) if the source network of the identity (e.g., its public IP or VNet) has been allowed/whitelisted on the Key Vault. Two use cases from the perspective of an individual user and a web app will be illustrated to explain how the authorization works. We then introduce a tool (MSI Validator) that is helpful for advanced troubleshooting.