# Build Azure Key Vault Certificate Workflows in Rust

Azure certificate operations require correct SDK models, authentication, and policies. This skill provides focused Rust examples for common Azure Key Vault certificate workflows.

## Install

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

## Metadata

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

## Capabilities

- Shows how to add the Azure certificate and identity crates to a Rust project.
- Creates a CertificateClient with DeveloperToolsCredential and an Azure Key Vault endpoint.
- Retrieves certificate metadata and formats an X.509 thumbprint.
- Creates and imports certificates with Azure SDK request models.
- Deletes certificates and streams certificate property listings.
- Reads and updates certificate policies through the Rust SDK.

## Use Cases

- Add Certificate Access: Set up authentication and retrieve certificate metadata from an existing Azure Key Vault.
- Manage Certificate Lifecycles: Create, import, list, and delete certificates with policy-aware Rust SDK calls.
- Review Azure Certificate Code: Check client setup, RBAC assumptions, certificate policies, and secret handling before deployment.

## Prompt Templates

### Connect to a Vault

```
Show me how to connect a Rust application to Azure Key Vault Certificates using DeveloperToolsCredential and my vault URL.
```

### Retrieve a Certificate

```
Create a Rust workflow that retrieves a named certificate and explains which returned fields contain public certificate data.
```

### Create and Import Certificates

```
Compare certificate creation and PFX or PEM import in Rust. Include required models, secure password handling, and validation steps.
```

### Design a Lifecycle Service

```
Design a Rust certificate service using Azure Key Vault. Cover policies, listing, deletion, RBAC, expiration monitoring, retries, and production credential selection.
```

## Limitations

- The snippets are partial examples and require application-specific error handling and project setup.
- Execution requires an Azure vault, network access, valid Entra ID credentials, and suitable RBAC permissions.
- The skill covers certificates, not Azure Key Vault secrets or cryptographic key workflows.
- Recovery, purge, renewal automation, and expiration monitoring are described but not implemented.

## Best Practices

- Use managed identity in production and grant only the certificate permissions required by each workload.
- Keep import passwords and certificate material outside source code, logs, and command history.
- Test lifecycle operations in a non-production vault and monitor certificate expiration.

## Anti Patterns

- Do not embed certificate passwords, private material, or production vault identifiers in source code.
- Do not grant full certificate management rights to read-only workloads.
- Do not assume partial snippets include production error handling, retries, auditing, or recovery.

## Security Audit

- Audited at: 2026-07-23T20:22:54.981\+00:00
- Summary: All 27 static findings are false positives caused by Markdown formatting, fixed installation guidance, placeholder Azure endpoints, or official reference links. One low-severity semantic finding remains because the certificate import example places a password literal directly in source code.

## Stats

- Views: 95
- Downloads: 9
- Favorites: 0
- Popularity score: 0