1.15.0-beta.1 (2025-07-17)
Features Added
-
Expanded the set of acceptable values for environment variable
AZURE_TOKEN_CREDENTIALS
to allow for selection of a specific credential in theDefaultAzureCredential
chain. The valid values now include any of the credential names available in the default chain (VisualStudioCredential
,VisualStudioCodeCredential
,AzureCliCredential
,AzurePowerShellCredential
,AzureDeveloperCliCredential
,EnvironmentCredential
,WorkloadIdentityCredential
,ManagedIdentityCredential
,InteractiveBrowserCredential
, orBrokerAuthenticationCredential
.) Note:BrokerAuthenticationCredential
requires that the project include a reference to package Azure.Identity.Broker. -
Re-introduced
VisualStudioCodeCredential
and included it in theDefaultAzureCredential
authentication flow. This credential now supports Single Sign-On (SSO) through the authentication broker on Windows, macOS, and Linux using the Azure.Identity.Broker package.
Bugs Fixed
ManagedIdentityCredential
now retries 410 status responses for at least 70 seconds total duration as required by Azure IMDS documentation. Previously, 410 responses were retried with the same short exponential backoff as other status codes, resulting in insufficient retry duration (#50724).ManagedIdentityCredential
throwsCredentialUnavailableException
when the IMDS endpoint is unavailable. This addresses a regression in how it behaves in theChainedTokenCredential
(47057).
Other Changes
VisualStudioCredential
throwsCredentialUnavailableException
for all failures except for OperationCancelledException due to cancellation being requested for aCancellationToken
. This ensures that it falls through for most failures when part of a chained credential.- Removed
AzureApplicationCredential
. For context, see issue 49781.