Reply to Email

Original: Action required: Transition Azure Key Vault access policies to Azure RBAC or configure Azure Key Vault to explicitly use access policies

|
On 2026-02-05 22:08:55, Microsoft Azure wrote:
Microsoft Azure header logo
Transition to Azure RBAC
========================

You’re receiving this email because you’re using Azure Key Vault. 

On 27 February 2027, all Azure Key Vault API versions prior to 2026-02-01 will be retired.

Azure Key Vault API version 2026-02-01—releasing in February 2026—introduces an important security update:Azure role-based access control (RBAC) will be the default access control model for all newly created vaults.Existing key vaults will continue using their current access control model. Azure portal behavior will remain unchanged. 

If you’re using legacy access policies for new and existing vaults, we recommendmigrating to Azure RBACbefore transitioning to API version 2026-02-01. To learn why Azure RBAC is critical to security, read our blog.

If you want to continue using legacy access policies for new key vault creation after transitioning to API version 2026-02-01, you'll need to explicitly configure access policies as the access