You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Microsoft.Azure.KeyVAult will be deprecated soon in favor of the new Azure SDK libraries, such as Azure.Security.KeyVault.Secrets. Along with Azure.Core, Azure.Identity, and Azure.ResourceManager.KeyVault (the latter is in preview currently), these provide a number of benefits and bug fixes over the older SDKs and are being unified (though still idiomatic) across supported languages. See https://aka.ms/azsdk/valueprop and https://aka.ms/azsdk/intro for more details.
The main difference when migrating is that certificates, keys, and secrets all got their own clients - though share a single HttpClient by default - instead of everything together in one monolithic KeyVaultClient. The methods are conceptually the same, but I'm happy to provide more details as needed.
The text was updated successfully, but these errors were encountered:
Microsoft.Azure.KeyVAult will be deprecated soon in favor of the new Azure SDK libraries, such as Azure.Security.KeyVault.Secrets. Along with Azure.Core, Azure.Identity, and Azure.ResourceManager.KeyVault (the latter is in preview currently), these provide a number of benefits and bug fixes over the older SDKs and are being unified (though still idiomatic) across supported languages. See https://aka.ms/azsdk/valueprop and https://aka.ms/azsdk/intro for more details.
The main difference when migrating is that certificates, keys, and secrets all got their own clients - though share a single HttpClient by default - instead of everything together in one monolithic
KeyVaultClient. The methods are conceptually the same, but I'm happy to provide more details as needed.The text was updated successfully, but these errors were encountered: