Bump Azure.Core from 1.58.0 to 1.59.0 - #6399
#6399Merged
premun merged 1 commit intoJun 16, 2026
maindotnet/arcade-services:mainfrom
dependabot/nuget/Azure.Core-1.59.0dotnet/arcade-services:dependabot/nuget/Azure.Core-1.59.0Copy head branch name to clipboard
Merged
Bump Azure.Core from 1.58.0 to 1.59.0#6399premun merged 1 commit intomaindotnet/arcade-services:mainfrom dependabot/nuget/Azure.Core-1.59.0dotnet/arcade-services:dependabot/nuget/Azure.Core-1.59.0Copy head branch name to clipboard
premun merged 1 commit into
maindotnet/arcade-services:mainfrom
dependabot/nuget/Azure.Core-1.59.0dotnet/arcade-services:dependabot/nuget/Azure.Core-1.59.0Copy head branch name to clipboard
Conversation
Member
|
@dependabot rebase |
--- updated-dependencies: - dependency-name: Azure.Core dependency-version: 1.59.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/nuget/Azure.Core-1.59.0
branch
from
June 16, 2026 09:08
8d06d6a to
fc985be
Compare
premun
approved these changes
Jun 16, 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
1 participant
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.58.0 to 1.59.0.
Release notes
Sourced from Azure.Core's releases.
1.59.0
1.59.0 (2026-06-09)
Features Added
AZID0004) mTLS Proof-of-Possession token binding support for managed identity scenarios, including dynamic host capability detection via MSAL and transport certificate rotation APIs onBearerTokenAuthenticationPolicy.Bugs Fixed
BearerTokenAuthenticationPolicyso that theAuthorizationheader is no longer re-attached to a request that has been redirected to a different host. Previously,RedirectPolicywould strip theAuthorizationheader before following a redirect, but the per-retryBearerTokenAuthenticationPolicywould re-add the cached bearer token to the redirected request — including when the redirect target was a different host. The policy now detects when the request URI authority has changed since it last authorized the message, defensively strips anyAuthorizationheader, and skips both re-authorization and theWWW-Authenticate(CAE)401handler so that no bearer token is sent to — or fetched in response to a challenge from — the redirect target. Same-host redirects, normal (non-redirected) requests, and CAE handling against the original host are unchanged. Callers who explicitly enabled auto-redirect (viaHttpPipelineTransportOptions.IsClientRedirectEnabled = trueorRedirectPolicy.SetAllowAutoRedirect(message, true)) and depended on the bearer token being re-attached on cross-host redirects should construct a separate client targeting the redirect-target host with a credential bound to that host's resource.Other Changes
Microsoft.Identity.Clientdependency to4.84.2.Commits viewable in compare view.