Azure.Identity 1.5.0-beta.3

The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org. Prefix Reserved
Details
Advisory: https://github.com/advisories/GHSA-5mfx-4wcx-rv27 Severity: high
This is a prerelease version of Azure.Identity.
There is a newer version of this package available.
See the version list below for details.
dotnet add package Azure.Identity --version 1.5.0-beta.3
NuGet\Install-Package Azure.Identity -Version 1.5.0-beta.3
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Azure.Identity" Version="1.5.0-beta.3" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Azure.Identity --version 1.5.0-beta.3
#r "nuget: Azure.Identity, 1.5.0-beta.3"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Azure.Identity as a Cake Addin
#addin nuget:?package=Azure.Identity&version=1.5.0-beta.3&prerelease

// Install Azure.Identity as a Cake Tool
#tool nuget:?package=Azure.Identity&version=1.5.0-beta.3&prerelease

Azure Identity client library for .NET

The Azure Identity library provides Azure Active Directory token authentication support across the Azure SDK. It provides a set of TokenCredential implementations which can be used to construct Azure SDK clients which support AAD token authentication.

Source code | Package (nuget) | API reference documentation | Azure Active Directory documentation

Getting started

Install the package

Install the Azure Identity client library for .NET with NuGet:

Install-Package Azure.Identity

Prerequisites

  • An Azure subscription.
  • The Azure CLI can also be useful for authenticating in a development environment, creating accounts, and managing account roles.

Authenticate the client

When debugging and executing code locally it is typical for a developer to use their own account for authenticating calls to Azure services. There are several developer tools which can be used to perform this authentication in your development environment.

Authenticating via Visual Studio

Developers using Visual Studio 2017 or later can authenticate an Azure Active Directory account through the IDE. Applications using the DefaultAzureCredential or the VisualStudioCredential can then use this account to authenticate calls in their application when running locally.

To authenticate in Visual Studio select the Tools > Options menu to launch the Options dialog. Then navigate to the Azure Service Authentication options to sign in with your Azure Active Directory account.

Visual Studio Account Selection

Authenticating via Visual Studio Code

Developers using Visual Studio Code can use the Azure Account Extension, to authenticate via the IDE. Applications using the DefaultAzureCredential or the VisualStudioCodeCredential can then use this account to authenticate calls in their application when running locally.

To authenticate in Visual Studio Code, first ensure the Azure Account Extension is installed. Once the extension is installed, press F1 to open the command palette and run the Azure: Sign In command.

Visual Studio Code Account Sign In

Authenticating via the Azure CLI

Developers coding outside of an IDE can also use the Azure CLI to authenticate. Applications using the DefaultAzureCredential or the AzureCliCredential can then use this account to authenticate calls in their application when running locally.

To authenticate with the Azure CLI, users can run the command az login. For users running on a system with a default web browser the azure cli will launch the browser to authenticate the user.

Azure CLI Account Sign In

For systems without a default web browser, the az login command will use the device code authentication flow. The user can also force the Azure CLI to use the device code flow rather than launching a browser by specifying the --use-device-code argument.

Azure CLI Account Device Code Sign In

Authenticating via Azure PowerShell

Developers coding outside of an IDE can also use Azure PowerShell to authenticate. Applications using the DefaultAzureCredential or the AzurePowerShellCredential can then use this account to authenticate calls in their application when running locally.

To authenticate with Azure PowerShell, users can run the command Connect-AzAccount. For users running on a system with a default web browser and version 5.0.0 or later of azure PowerShell, it will launch the browser to authenticate the user.

For systems without a default web browser, the Connect-AzAccount command will use the device code authentication flow. The user can also force Azure PowerShell to use the device code flow rather than launching a browser by specifying the UseDeviceAuthentication argument.

Key concepts

Credentials

A credential is a class which contains or can obtain the data needed for a service client to authenticate requests. Service clients across Azure SDK accept credentials when they are constructed, and service clients use those credentials to authenticate requests to the service.

The Azure Identity library focuses on OAuth authentication with Azure Active directory, and it offers a variety of credential classes capable of acquiring an AAD token to authenticate service requests. All of the credential classes in this library are implementations of the TokenCredential abstract class in Azure.Core, and any of them can be used to construct service clients capable of authenticating with a TokenCredential.

See Credential Classes for a complete listing of available credential types.

DefaultAzureCredential

The DefaultAzureCredential is appropriate for most scenarios where the application is intended to ultimately be run in the Azure Cloud. This is because the DefaultAzureCredential combines credentials commonly used to authenticate when deployed, with credentials used to authenticate in a development environment.

Note: DefaultAzureCredential is intended to simplify getting started with the SDK by handling common scenarios with reasonable default behaviors. Developers who want more control or whose scenario isn't served by the default settings should use other credential types.

