migrating-azure-keyvault

Migrate legacy Azure Key Vault SDK usage to Azure.Security.KeyVault libraries for .NET.

19|2|Updated May 13, 2026
One-click install
npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill migrating-azure-keyvault
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrating-azure-keyvault
Source: https://github.com/microsoft/upgrade-agent-plugins/tree/main/plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/lazy/libraries/migrating-azure-keyvault
Command: npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill migrating-azure-keyvault

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of migrating from the deprecated Microsoft.Azure.KeyVault SDK to the modern Azure.Security.KeyVault client libraries, simplifying the transition for developers.

Core Features & Use Cases

  • SDK Migration: Assists in migrating from the old Microsoft.Azure.KeyVault SDK to the new Azure.Security.KeyVault.* libraries.
  • Authentication Replacement: Guides the replacement of custom token callbacks with Azure.Identity.
  • Client Initialization: Offers instructions on replacing the single KeyVaultClient with resource-specific clients like SecretClient, KeyClient, and CertificateClient.
  • Operation Conversion: Provides guidance on converting secret, key, and certificate operations from the old SDK to the new one.
  • Error Handling: Offers a guide to migrate error handling from KeyVaultErrorException to RequestFailedException.
  • Use Case: Useful for developers who need to update their applications to use the modern Azure.Security.KeyVault client libraries after deprecation warnings.

Quick Start

Run the script to automatically detect usage of the deprecated Key Vault SDK and generate a migration plan.

Frequently Asked Questions about migrating-azure-keyvault

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

FAQPage Schema
How do I migrate from the deprecated Microsoft.Azure.KeyVault SDK to the new libraries?

Run the migration script to automatically detect deprecated Key Vault SDK usage and generate a tailored plan for transitioning to Azure.Security.KeyVault libraries.

How do I replace custom token callbacks when upgrading Azure Key Vault authentication?

When upgrading Azure Key Vault authentication, you replace custom token callbacks by utilizing Azure.Identity for handling authentication across the new Azure.Security.KeyVault client libraries.

How do I handle KeyVaultErrorException migration after updating to modern Azure Key Vault libraries?

For KeyVaultErrorException migration after updating to modern Azure Key Vault libraries, you transition your error handling logic to catch RequestFailedException instead.

Does the Azure Key Vault SDK migration support converting operations for secrets, keys, and certificates?

Yes, the Azure Key Vault SDK migration handles converting operations for secrets, keys, and certificates by mapping legacy calls to the new resource-specific clients.

Can I use this migration process for .NET Core applications receiving Key Vault deprecation warnings?

Yes, you can use this migration process for .NET Core applications receiving deprecation warnings, as it focuses on .NET languages and streamlines the transition to modern Azure.Security.KeyVault libraries.