What's New in Azure SDKs: Identity Goes GA and More -- Visual Studio Magazine

What's New in Azure SDKs: Identity Goes GA and More

By David Ramel
08/19/2020

Microsoft's latest monthly updates to its Azure SDKs for cloud computing include many new features, updates and fixes, highlighted by Azure Identity graduating to general availability (GA).

For the Identity library, first previewed in June 2019, the GA release features new developer credential types, logging enhancements, proactive token refresh, and authority host support, said Microsoft's Jon Gallant in an Aug. 18 SDK roundup announcement.

"In this release, we have added support for more environments and developer platforms, without compromising the simplicity of the DefaultAzureCredential class," said Jianghao Lu, senior software engineer, in his own Aug. 18 blog post about Identity. "It's now easier than ever to authenticate your cloud application on your local workstation, with your choice of IDE or developer tool. When the application is deployed to Azure, you are given more control and insights on how your application is authenticated."

The DefaultAzureCredential class previously supported reading credentials from environment variables, Managed Identity, Windows shared token cache, and interactively in the browser (for .NET and Python), in that order, Lu said.

New environments include:

IntelliJ (Java only)
Visual Studio (.NET only)
Visual Studio Code
Azure CLI

Other environments received updates, specific to platform/language.

**[Click on image for larger view.]** Default Azure Credential Flow *(source: Microsoft).*

Other release highlights listed by Gallant include:

Azure Cognitive Search SDK for .NET added FieldBuilder to help easily build a search index from a model type.
The Azure SDK for Java added ObjectSerializer and JsonSerializer APIs to support pluggable serialization within SDKs. See more about that and other changes in the release notes.
Added support for Key Vault service version 7.1 for Keys, Secrets, and Certificates. See more about that (and the aforementioned FieldBuilder) in the .NET release notes, and also in the Java release notes.

The Azure SDK for JavaScript, in addition to Identity and Azure Key Vault going GA, sees updates to Core libraries, Azure Event Hubs and Azure Form Recognizer, while Azure Service Bus was introduced in preview. See more in the release notes for that SDK.

The Azure SDK for Python sees Storage features going GA and updates to App Configuration, Identity, Text Analytics, Key Vault and Cosmos DB, with previews for Service Bus, Form Recognizer and Search. See more in the release notes for that SDK.

Fore additional information about everything above and much more, links to packages, code, and docs can be found on the Azure SDK Releases page.

About the Author

David Ramel is an editor and writer at Converge 360.

Printable Format

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.