migrating-azure-keyvault Skill
Migrates from the deprecated Microsoft.Azure.KeyVault SDK to the modern Azure.Security.KeyVault client libraries (Secrets, Keys, Certificates). Use ONLY when Microsoft.Azure.KeyVault has been flagged as obsolete or deprecated and must be replaced — not for version-bump scenarios where Microsoft.Azure.KeyVault is still Published by microsoft in upgrade-agent-plugins.
What is migrating-azure-keyvault Skill?
Migrates from the deprecated Microsoft.Azure.KeyVault SDK to the modern Azure.Security.KeyVault client libraries (Secrets, Keys, Certificates). Use ONLY when Microsoft.Azure.KeyVault has been flagged as obsolete or deprecated and must be replaced — not for version-bump scenarios where Microsoft.Azure.KeyVault is still Published by microsoft in upgrade-agent-plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Security review
- Security review use cases
Technical details
- Install or run with Copy skill directory
When to use migrating-azure-keyvault Skill
- Use it for security review.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/upgrade-agent-plugins
- Skill file: plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/lazy/libraries/migrating-azure-keyvault/SKILL.md
What it does
Migrates from the deprecated Microsoft.Azure.KeyVault SDK to the modern Azure.Security.KeyVault client libraries (Secrets, Keys, Certificates). Use ONLY when Microsoft.Azure.KeyVault has been flagged as obsolete or deprecated and must be replaced — not for version-bump scenarios where Microsoft.Azure.KeyVault is still
Skill instructions
Azure Key Vault SDK Migration Overview Migrate from the deprecated Microsoft.Azure.KeyVault SDK to the modern Azure.Security.KeyVault. libraries. The new SDK splits the single KeyVaultClient into resource-specific clients (SecretClient, KeyClient, CertificateClient) and uses Azure.Identity for authentication instead of custom token callbacks. Both synchronous and asynchronous APIs are available. Package Reference Changes Old References (Remove) xml <PackageReference Include="Microsoft.Azure.KeyVault" Version="{any}" / <PackageReference Include="Microsoft.Azure.KeyVault.Models" Version="{any}" / <!-- Legacy authentication helper -- <PackageReference Include="Microsoft.Azure.Services.AppAuthentication" Version="{any}" / New References (Add) xml <!-- Add only the packages for the resource types the project uses -- <PackageReference Include="Azure.Security.KeyVault.Secrets" Version="{latest-stable}" / <PackageReference Include="Azure.Security.KeyVault.Keys" Version="{latest-stable}" / <Pac
Explore related resources
Frequently asked questions
What is migrating-azure-keyvault?
migrating-azure-keyvault is a open-source AI agent skill with Copy skill directory. Migrates from the deprecated Microsoft.Azure.KeyVault SDK to the modern Azure.Security.KeyVault client libraries (Secrets, Keys, Certificates).
Who is migrating-azure-keyvault best for?
migrating-azure-keyvault is best for reusing agent instructions, scripts, and references, security review workflows.
How do I install migrating-azure-keyvault?
Install or run migrating-azure-keyvault using Copy skill directory. Check migrating-azure-keyvault for the latest setup command.
Is migrating-azure-keyvault actively maintained?
migrating-azure-keyvault may need a closer maintenance check before production use.
Auto-fetched from GitHub.
