CLOUD DEVELOPMENT / Microsoft
Azure Key Vault Keys SDK for .NET
Microsoft's .NET guide to Azure.Security.KeyVault.Keys: creating RSA, EC and symmetric keys in Key Vault or Managed HSM, rotating them by policy, and running encrypt, wrap and sign operations through CryptographyClient.
“Azure Key Vault Keys SDK for .NET. Client library for managing cryptographic keys in Azure Key Vault and Managed HSM. Use for key creation, rotation, encryption, decryption, signing, and verification. Triggers: "Key Vault keys", "KeyClient", "CryptographyClient", "RSA key", "EC key", "encrypt decrypt .NET", "key rotation", "HSM". ”
01 / THE REASONING
Why this made the selection.
- It walks the key lifecycle in one file: create RSA, EC and Oct keys, list versions, update properties, delete and purge, back up and restore, rotate, and set a policy that rotates 30 days before a 90-day expiry.
- It separates KeyClient management from CryptographyClient operations (encrypt and decrypt, wrap and unwrap, sign and verify) and tabulates the algorithms for each, marking Rsa15 as legacy.
- It names the RBAC roles Key Vault Crypto Officer, Key Vault Crypto User and Key Vault Reader, and handles 404 and 403 from RequestFailedException separately.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- .github/plugins/azure-sdk-dotnet/skills/azure-security-keyvault-keys-dotnet/SKILL.md (all 417 lines)
- .github/plugins/azure-sdk-dotnet/README.md
- .github/plugins/azure-sdk-dotnet/.claude-plugin/plugin.json
- README.md
- LICENSE
Our findings
- The Authentication sample builds DefaultAzureCredential with DefaultAzureCredential.DefaultEnvironmentVariableName and says to set AZURE_TOKEN_CREDENTIALS=prod, or a specific credential, in production.
- KEY_VAULT_NAME is marked required and AZURE_KEYVAULT_URL optional; AZURE_TOKEN_CREDENTIALS is marked "Required only if DefaultAzureCredential is used in production".
- Practice 3 says to set HardwareProtected = true for sensitive keys. The EC and Oct samples set it; the RSA options sample sets it false with the comment "true for HSM-backed".
- KeyResolver turns a key ID URI into a CryptographyClient for later operations.
- The frontmatter declares license MIT, author Microsoft, version 1.0.0 and package Azure.Security.KeyVault.Keys. It declares no allowed-tools.
Not established by this review
- No key was created, rotated, deleted, purged, backed up or used for a cryptographic operation.
- No dotnet package was added to a project.
- Neither the azure-sdk-dotnet plugin nor azure-security-keyvault-keys-dotnet was installed.
- Not executed: it was not installed or run.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Add a skill to your workflow.
- The azure-sdk-dotnet plugin README prints `npx skills add microsoft/skills --skill azure-sdk-dotnet` under Install. It installs the whole azure-sdk-dotnet plugin, whose skill table lists azure-security-keyvault-keys-dotnet; it does not install that skill alone.
- The same README prints `/plugin install azure-sdk-dotnet@skills`, which also brings in azure-security-keyvault-keys-dotnet together with every other skill in the plugin. The repository README runs plugin commands inside Copilot CLI after `/plugin marketplace add microsoft/skills`.
Before you start
- The skill prints `dotnet add package Azure.Security.KeyVault.Keys` and `dotnet add package Azure.Identity`. This review ran neither.
- A Key Vault or Managed HSM named by KEY_VAULT_NAME or AZURE_KEYVAULT_URL, and an identity holding Key Vault Crypto Officer, Key Vault Crypto User or Key Vault Reader as the operation needs.
- Copilot CLI, where `/plugin install azure-sdk-dotnet@skills` adds this keys skill with the rest of the plugin.
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://github.com/microsoft/skills/blob/fc164ba1d7a0c10377dbcc1c9ac07253b9329fdb/.github/plugins/azure-sdk-dotnet/skills/azure-security-keyvault-keys-dotnet/SKILL.md
Supports: name, upstreamDescription, summary, whySelected, bestFor, limitations, review.findings, install.prerequisites, access.permissions
https://github.com/microsoft/skills/blob/fc164ba1d7a0c10377dbcc1c9ac07253b9329fdb/.github/plugins/azure-sdk-dotnet/README.md
Supports: install.sourceUrl, install.steps, limitations (install scope)
https://github.com/microsoft/skills/blob/fc164ba1d7a0c10377dbcc1c9ac07253b9329fdb/.github/plugins/azure-sdk-dotnet/.claude-plugin/plugin.json
Supports: publisher, license (plugin licence field)
- Repository README ↗Checked
https://github.com/microsoft/skills/blob/fc164ba1d7a0c10377dbcc1c9ac07253b9329fdb/README.md
Supports: compatibility, install.steps (Copilot CLI plugin commands)
- Repository LICENSE ↗Checked
https://github.com/microsoft/skills/blob/fc164ba1d7a0c10377dbcc1c9ac07253b9329fdb/LICENSE
Supports: license
https://github.com/microsoft/skills/commit/073741f2fc5628b22e8a5f8b56fb3878c418ecb6
Supports: limitations (last commit date)