Bump Azure.Identity from 1.12.1 to 1.15.0 #143
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated Azure.Identity from 1.12.1 to 1.15.0.
Release notes
Sourced from Azure.Identity's releases.
1.15.0
1.15.0 (2025-08-07)
Breaking Changes
Behavioral Breaking Changes
SharedTokenCacheCredential. The supporting credential (SharedTokenCacheCredential) was a legacy mechanism for authenticating clients using credentials provided to Visual Studio. For brokered authentication, consider usingInteractiveBrowserCredentialinstead. The following changes have been made:SharedTokenCacheCredentialclass is marked as[Obsolete]and[EditorBrowsable(EditorBrowsableState.Never)]SharedTokenCacheCredentialOptionsclass is marked as[Obsolete]and[EditorBrowsable(EditorBrowsableState.Never)]DefaultAzureCredentialOptions.ExcludeSharedTokenCacheCredentialproperty is marked as[Obsolete]and[EditorBrowsable(EditorBrowsableState.Never)]SharedTokenCacheUsernameproperty is marked as[Obsolete]and[EditorBrowsable(EditorBrowsableState.Never)]SharedTokenCacheCredentialis no longer included in theDefaultAzureCredentialauthentication flowBugs Fixed
AdditionallyAllowedTenantsvalues which will now be matched against tenant IDs without case sensitivity, making the authentication more resilient to case differences in tenant IDs returned from WWW-Authenticate challenges (#51693).Other Changes
BrokerAuthenticationCredentialhas been renamed asBrokerCredential.Added the
EditorBrowsable(Never)attribute to propertyVisualStudioCodeTenantIdasTenantIdis preferred. TheVisualStudioCodeTenantIdproperty exists only to provide backwards compatibility.1.15.0-beta.1
1.15.0-beta.1 (2025-07-17)
Features Added
Expanded the set of acceptable values for environment variable
AZURE_TOKEN_CREDENTIALSto allow for selection of a specific credential in theDefaultAzureCredentialchain. 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:BrokerAuthenticationCredentialrequires that the project include a reference to package Azure.Identity.Broker.Re-introduced
VisualStudioCodeCredentialand included it in theDefaultAzureCredentialauthentication 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
ManagedIdentityCredentialnow 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).ManagedIdentityCredentialthrowsCredentialUnavailableExceptionwhen the IMDS endpoint is unavailable. This addresses a regression in how it behaves in theChainedTokenCredential(47057).Other Changes
VisualStudioCredentialthrowsCredentialUnavailableExceptionfor 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.AzureApplicationCredential. For context, see issue 49781.1.13.2
1.13.2 (2025-07-18)
Features Added
Azure.ResourceManagerAOT-compatible.Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)