The DefaultAzureCredential will attempt to authenticate via the following mechanisms in order.

DefaultAzureCredential authentication flow

  • Environment - The DefaultAzureCredential will read account information specified via environment variables and use it to authenticate.
  • Managed Identity - If the application is deployed to an Azure host with Managed Identity enabled, the DefaultAzureCredential will authenticate with that account.
  • Visual Studio - If the developer has authenticated via Visual Studio, the DefaultAzureCredential will authenticate with that account.
  • Visual Studio Code - If the developer has authenticated via the Visual Studio Code Azure Account plugin, the DefaultAzureCredential will authenticate with that account.
  • Azure CLI - If the developer has authenticated an account via the Azure CLI az login command, the DefaultAzureCredential will authenticate with that account.
  • Azure PowerShell - If the developer has authenticated an account via the Azure PowerShell Connect-AzAccount command, the DefaultAzureCredential will authenticate with that account.
  • Interactive - If enabled the DefaultAzureCredential will interactively authenticate the developer via the current system's default browser.

Examples

You can find more examples of using various credentials in Azure Identity Examples Wiki page.

Authenticating with the DefaultAzureCredential

This example demonstrates authenticating the SecretClient from the Azure.Security.KeyVault.Secrets client library using the DefaultAzureCredential.

// Create a secret client using the DefaultAzureCredential
var client = new SecretClient(new Uri("https://myvault.azure.vaults.net/"), new DefaultAzureCredential());

Enabling the interactive authentication with the DefaultAzureCredential

Interactive authentication is disabled in the DefaultAzureCredential by default. This example demonstrates two ways of enabling the interactive authentication portion of the DefaultAzureCredential. When enabled the DefaultAzureCredential will fall back to interactively authenticating the developer via the system's default browser if when no other credentials are available. This example then authenticates an EventHubProducerClient from the Azure.Messaging.EventHubs client library using the DefaultAzureCredential with interactive authentication enabled.

// the includeInteractiveCredentials constructor parameter can be used to enable interactive authentication
var credential = new DefaultAzureCredential(includeInteractiveCredentials: true);

var eventHubClient = new EventHubProducerClient("myeventhub.eventhubs.windows.net", "myhubpath", credential);

Specifying a user assigned managed identity with the DefaultAzureCredential

Many Azure hosts allow the assignment of a user assigned managed identity. This example demonstrates configuring the DefaultAzureCredential to authenticate a user assigned identity when deployed to an azure host. It then authenticates a BlobClient from the Azure.Storage.Blobs client library with credential.

// When deployed to an azure host, the default azure credential will authenticate the specified user assigned managed identity.

string userAssignedClientId = "<your managed identity client Id>";
var credential = new DefaultAzureCredential(new DefaultAzureCredentialOptions { ManagedIdentityClientId = userAssignedClientId });

var blobClient = new BlobClient(new Uri("https://myaccount.blob.core.windows.net/mycontainer/myblob"), credential);

In addition to configuring the ManagedIdentityClientId via code, it can also be set using the AZURE_CLIENT_ID environment variable. These two approaches are equivalent when using the DefaultAzureCredential.

Define a custom authentication flow with the ChainedTokenCredential

While the DefaultAzureCredential is generally the quickest way to get started developing applications for Azure, more advanced users may want to customize the credentials considered when authenticating. The ChainedTokenCredential enables users to combine multiple credential instances to define a customized chain of credentials. This example demonstrates creating a ChainedTokenCredential which will attempt to authenticate using managed identity, and fall back to authenticating via the Azure CLI if managed identity is unavailable in the current environment. The credential is then used to authenticate an EventHubProducerClient from the Azure.Messaging.EventHubs client library.

// Authenticate using managed identity if it is available; otherwise use the Azure CLI to authenticate.

var credential = new ChainedTokenCredential(new ManagedIdentityCredential(), new AzureCliCredential());

var eventHubProducerClient = new EventHubProducerClient("myeventhub.eventhubs.windows.net", "myhubpath", credential);

Managed Identity Support

The Managed identity authentication is supported via either the DefaultAzureCredential or the ManagedIdentityCredential directly for the following Azure Services:

Credential Classes

Authenticating Azure Hosted Applications

credential usage
DefaultAzureCredential provides a simplified authentication experience to quickly start developing applications run in the Azure cloud
ChainedTokenCredential allows users to define custom authentication flows composing multiple credentials
ManagedIdentityCredential authenticates the managed identity of an azure resource
EnvironmentCredential authenticates a service principal or user via credential information specified in environment variables

Authenticating Service Principals

credential usage
ClientSecretCredential authenticates a service principal using a secret
ClientCertificateCredential authenticates a service principal using a certificate

