Other Articles
- SQL Database – Enable Database Encryption
- SQL Databases – Enable Backup
- SQL Database – Monitor CPU Utilization
- SQL Database – Monitor IO Utilization
- SQL Database – Monitor Memory Utilization
- SQL Database – Protect From Direct Internet Traffic
- SQL Server – Enable SQL Defender
- SQL Server – Require Microsoft Entra-Only Authentication
- SQL Server – Block Public Firewall Rules
- SQL Server – Enable Auditing
- Storage Account – Enable Storage Encryption
- Storage Account – Disable Blob Public Access
- Storage Account – Disable Cross-Tenant Replication
- Storage Account – Disable Public Network Access
- Storage Account – Enable Microsoft Defender
- Storage Account – Enable Secure Transfer
- Storage Account – Enforce Minimum TLS Version
- Storage Account – Enforce Network Access Rule
- Storage Account – Enforce Private Endpoint Access
- Storage Account – Enable Blob Soft Delete
- Storage Account – Enable Blob Versioning
- User – Enable Azure MFA
- App Service – Disable Remote Debugging
- App Service – Enable Defender
- App Service – Enable Entra ID Registration
- App Service – Enable HTTP2
- App Service – Enforce Latest TLS Version
- App Service – Enforce Secure FTPS State
- App Service – Monitor Server Errors
- App Service – Redirect HTTP to HTTPS
- Cosmos DB – Enable Backup
- Cosmos DB – Enable Microsoft Defender
- Cosmos DB – Monitor Latency
- Cosmos DB – Ensure Private Connectivity
- Cosmos DB for PostgreSQL – Monitor CPU Utilization
- Cosmos DB for PostgreSQL – Monitor IO Utilization
- Cosmos DB for PostgreSQL – Monitor Memory Utilization
- Cosmos DB for PostgreSQL – Protect From Direct Internet Traffic
- Cosmos DB – Protect From Direct Internet Traffic
- Cosmos DB – Restrict Firewall Network Access
- Virtual Machine – Enable Defender
- Virtual Machine – Protect From Direct Internet Traffic
- Key Vault – Enable Defender
- Key Vault – Ensure Vault Recoverable
- Key Vault – Require Private Endpoint Access
- Key Vault – Enforce Keys Expiration
- Key Vault – Enable Purge Protection
- MySQL Flexible Server – Enable Audit Log Events Connection
- MySQL Flexible Server – Enable Audit Logs
- MySQL Flexible Server – Enforce Minimum TLS Version
- PostgreSQL Flexible Server – Configure Log File Retention
- PostgreSQL Flexible Server – Enable Connection Logging
- PostgreSQL Flexible Server – Enable Connection Throttling
- PostgreSQL Flexible Server – Enable Disconnection Logging
- PostgreSQL Flexible Server – Enable Log Checkpoints
- Network Security Group – Ensure Flow Logs Captured
- General – Enable Auto Provisioning Log Analytics
- General – Enable Security Notifications
- General – Set Additional Email Address
- Cosmos DB – Enforce Minimum TLS Version
- PostgreSQL Flexible Server – Enforce Minimum TLS Version
- Container Instance – Enforce Use of Private Virtual Networks
- Container Instance – Enforce Managed Identity Usage
Key Vault – Use Azure RBAC Authorization
Secure Configuration Checks > Azure
This check ensures that Azure Key Vaults use Azure role-based access control (RBAC) to authorize access to keys, secrets and certificates, instead of vault access policies. Azure RBAC gives centralized, consistent access management and works with features such as Privileged Identity Management and Conditional Access.
Check Details
- Resource: Key Vault
- Check: Use Azure RBAC for Key Vault Access
- Risk: Vault access policies are managed separately for each vault and offer less control. Access can be granted too broadly, and it is harder to review and audit across the environment.
Before you start
- Once the vault switches to Azure RBAC, existing access policies stop working. Assign the equivalent Azure roles to every user, group and application that needs access, or they will lose access.
- You need the Owner or User Access Administrator role on the vault to assign roles.
Remediation via Azure Portal
-
Log in to the Azure Portal.
-
Navigate to Key vaults and select the affected key vault.
- In the left menu, click on Access control (IAM) and assign the required roles to the users, groups and applications that need access (for example, Key Vault Administrator, Key Vault Secrets User or Key Vault Crypto User).
-
In the left menu, click on Access configuration under Settings.
-
Under Permission model, select Azure role-based access control.
- Click Apply to save the changes.
Remediation via Azure CLI
-
Open Azure Cloud Shell from the Azure Portal or use a local
terminal with Azure CLI installed.
-
Run the following command to assign a role before switching:
az role assignment create \ --role "Key Vault Administrator" \ --assignee <user-or-app-object-id> \ --scope <key-vault-resource-id>
-
Run the following command to switch the vault to Azure RBAC:
az keyvault update \ --name <key-vault-name> \ --resource-group <resource-group-name> \ --enable-rbac-authorization true
Replace
<user-or-app-object-id>,<key-vault-resource-id>,<key-vault-name>and<resource-group-name>with your actual values. Choose the role that matches the access each user or application needs.
Updated on 04 November, 2026