Bump Azure.Core from 1.62.0 to 1.63.0 - #595
Open
dependabot[bot] wants to merge 1 commit into
Open
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
dependabot
Bot
added
.NET
--- updated-dependencies: - dependency-name: Azure.Core dependency-version: 1.63.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: azure-sdk - dependency-name: Azure.Messaging.ServiceBus dependency-version: 7.21.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: azure-sdk - dependency-name: Azure.ResourceManager.AppContainers dependency-version: 1.6.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: azure-sdk ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/nuget/src/azure-sdk-684ebdb31b
branch
from
September 29, 2026 11:51
b10bf72 to
d355d6a
Compare
This branch has not been deployed
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.
Pinned Azure.Core at 1.63.0.
Release notes
Sourced from Azure.Core's releases.
1.63.0
1.63.0 (2026-09-25)
Features Added
ClientCertificateCredential, including subject name and issuer certificate authentication configured withSendCertificateChain. Proof-of-possession is used by default when requested; first-party applications can opt out by setting theAzure.Identity.EnableClientCertificateMtlsProofOfPossessionAppContext switch (orAZURE_IDENTITY_ENABLE_CLIENT_CERTIFICATE_MTLS_POPenvironment variable) tofalse.EnableMtlsProofOfPossessiontofalsein the credential's JSON configuration to force bearer authentication for both exchanges. On a host that cannot provide a binding certificate, the flow falls back to a bearer token instead of failing, matching the direct managed identity flow.Breaking Changes
ManagedIdentityCredentialOptions.DisableMtlsProofOfPossessionproperty and corresponding configuration setting toEnableMtlsProofOfPossession. mTLS proof-of-possession is enabled by default for direct and configured managed identity when requested and supported. To force bearer authentication, replaceDisableMtlsProofOfPossession = truewithEnableMtlsProofOfPossession = falsein code or credential configuration.Bugs Fixed
ModelReaderWriterdeserialization ofGeoPointwithAzureCoreContextor a generated consumer context throwing because its type builder was not registered.DefaultAzureCredentialtaking up to a minute to continue past managed identity on hosts where IMDS is unavailable. Ordinary chained requests use the short Azure.Core IMDS probe, while proof-of-possession capability discovery passes the same initial IMDS timeout to MSAL so discovery retry delays are canceled and timed-out discovery results are not cached.Commits viewable in compare view.