key-vault

Name: key-vault
Availability: InStock
Author: theslashdojo

Automate Azure Key Vault lifecycle management with the Azure CLI.

Updated Apr 10, 2026

Search Tags:#azure #rbac #secrets #secret-management #azure-cli #key-vault #az-keyvault

Ready to run

npx skills add https://github.com/theslashdojo/dojo --skill key-vault

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: key-vault
Source: https://github.com/theslashdojo/dojo/tree/main/nodes/azure/key-vault
Command: npx skills add https://github.com/theslashdojo/dojo --skill key-vault

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires azure-cli, and includes scripts (resource) components.

What problem does it solve?

Create Azure Key Vaults, grant vault-scoped RBAC, and manage secret values with the Azure CLI. Use when automation needs a durable secret boundary for Azure-hosted workloads or deployment pipelines.

Core Features & Use Cases

Create vaults with RBAC authorization enabled to restrict secret access to specific principals.
Manage secret lifecycles (set, show, delete, purge) to protect sensitive configuration at runtime.
Integrate with Azure App Service or Functions by referencing Key Vault secrets instead of embedding values.

Quick Start

Create a new Key Vault, grant vault access to a principal with the Key Vault Secrets Officer role, and set a secret using az keyvault.

Frequently Asked Questions about key-vault

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create an Azure Key Vault with RBAC authorization using the Azure CLI?▼

To create an Azure Key Vault with RBAC authorization, use the Azure CLI to provision the vault and enable role-based access control. This restricts secret access to specific principals, establishing a durable secret boundary for Azure-hosted workloads and deployment pipelines.

What is the best way to manage Azure Key Vault secret lifecycles in automation pipelines?▼

Managing Azure Key Vault secret lifecycles in automation pipelines is best handled through Azure CLI scripting. You can set, show, delete, and purge secrets programmatically to protect sensitive configurations at runtime and ensure consistent secret rotation across automated deployments.

How do I grant a principal the Key Vault Secrets Officer role for vault-scoped access?▼

To grant a principal the Key Vault Secrets Officer role, apply vault-scoped RBAC using the Azure CLI. This action delegates granular access control to specific identities, ensuring only authorized services manage secret values within the Azure Key Vault boundary.

Can I integrate Azure App Service or Functions with Key Vault secrets instead of embedding values?▼

Yes, you can integrate Azure App Service or Functions by referencing Azure Key Vault secrets directly. This replaces the need for embedding sensitive configuration values, ensuring your runtime applications securely retrieve secrets via vault-backed references.

Do I need the Azure CLI installed to automate Key Vault creation and secret rotation?▼

Yes, you need the Azure CLI installed to automate Key Vault creation and secret rotation. This Skill depends on the Azure CLI to execute script-driven actions like vault creation, RBAC grants, and secret operations across your deployment workflows.

Why does my Azure Key Vault secret deletion require a separate purge step?▼

Azure Key Vault secret deletion requires a separate purge step because deleted secrets are retained in a soft-delete state. Explicitly purging the secret permanently removes it, completing the secret lifecycle and ensuring sensitive configuration values are fully destroyed.