.NET: Bump Azure.Core from 1.61.0 to 1.62.0

[dependabot]

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

• Added experimental (SCME0002) AzureCredentialResolver.Default public static property so standalone callers can share the process-wide credential cache used by DI-resolved paths.
• AzureCredentialResolver now resolves every ChainedTokenCredential Sources[] entry through the active resolver chain, so any registered CredentialResolver (built-in, broker, or third-party) can claim or override an entry. Entries are constructed as chained, so transient failures surface as CredentialUnavailableException and the chain falls through.

Breaking Changes

• AzureCredentialResolver now resolves a top-level single source (e.g. CredentialSource: AzureCliCredential) to the concrete credential type (AzureCliCredential) rather than a DefaultAzureCredential wrapper. Construction is unchanged (it uses the same DefaultAzureCredentialFactory helpers) — only the returned type differs; callers using CredentialSettings.TokenProvider as a TokenCredential are unaffected.
• AzureCredentialResolver no longer claims top-level BrokerCredential sections (canonical name or broker alias); they now require BrokerCredentialResolver from Azure.Identity.Broker 1.7.0+ (e.g. via AddBrokerCredentialResolver()). BrokerCredential entries nested inside a ChainedTokenCredential continue to resolve. Note: if BrokerCredentialResolver from Azure.Identity.Broker 1.7.0 is registered ahead of AzureCredentialResolver, a nested BrokerCredential entry is currently built as non-chained, so it may surface AuthenticationFailedException and 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 future Azure.Identity.Broker release 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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[Copilot]

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.