Authenticating Users

credential usage
InteractiveBrowserCredential interactively authenticates a user with the default system browser
DeviceCodeCredential interactively authenticates a user on devices with limited UI
UsernamePasswordCredential authenticates a user with a username and password
AuthorizationCodeCredential authenticate a user with a previously obtained authorization code

Authenticating via Development Tools

credential usage
AzureCliCredential authenticate in a development environment with the Azure CLI
AzurePowerShellCredential authenticate in a development environment with the Azure PowerShell
VisualStudioCredential authenticate in a development environment with Visual Studio
VisualStudioCodeCredential authenticate in a development environment with Visual Studio Code

Note: All credential implementations in the Azure Identity library are threadsafe, and a single credential instance can be used by multiple service clients.

Environment Variables

DefaultAzureCredential and EnvironmentCredential can be configured with environment variables. Each type of authentication requires values for specific variables:

Service principal with secret
variable name value
AZURE_CLIENT_ID id of an Azure Active Directory application
AZURE_TENANT_ID id of the application's Azure Active Directory tenant
AZURE_CLIENT_SECRET one of the application's client secrets
Service principal with certificate
variable name value
AZURE_CLIENT_ID id of an Azure Active Directory application
AZURE_TENANT_ID id of the application's Azure Active Directory tenant
AZURE_CLIENT_CERTIFICATE_PATH path to a PEM-encoded certificate file including private key (without password protection)
Username and password
variable name value
AZURE_CLIENT_ID id of an Azure Active Directory application
AZURE_USERNAME a username (usually an email address)
AZURE_PASSWORD that user's password

Configuration is attempted in the above order. For example, if values for a client secret and certificate are both present, the client secret will be used.

Troubleshooting

Error Handling

Errors arising from authentication can be raised on any service client method which makes a request to the service. This is because the first time the token is requested from the credential is on the first call to the service, and any subsequent calls might need to refresh the token. In order to distinguish these failures from failures in the service client Azure Identity classes raise the AuthenticationFailedException with details to the source of the error in the exception message as well as possibly the error message. Depending on the application these errors may or may not be recoverable.

using Azure.Identity;
using Azure.Security.KeyVault.Secrets;

// Create a secret client using the DefaultAzureCredential
var client = new SecretClient(new Uri("https://myvault.azure.vaults.net/"), new DefaultAzureCredential());

try
{
    KeyVaultSecret secret = await client.GetSecretAsync("secret1");
}
catch (AuthenticationFailedException e)
{
    Console.WriteLine($"Authentication Failed. {e.Message}");
}

For more details on dealing with errors arising from failed requests to Azure Active Directory, or managed identity endpoints please refer to the Azure Active Directory documentation on authorization error codes.

Logging

The Azure Identity library provides the same logging capabilities as the rest of the Azure SDK.

The simplest way to see the logs to help debug authentication issues is to enable the console logging.

// Setup a listener to monitor logged events.
using AzureEventSourceListener listener = AzureEventSourceListener.CreateConsoleLogger();

All credentials can be configured with diagnostic options, in the same way as other clients in the SDK.

DefaultAzureCredentialOptions options = new DefaultAzureCredentialOptions()
{
    Diagnostics =
    {
        LoggedHeaderNames = { "x-ms-request-id" },
        LoggedQueryParameters = { "api-version" },
        IsLoggingContentEnabled = true
    }
};

CAUTION: Requests and responses in the Azure Identity library contain sensitive information. Precaution must be taken to protect logs when customizing the output to avoid compromising account security.

Next steps

Client libraries supporting authentication with Azure Identity

Many of the client libraries listed here support authenticating with TokenCredential and the Azure Identity library. There you will also find links where you can learn more about their use, including additional documentation and samples.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 was computed. 
.NET Framework net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (671)

Showing the top 5 NuGet packages that depend on Azure.Identity:

Package Downloads
Microsoft.Data.SqlClient The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org.

The current data provider for SQL Server and Azure SQL databases. This has replaced System.Data.SqlClient. These classes provide access to SQL and encapsulate database-specific protocols, including tabular data stream (TDS). Commonly Used Types: Microsoft.Data.SqlClient.SqlConnection Microsoft.Data.SqlClient.SqlException Microsoft.Data.SqlClient.SqlParameter Microsoft.Data.SqlClient.SqlDataReader Microsoft.Data.SqlClient.SqlCommand Microsoft.Data.SqlClient.SqlTransaction Microsoft.Data.SqlClient.SqlParameterCollection Microsoft.Data.SqlClient.SqlClientFactory When using NuGet 3.x this package requires at least version 3.4.

Microsoft.Extensions.Azure The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org.

Azure Client SDK integration with Microsoft.Extensions libraries

