.NET: Bump Azure.Core from 1.61.0 to 1.62.0 - #7954
Merged
Roger Barreto (rogerbarreto) merged 1 commit intoAug 31, 2026
Merged
Conversation
--- updated-dependencies: - dependency-name: Azure.Core dependency-version: 1.62.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
.NET
dependabot
Bot
requested review from
chetantoshniwal and
Peter Ibekwe (peibekwe)
as code owners
August 30, 2026 08:45
dependabot
Bot
requested review from
SergeyMenshykh,
Roger Barreto (rogerbarreto) and
westey (westey-m)
as code owners
August 30, 2026 08:45
dependabot
Bot
added
the
dependencies
github-actions
Bot
changed the title
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the centrally managed Azure.Core dependency from 1.61.0 to 1.62.0.
Changes:
- Bumps Azure.Core to version 1.62.0.
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
Roger Barreto (rogerbarreto)
approved these changes
Aug 31, 2026
This was referenced Aug 31, 2026
Merged
This was referenced Sep 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.Core from 1.61.0 to 1.62.0.
Release notes
Sourced from Azure.Core's releases.
1.62.0
1.62.0 (2026-08-20)
Features Added
SCME0002)AzureCredentialResolver.Defaultpublic static property so standalone callers can share the process-wide credential cache used by DI-resolved paths.AzureCredentialResolvernow resolves everyChainedTokenCredentialSources[]entry through the active resolver chain, so any registeredCredentialResolver(built-in, broker, or third-party) can claim or override an entry. Entries are constructed as chained, so transient failures surface asCredentialUnavailableExceptionand the chain falls through.Breaking Changes
AzureCredentialResolvernow resolves a top-level single source (e.g.CredentialSource: AzureCliCredential) to the concrete credential type (AzureCliCredential) rather than aDefaultAzureCredentialwrapper. Construction is unchanged (it uses the sameDefaultAzureCredentialFactoryhelpers) — only the returned type differs; callers usingCredentialSettings.TokenProvideras aTokenCredentialare unaffected.AzureCredentialResolverno longer claims top-levelBrokerCredentialsections (canonical name orbrokeralias); they now requireBrokerCredentialResolverfromAzure.Identity.Broker1.7.0+ (e.g. viaAddBrokerCredentialResolver()).BrokerCredentialentries nested inside aChainedTokenCredentialcontinue to resolve. Note: ifBrokerCredentialResolverfromAzure.Identity.Broker1.7.0 is registered ahead ofAzureCredentialResolver, a nestedBrokerCredentialentry is currently built as non-chained, so it may surfaceAuthenticationFailedExceptionand abort the chain instead of falling through to the next entry. Without a broker resolver registered, the built-in chain path builds the broker entry as chained (correct fall-through). A futureAzure.Identity.Brokerrelease will make its resolver honor chained semantics for nested entries.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 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)