# Manage Azure Key Vault Secrets with Rust

Rust developers need reliable patterns for accessing Azure Key Vault secrets. This skill provides focused SDK examples for authentication, retrieval, updates, listing, version access, and deletion.

## Install

```bash
npx skillstore add sickn33/azure-keyvault-secrets-rust
```

## Metadata

- Status: approved
- Slug: sickn33-azure-keyvault-secrets-rust
- Skillstore revision: r2
- Version status: missing
- Tree hash: b5494999043bae61e1af85b9dcf1f6cf39935487f21b7576fc0f79f281795b98
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/azure-keyvault-secrets-rust
- Ref: f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/sickn33-azure-keyvault-secrets-rust
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-azure-keyvault-secrets-rust/manifest

## Capabilities

- Shows how to add Azure Key Vault Secrets and Azure Identity dependencies with Cargo.
- Creates a SecretClient using DeveloperToolsCredential and an Azure Key Vault endpoint.
- Provides Rust examples for retrieving, setting, updating, and deleting secrets.
- Lists secret names through an asynchronous stream and the ResourceExt trait.
- Retrieves a specific secret version with SecretClientGetSecretOptions.
- Summarizes relevant Key Vault RBAC roles and secret-management practices.

## Use Cases

- Integrate Secrets into a Rust Service: Add authenticated secret retrieval and updates to an asynchronous Rust application.
- Prepare Production Authentication: Plan local credentials, managed identity, and least-privilege Key Vault roles for deployment.
- Review Secret Access Behavior: Assess version access, deletion, listing, and output handling before approving a service integration.

## Prompt Templates

### Add the Rust Dependencies

```
Show how to add Azure Key Vault Secrets and Azure Identity dependencies to a Rust project. Include the required vault URL environment variable.
```

### Retrieve a Secret Safely

```
Create a Rust example that authenticates with DeveloperToolsCredential and retrieves {secret_name} from {vault_url}. Never print or log the secret value.
```

### Manage Secret Metadata

```
Write an asynchronous Rust workflow that sets {secret_name}, updates its content type and tags, then lists secret names. Explain the required RBAC role.
```

### Design Production Secret Access

```
Design production Rust secret access for {application}. Use managed identity, least-privilege RBAC, version selection, redacted errors, and soft-delete considerations.
```

## Limitations

- The snippets are not a complete application and omit runtime setup and comprehensive error handling.
- The examples depend on current Azure SDK APIs and require validation against the selected crate version.
- The skill does not configure vault networking, RBAC assignments, managed identities, or deployment infrastructure.
- The retrieval example prints a secret value and must be changed before production use.

## Best Practices

- Use developer credentials locally and managed identity for production workloads.
- Assign the narrowest Key Vault role that supports the required operations.
- Keep secret values out of source code, logs, error messages, and command output.

## Anti Patterns

- Do not print retrieved secret values or include them in diagnostic messages.
- Do not grant Key Vault Secrets Officer when the application only reads secrets.
- Do not use developer credentials in production or commit credential material.

## Security Audit

- Audited at: 2026-07-23T20:38:07.25\+00:00
- Summary: The 22 command findings are Markdown fences or inline code formatting, while five URL findings are placeholder Azure endpoints or reference links. One high-severity issue remains: the retrieval example prints a secret value to standard output, which can expose credentials through logs.

## Stats

- Views: 91
- Downloads: 7
- Favorites: 0
- Popularity score: 0