Microsoft.Extensions.Caching.SqlServer The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org.

Distributed cache implementation of Microsoft.Extensions.Caching.Distributed.IDistributedCache using Microsoft SQL Server. This package was built from the source code at https://github.com/dotnet/aspnetcore/tree/e1ad9117a4dac3b0f5f2a7e2b10b43b7016379b9

WindowsAzure.ServiceBus The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org.

Please note, for Azure Service Bus, Azure Event Hubs and Azure Relay, newer packages Azure.Messaging.ServiceBus, Azure.Messaging.EventHubs and Microsoft.Azure.Relay are available as of November 2020, February 2020 and March 2017 respectively. While WindowsAzure.ServiceBus will continue to receive critical bug fixes, we strongly encourage you to upgrade. Read https://aka.ms/azsdk/blog/msging/intro for more details. It adds Microsoft.ServiceBus.dll along with related configuration files to your project. This library allows AMQP 1.0 to be used as one of the protocols for communication with Microsoft Azure Service Bus. For more information on Messaging features, please visit: http://azure.microsoft.com/en-us/documentation/services/service-bus/ For more information on Event Hub features, please visit: http://go.microsoft.com/fwlink/?LinkID=403957 Please note that this package requires at least .Net Framework 4.6.2.

Microsoft.Identity.Web.Certificate The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org.

This package brings certificate management for MSAL.NET.

GitHub repositories (135)

Showing the top 5 popular GitHub repositories that depend on Azure.Identity:

Repository Stars
microsoft/semantic-kernel
Integrate cutting-edge LLM technology quickly and easily into your apps
jasontaylordev/CleanArchitecture
Clean Architecture Solution Template for ASP.NET Core
bitwarden/server
The core infrastructure backend (API, database, Docker, etc).
dotnet/efcore
EF Core is a modern object-database mapper for .NET. It supports LINQ queries, change tracking, updates, and schema migrations.
dotnet/AspNetCore.Docs
Documentation for ASP.NET Core
Version Downloads Last updated
1.11.0-beta.1 15,752 2/6/2024
1.10.4 16,995,254 11/13/2023
1.10.3 15,736,959 10/18/2023
1.10.2 6,598,848 10/9/2023
1.10.1 1,865,875 9/13/2023
1.10.0 2,863,795 8/15/2023
1.10.0-beta.1 14,936 7/17/2023
1.9.0 13,454,206 5/11/2023
1.9.0-beta.3 40,734 4/12/2023
1.9.0-beta.2 109,441 2/22/2023
1.9.0-beta.1 287,544 10/13/2022
1.8.2 15,537,714 2/8/2023
1.8.1 3,545,609 1/13/2023
1.8.0 10,519,679 11/9/2022
1.8.0-beta.1 5,349 10/13/2022
1.7.0 56,681,684 9/19/2022
1.7.0-beta.1 64,736 8/10/2022
1.6.1 6,578,729 8/8/2022
1.6.0 71,790,619 4/5/2022
1.6.0-beta.1 53,332 2/11/2022
1.5.0 32,167,314 10/14/2021
1.5.0-beta.4 54,025 9/8/2021
1.5.0-beta.3 146,938 8/11/2021
1.5.0-beta.2 35,082 7/12/2021
1.5.0-beta.1 26,709 6/8/2021
1.4.1 8,746,397 8/5/2021
1.4.0 38,371,795 5/12/2021
1.4.0-beta.5 131,863 4/6/2021
1.4.0-beta.4 34,741 3/9/2021
1.4.0-beta.3 128,419 2/10/2021
1.4.0-beta.2 22,513 1/30/2021
1.4.0-beta.1 125,006 10/16/2020
1.3.0 112,937,076 11/13/2020
1.3.0-beta.2 3,298 10/8/2020
1.3.0-beta.1 39,795 9/11/2020
1.2.3 10,243,636 9/11/2020
1.2.2 1,251,273 8/20/2020
1.2.1 769,225 8/18/2020
1.2.0-preview.6 18,519 7/23/2020
1.2.0-preview.5 16,323 7/8/2020
1.2.0-preview.4 69,739 6/10/2020
1.2.0-preview.3 121,938 5/5/2020
1.2.0-preview.2 44,984 4/6/2020
1.2.0-preview.1 71,543 3/10/2020
1.1.1 11,837,154 2/11/2020
1.1.0 805,261 11/25/2019
1.0.0 2,758,987 10/30/2019
1.0.0-preview.5 10,520 10/7/2019
1.0.0-preview.4 3,332 9/10/2019
1.0.0-preview.3 5,259 8/6/2019
1.0.0-preview.2 1,150 7/2/2019
1.0.0-preview.1 786 6/28/2019