Bump the nuget group with 2 updates

[dependabot]

Updated Azure.Identity from 1.4.1 to 1.11.4.

Release notes

Sourced from Azure.Identity's releases.

1.7.0

1.7.0 (2025-09-22)

Features Added

• Added ClientConnection constructor, accepting credentials and metadata.

• Added JsonPatch which allows for applying JSON Patch operations to JSON documents.

1.6.0

1.6.0 (2025-10-24)

Features Added

• Upgraded api-version tag from 'package-2025-01' to 'package-2025-06'. Tag details available at https://github.com/Azure/azure-rest-api-specs/blob/1e7684349abdacee94cbf89200f319cd49e323f2/specification/storage/resource-manager/readme.md.
  • Supported new property GeoPriorityReplicationStatus.IsBlobEnabled on Storage accounts.
  • Supported new ObjectReplicationPolicy Properties: PriorityReplication.Enabled.

1.5.0

1.5.0 (2025-09-23)

Features Added

• Support a custom hub name in MapWebPubSubHub extension method.

Other Changes

• Upgrade Azure.Messaging.WebPubSub to 1.6.0.

1.5.0-beta.1

1.5.0-beta.1 (2025-10-16)

Features Added

• Added mapping for enduser.pseudo.id attribute to user_Id

• Added support for configuring sampling via OpenTelemetry environment
  variables:

  • OTEL_TRACES_SAMPLER (supported values: microsoft.rate_limited,
    microsoft.fixed_percentage).
  • OTEL_TRACES_SAMPLER_ARG (rate limit in traces/sec for
    microsoft.rate_limited, sampling ratio 0.0 - 1.0 for
    microsoft.fixed_percentage). This now applies to both
    UseAzureMonitorExporter and the direct
    Sdk.CreateTracerProviderBuilder().AddAzureMonitorTraceExporter(...) path.
    (#​52720)

• Added handling of stable database client span semantic conventions
  (#​53050)

Commits viewable in compare view.

Updated Azure.Identity from 1.8.0 to 1.11.4.

Release notes

Sourced from Azure.Identity's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Identity.Client from 4.49.1 to 4.61.3.

Release notes

Sourced from Microsoft.Identity.Client's releases.

4.61.3

Bug Fixes

• Exclude the use of WSTrust for ROPC flow except for AAD authorities. See Issue #​4791

4.61.2

Bug Fixes

• Fixed a regression in MSAL 4.61.1 where Proof of Possession (POP) extensibility API was made available for all the confidential client scenarios caused runtime exception for users using higher level SDKs with explicit dependency on MSAL. See 4789
• Measurement of duration in milliseconds is now consistent across all platforms. See 4784

4.61.1

New Features

• Enabled Proof of Possession (POP) extensibility API for all confidential client requests, enhancing security measures for confidential clients. See 4757
• Introduced a public API that identifies and returns the current Azure environment for Managed Identity. See 4751
• Deprecated the WithClientAssertion(string) method. Developers are encouraged to use the overload with Func<AssertionRequestOptions, Task> instead, which ensures the return of a non-expired assertion, potentially including a Federated Credential. See 4775
• Adding support for Non-GUID Client IDs with AuthorityType.Generic See #​4686

Bug Fixes

• Improved logic to handle ADFS tokens that include a manually added tid claim, preventing exceptions. See 4608
• Improved build-time validation to ensure that applications using the WithBroker(true) method will fail at build time if the application targets net6-windows and uses an old broker API. This change prevents runtime failures and facilitates early detection of issues. See 4768
• Fixed token acquisition failure in broker based flow when authority is common. See 4696

4.61.0

4.61.0

New Features

• Removed support for deprecated frameworks, Xamarin.Android 12 and Xamarin.iOS 10. MSAL.NET packages will no longer include monoandroid12.0 and xamarinios10 binaries. Existing applications should migrate to modern frameworks like .NET MAUI. See 4715 and Announcing the Upcoming Deprecation of MSAL.NET for Xamarin and UWP.
• Removed support for UWP. MSAL.NET packages will no longer include uap10.0.17763 binary. Existing applications should migrate to modern frameworks like WinUI 3. See 4717 and Announcing the Upcoming Deprecation of MSAL.NET for Xamarin and UWP.
• Removed Windows Forms dependency from Microsoft.Identity.Client, which will no longer include net6.0-windows7.0 binary. Existing desktop applications targeting net6.0-windows should reference Microsoft.Identity.Client.Broker when using interactive authentication with Windows Broker and call WithBroker(BrokerOptions); or reference Microsoft.Identity.Client.Desktop when authenticating with browser and call WithWindowsEmbeddedBrowserSupport(). There are no changes to the usage of the system browser. See 4468.
• Re-enabled the use of SHA 256 and PSS padding to create client assertions. See 4695.

Bug Fixes

• Public methods in Kerberos TicketCacheWriter and TicketCacheReader were corrected to be internal. Public API in KerberosSupplementalTicketManager should be used. See #​4726.

4.60.3

Bug Fixes

Updated Android webview attribute.

4.60.2

Bug Fixes

When OnBeforeTokenRequest extensibility API is used, MSAL now correctly uses the user-provided OnBeforeTokenRequestData.RequestUri to set the token request endpoint. See 4701.

4.60.1

Addressed an issue where attempts to acquire a token via certificate authentication resulted in a Microsoft.Identity.Client.MsalServiceException (Error code: AADSTS5002730), signaling an "Invalid JWT token. Unsupported key for the signing algorithm." This was due to a known bug in Microsoft Entra ID (Azure AD) that affects the handling of JWT tokens signed with certain algorithms, specifically SHA2 and PSS. See 4690

4.60.0

New Features

• AAD client assertions are computed using SHA 256 and PSS padding. See 4428
• CorrelationId is available in MsalException. See 4187
• Open telemetry records telemetry for proactive token refresh background process. See 4492
• MSAL.Net now supports generic authorities with query parameters. See 4631

Bug Fixes

• MSAL.Net now logs an error when OBO is performed over common or organizations. See 4606
• MSAL.Net now handles the v2.0 authorization endpoint. See 4416
• Improved logging and error message when the web api received claims challenge. See 4496
• Cloud shell error message from the managed identity endpoint is parsed correctly. See 4402
• Improved error message when CCA certificate is disposed before MSAL can use it. See 4602
• Client id is now accepted as a scope. See 4652

4.59.1

Bug Fixes

Updated Android webview attribute.

4.59.0

New Features

• Removed support for deprecated Xamarin.Android 9 and Xamarin.Android 10 frameworks. MSAL.NET packages will no longer include monoandroid90 and monoandroid10.0 binaries and instead include monoandroid12.0. Xamarin.Android apps should now target framework version 12 (corresponding to Android API level 31) or above. See 3530.
• Removed support for deprecated .NET 4.5 framework. MSAL.NET packages will no longer include net45 binary. Existing applications should target at least .NET 4.6.2. See 4314.

Bug Fixes

• When public client apps persist cache data on Linux platforms, exceptions are now thrown, instead of just logged. This behavior is now consistent with Windows and Mac cache accessors. See 4493.
• Downgraded System.Diagnostics.DiagnosticSource dependency to 6.0.1 from 7.0.2 to enable apps to run in .NET 6 in-process Azure Functions. Added extra checks to prevent crashing if OpenTelemetry dependencies cannot be used in the app's runtime. See 4456.
• MSAL now throws MsalServiceException instead of MsalManagedIdentityException in managed identity flows. See 4483.
• Background proactive token refresh operation can now be cancelled using the cancelation token passed into the parent acquire token call. See 4473.
• Fixed SemaphoreFullException happening in managed identity flows. See 4472.
• Improved exception messages when using non-RSA certificates. See 4407.
• Fixed a scenario when the same tokens are cached under different cache keys when an identity provider sends scopes in a different order. See 4474.

4.58.1

New Features

• Added WithForceRefresh support for silent flows using the Windows broker. See 4457.

Bug Fixes

• Fixed a bug when a x-ms-pkeyauth HTTP header was incorrectly sent on Mac and Linux platforms. See 4445.
• Fixed an issue with client capabilities and claims JSON not being merged correctly. See 4447.
• MSAL can now be used in .NET 8 applications which use native AOT configuration binder source generator. See 4453.
• Fixed an issue with sending an incorrect operating system descriptor in silent flows on Mac. See 4444.

4.58.0

New Features

• Removed support for deprecated .NET 4.6.1 framework and added .NET 4.6.2 support. MSAL.NET packages will no longer include net461 binary. Existing .NET 4.6.1 apps will now reference .NET Standard 2.0 MSAL binary. See 4315.
• MSAL.NET repository now supports Central Package Management. See 3434.
• Added instrumentation to collect metrics with Open Telemetry. Aggregated metrics consist of successful and failed token acquisition calls, total request duration, duration in cache, and duration in a network call. See 4229.

Bug Fixes

• Resolved the issue with dual-headed accounts that share the same UPN for both, Microsoft (MSA) and Microsoft Entra ID (Azure AD) accounts. See 4425.
• MSAL now correctly falls back to use local cache if broker fails to return a result for AcquireTokenSilent calls. See 4395.
• Fixed a bug when the cache level in the telemetry was not correctly set to L1 Cache when in-memory cache was used. See 4414.
• Deprecated WithAuthority on the request builders. Set the authority on the application builders. Use WithTenantId or WithTenantIdFromAuthority on the request builder to update the tenant ID. See 4406.
• Fixed an issue with the Windows broker dependencies when the app was targetting NativeAOT on Windows. See 4424.
• Updated Microsoft.Identity.Client.NativeInterop reference to version 0.13.14, which includes bug fixes and stability improvements. See 4439.

4.57.0

New Features

• Removed support for deprecated .NET Core 2.1 framework. MSAL.NET packages will no longer include netcoreapp2.1 binary. Existing .NET Core 2.1 apps will now reference .NET Standard 2.0 MSAL binary. See 4313.
• Added additional logging in the cache. See 3957.
• Removed unused HTTP telemetry data (x-client-info). See 4167.
• Updated Microsoft.Identity.Client.NativeInterop reference to version 0.13.12, which includes bug fixes and stability improvements. See 4374.

Bug Fixes

• Added simple retry logic for signing client assertions failures. See 4366.
• Fixed inconsistencies in throwing exceptions for badly formatted authorities. Now MSAL will always throw an ArgumentException if an authority is in incorrect format (e.g., doesn't start with HTTPS, has spaces, etc.) See 4280.
• Included missing Windows broker-related exception data when serializing MSAL exceptions. See 4371.
• Fixed a crash when using managed identity and provided resource is null. See 4332.
• Removed duplicate Windows broker logs. See 4353.

4.56.0

New Features

• MSAL.NET cache extensions (Microsoft.Identity.Client.Extensions.Msal) package has been moved to the main MSAL.NET repository (where any new issues should be created). The package version has been increased to match the main MSAL version. Along with this move, support for .NET 4.5 and .NET Core 3.1 was removed and this package now only supports .NET Standard 2.0. Additionally, Microsoft.Identity.Client.Extensions.Adal has been deprecated. See 3152, 4330.
• Added AuthenticationResult.AuthenticationResultMetadata.Telemetry that currently contains telemetry from the Windows broker (WAM). See 4159.

Bug Fixes

• Added throttling logic for acquiring tokens for managed identity (using AcquireTokenForManagedIdentity and WithAppTokenProvider) to prevent the throttling exceptions thrown by the managed identity endpoints. See 4196.
• Enabled cache synchronization by default. This helps to keep the cache consistent when a singleton confidential client application (CCA) is used with enabled external token cache serialization. The cache synchronization has a negligible performance effect when CCA is created per request. See 4268.
• Fixed an authority validation error in interactive flows when an Active Directory Federation Services (ADFS) authority with a tenant ID was used. See 4272.
• Added clarity to the Windows broker logs. See 4318.

4.55.0

New Features

• A user assigned managed identity can now be specified using its object ID. 4215.

Bug Fixes

• WithTenantId now works with CIAM authorities. See 4191.
• Improved the error message when cache serialization fails. See 4206.
• Improved logging when using the Windows broker (WAM). See 4183.

4.54.1

New Features

• The client-side telemetry API (ITelemetryClient) is now generally available. See 3784.
• Added WithSearchInCacheForLongRunningProcess() modifier which allows InitiateLongRunningProcessInWebApi method to search in cache. This flag is intended only for rare legacy cases; for most cases, rely on the default behavior of InitiateLongRunningProcessInWebApi and AcquireTokenInLongRunningProcess. See 4124.

Bug Fixes

• WithTenantId can now be used with dSTS authorities to overwrite the tenant. See 4144, 4145.
• Fixed a bug in token serialization for rare cases when an ID token has no oid claim. See 4140.

4.54.0

New Features

• Acquiring tokens with managed identity is now generally available. See 4125 and documentation for managed identity in MSAL.NET.
• Updated the managed identity API to specify the identity type when creating an ManagedIdentityApplication. See 4114.
• When acquiring tokens with managed identity and using the default HTTP client, MSAL will retry the request for certain exception codes. See 4067.
• Adds MsalManagedIdentityException class that represents any managed identity related exceptions. It includes general exception information including the Azure source from which the exception originates. See 4041.
• MSAL will now proactively refresh tokens acquired with managed identity. See 4062.
• MSAL will now proactively refresh tokens acquired using AppTokenProvider API. See 4074.
• MsalException and derived exception classes now have a property AdditionalExceptionData, which holds any extra error information. Currently it is only populated for exceptions coming from the Windows authentication broker (WAM). See 4106.
• For HTTP telemetry. added a new telemetry ID for long-running on-behalf-of requests. See 4099.

Bug Fixes

• Fixed a JSON serialization issue in iOS apps that are built in release Ahead-Of-Time (AOT) compilation mode. See 4082.
• MSAL.NET package now references correct Microsoft.iOS version. See 4091.
• Microsoft.Identity.Client.Broker package can now be used in projects which rely on the older package.config. See 4108.
• Fixed a user_mismatch error when WithAccount is specified when acquiring tokens interactively and selecting a different account in the account picker. See 3991.

4.53.0

New Features

• Added support for CIAM authorities. See 3990

Bug Fixes

• Fixed issue where WAM is invoked for B2C authorities. MSAL will now fall back to the browser for this scenario. See 4072

4.52.0

New Features

• The improved experience using Windows broker (WAM) is now generally available for all desktop platforms, except UWP. See 3375, 3447.
• Acquiring Proof-of-Possession tokens on public desktop clients using WAM broker is now generally available. See 3992.
• The requirement for a specific Windows SDK version on .NET 6 platform has been removed, which should improve the package usage on .NET 6 platforms. MSAL.NET now targets a more general net6.0-windows instead of net6.0-windows10.0.17763.0. See 3986.
• Added support for non-Azure AD IdP's in client credential flows. Use WithGenericAuthority(authority). This is still an experimental API and may change in the future. See 4047, 1538.
• Added AuthenticationResult.AdditionalResponseParameters property bag with any extra parameters from the AAD response. This collection will also have spa_accountId parameter which can be used in brokered hybrid single-page application (SPA) scenarios. See 3994.

4.51.0

New Features

• Simplified managed identity API. Use ManagedIdentityApplicationBuilder to create a IManagedIdentityApplication and call AcquireTokenForManagedIdentity. See 3970 and wiki.
• Added StopLongRunningProcessInWebApiAsync which allows to remove cached tokens based on a long-running OBO key. See 3346 and wiki.

Bug Fixes

• InitiateLongRunningProcessInWebApi will now always acquire new tokens from AAD without checking the token cache first. See 3825.
• When using preview Windows broker, MSAL will correctly handle the transitive reference to Microsoft.Identity.Client.NativeInterop. Any explicit references to Microsoft.Identity.Client.NativeInterop in projects also referencing MSAL should be removed. See 3964.
• Fixed preview Windows broker throwing a signed out exception when calling AcquireTokenSilent after acquiring token using the Username/Password flow. See 3916 and See 3961.

4.50.0

New Features

• Extended managed identity experimental functionality with support for Azure Cloud Shell. See 3832.
• Added support for PII logging for WAM preview. See 3845, 3822.

Bug Fixes

• Fixed JSON serialization issues for apps running on .NET 7. See 3892.
• Improved logging performance to only create logs when a specified log level is enabled. See 3901.
• Fixed Unable to load DLL 'msalruntime' exception for apps that use WAM preview and are packaged as MSIX. See 3740.
• WAM preview now honors the login hint. See 3301 and WAM docs.
• WAM preview now allows to sign in with an account different from the provided login hint. See 3929.
• Fixed an ApiContractViolation exception in WAM preview when signing out. See 3685.
• MSAL now allows passing no scopes when using WAM preview. See 3675.
• When broker is enabled, MSAL will now use the refresh token from the broker instead of a locally cached one. See 3613.
• Added a more descriptive error message when combined flat user and app cache is used. Use a partitioned token cache (for ex. distributed cache like Redis) or separate files for app and user token caches. See 3218.
• Updated logs to clarify that managed identity correlation ID differs from MSAL one. See #​3908.
• Fixed an occasional cryptographic exception by removing the RSA public key size check - AAD is better suited to handle this verification. See 3896.
• Fixed JSON parsing errors when receiving an error token response. See 3883.
• Added better error handling when receiving WS-Trust responses. See 3614.
• WithAuthority methods on the request builders are hidden. Use either WithTenantId on the request builders or WithAuthority only on the application builder. See #​2929.
• Deprecated IsBrokerAvailable method on mobile platforms. Applications should rely on the library automatically falling back to a browser if the broker is not available. See 3320.
• Deprecated unused extended expiry API. See 1377.

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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.