Update dependency Azure.Core to 1.60.0 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
Azure.Core (source)	1.57.0 → 1.60.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

Azure/azure-sdk-for-net (Azure.Core)

v1.60.0

Compare Source

1.60.0 (2026-06-30)

Features Added

• Added experimental (AZID0004) DisableMtlsProofOfPossession property to ManagedIdentityCredentialOptions to allow explicit opt-out of mTLS proof-of-possession token acquisition when the underlying requirements are met.
• Simplified mTLS token binding integration for Managed Identity by moving to an optional, runtime-resolved attestation model using lazy reflection-based resolution of the Microsoft.Identity.Client.KeyAttestation extension package.

Bugs Fixed

• Fixed a regression (introduced with managed identity host capability detection) where DefaultAzureCredential could throw an AuthenticationFailedException and stop evaluating the credential chain on hosts without a managed identity — for example, a developer machine running in Visual Studio where the IMDS endpoint (169.254.169.254) is unreachable. When ManagedIdentityCredential is part of a chain, a failure to detect the managed identity source/capabilities is now surfaced as a CredentialUnavailableException, allowing the chain to continue to the next credential.

v1.59.0

Compare Source

1.59.0 (2026-06-09)

Features Added

• Added experimental (AZID0004) mTLS Proof-of-Possession token binding support for managed identity scenarios, including dynamic host capability detection via MSAL and transport certificate rotation APIs on BearerTokenAuthenticationPolicy.

Bugs Fixed

• Fixed BearerTokenAuthenticationPolicy so that the Authorization header is no longer re-attached to a request that has been redirected to a different host. Previously, RedirectPolicy would strip the Authorization header before following a redirect, but the per-retry BearerTokenAuthenticationPolicy would 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 any Authorization header, and skips both re-authorization and the WWW-Authenticate (CAE) 401 handler 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 (via HttpPipelineTransportOptions.IsClientRedirectEnabled = true or RedirectPolicy.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

• Updated Microsoft.Identity.Client dependency to 4.84.2.

v1.58.0

Compare Source

1.58.0 (2026-06-04)

Features Added

• Adopt System.ClientModel 1.14.0

Bugs Fixed

• Fixed NullReferenceException thrown by Operation.RehydrateAsync / ArmOperation.RehydrateAsync (and the resulting operation's UpdateStatusAsync / Value) when the rehydrated long-running operation has completed with a failure. OperationState.Failure and OperationState<T>.Failure now honor their documented contract and materialize a default RequestFailedException from the raw response when the caller passes null, matching the behavior of the non-rehydration polling path.
• Fixed DiagnosticScope to mark the parent ActivityContext as remote (IsRemote = true) when a traceparent is provided via SetTraceContext or AddLink. The traceparent in these paths is always extracted from an external source (e.g. a messaging broker's application properties), so samplers that distinguish local vs. remote parents — such as the RateLimitedSampler used by the Azure Monitor OpenTelemetry exporter — can now make correct decisions for activities started from incoming messages.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud