azure-identity-dotnet

Authenticate .NET applications to Azure services using Azure.Identity credential types.

2.9k|323|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/microsoft/skills --skill azure-identity-dotnet-microsoft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azure-identity-dotnet
Source: https://github.com/microsoft/skills/tree/main/.github/plugins/azure-sdk-dotnet/skills/azure-identity-dotnet
Command: npx skills add https://github.com/microsoft/skills --skill azure-identity-dotnet-microsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Authentication for Azure services in .NET applications often requires managing multiple credential sources and wiring them into SDK clients. This skill provides a unified approach via the Azure.Identity library, enabling seamless switch between credentials without code changes.

Core Features & Use Cases

  • Unified credentials: Supports DefaultAzureCredential, ManagedIdentityCredential, ClientSecretCredential, and more to cover local development, CI/CD, and cloud deployments.
  • Seamless DI integration: Works with ASP.NET Core DI to inject credentials into Azure SDK clients.
  • Real-world use cases: Authenticate to storage, databases, and messaging services across environments with a single credential orchestration.

Quick Start

Install the Azure.Identity package and use DefaultAzureCredential to authenticate Azure SDK clients in your .NET application.

Frequently Asked Questions about azure-identity-dotnet

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

FAQPage Schema
How do I handle Azure authentication across local development and production in .NET?

Azure authentication in .NET can be unified using DefaultAzureCredential, which automatically switches between credential types for local development and cloud deployments without requiring code changes.

How do I inject Azure credentials into ASP.NET Core DI?

You can inject Azure credentials into ASP.NET Core DI by registering the Azure.Identity library credential classes, allowing Azure SDK clients to receive authentication through standard dependency injection.

What is the best way to authenticate .NET apps to Azure services without managing multiple credential sources?

The best way to authenticate .NET apps to Azure services is using a unified credential mechanism like DefaultAzureCredential, which orchestrates multiple credential types across environments seamlessly.

Can I use ManagedIdentityCredential for Azure SDK clients in .NET?

Yes, ManagedIdentityCredential is supported by the Azure.Identity library to authenticate Azure SDK clients in .NET, specifically targeting cloud deployment scenarios where managed identities are available.

Does Azure authentication for .NET work with storage, databases, and messaging services?

Azure authentication for .NET works with storage, databases, and messaging services by using a single credential orchestration mechanism to authenticate to these Azure services across different environments.

Why does my .NET app need different Azure credentials for different environments?

Your .NET app needs different Azure credentials because local development, CI/CD, and cloud deployments require distinct authentication sources, which DefaultAzureCredential resolves by automatically selecting the appropriate credential type.