Bump the all-dependencies group with 10 updates by dependabot[bot] · Pull Request #698 · sebastienros/yessql

This is the general availability release of Microsoft.Data.SqlClient 7.0, a major milestone for the .NET data provider for SQL Server. This release addresses the most upvoted issue in the repository's history — extracting Azure dependencies from the core package — introduces pluggable SSPI authentication, adds enhanced routing for Azure SQL Hyperscale, and delivers async read performance improvements.

Also released as part of this milestone:

Released Microsoft.Data.SqlClient.Extensions.Abstractions 1.0.0. See release notes.
Released Microsoft.Data.SqlClient.Extensions.Azure 1.0.0. See release notes.
Released Microsoft.Data.SqlClient.Internal.Logging 1.0.0. See release notes.
Released Microsoft.Data.SqlClient.AlwaysEncrypted.AzureKeyVaultProvider 7.0.0. See release notes.

Changes Since 7.0.0-preview4

Added

Added actionable error message when Entra ID authentication methods are used without the Microsoft.Data.SqlClient.Extensions.Azure package installed, guiding users to install the correct package.
(#3962,
#4046)
Added Azure authentication sample application.
(#3988)

Changed

Other changes

Renamed the Microsoft.Data.SqlClient.Extensions.Logging package to Microsoft.Data.SqlClient.Internal.Logging to indicate it is for internal use only and should not be referenced directly by application code.
(#4038)
Fixed non-localized exception strings.
(#4022)
Codebase merge and cleanup:
(#3997,
#4052)
Various test improvements:
(#3891,
#3996,
#4002,
#4034,
#4041,
#4044)
Documentation improvements (including Entra ID branding updates):
(#4021,
#4047,
#4049)
Updated Dependencies
(#4045):
- Updated Azure.Core to v1.51.1
- Updated Azure.Identity to v1.18.0
  ... (truncated)

7.0.0-preview4

Changed

Azure Dependencies Removed from Core Package

What Changed:

The core Microsoft.Data.SqlClient package no longer depends on Azure.Core, Azure.Identity, or their transitive dependencies (e.g., Microsoft.Identity.Client, Microsoft.Web.WebView2). Azure Active Directory / Entra authentication functionality (ActiveDirectoryAuthenticationProvider and related types) has been extracted into a new Microsoft.Data.SqlClient.Extensions.Azure package that can be installed separately when needed. (#1108, #3680, #3902, #3904, #3908, #3917, #3982, #3978, #3986)
To support this separation, two additional packages were introduced: Microsoft.Data.SqlClient.Extensions.Abstractions (shared types between the core driver and extensions) and Microsoft.Data.SqlClient.Extensions.Logging (shared ETW tracing infrastructure). (#3626, #3628, #3967)

Who Benefits:

All users benefit from a significantly lighter core package. Previously, the Azure dependency chain pulled in numerous assemblies (including Azure.Core, Azure.Identity, Microsoft.Identity.Client, and Microsoft.Web.WebView2) even for applications that only needed basic SQL Server connectivity. This was the most upvoted open issue in the repository (#1108).
Users who do not use Azure AD authentication no longer carry Azure-related assemblies in their build output, reducing deployment size and eliminating confusion about unexpected dependencies.
Users who do use Azure AD authentication can now manage Azure dependency versions independently from the core driver.

Impact:

Applications using Azure AD authentication (e.g., ActiveDirectoryPassword, ActiveDirectoryInteractive, ActiveDirectoryDefault, etc.) must now install the Microsoft.Data.SqlClient.Extensions.Azure NuGet package separately. No code changes are required beyond adding the package reference.

Added

Expose SSPI Context Provider as Public API

What Changed:

Added the SspiContextProvider abstract class and a public SspiContextProvider property on SqlConnection, allowing applications to supply a custom SSPI context provider for integrated authentication. This enables custom Kerberos ticket negotiation and NTLM username/password authentication scenarios that the driver does not natively support. (#2253, #2494)

Who Benefits:

Users authenticating across untrusted domains, non-domain-joined machines, or cross-platform environments where configuring integrated authentication on the client is difficult or impossible.
Users running in containers who need manual Kerberos negotiation without deploying sidecars or external ticket-refresh mechanisms.
Users who need NTLM username/password authentication to SQL Server, which the driver does not provide natively.

Impact:

Applications can set a custom SspiContextProvider on SqlConnection before opening the connection. The provider handles the authentication token exchange during integrated authentication. This is an additive API — existing authentication behavior is unchanged when no custom provider is set. See SspiContextProvider_CustomProvider.cs for a sample implementation.
Note: The SspiContextProvider is a part of the connection pool key. Care should be taken when using this property to ensure the implementation returns a stable identity per resource.

Expose Default Transient Error List

What Changed:

Exposed the default transient error codes list via the new SqlConfigurableRetryFactory.BaselineTransientErrors static property (returns a ReadOnlyCollection<int>), making it easier to extend the set of transient errors without copy-pasting from the repository source. (#3903)

Who Benefits:

Developers implementing custom retry logic who want to extend the built-in transient error list rather than replacing it.

Impact:

... (truncated)

7.0.0-preview3

Preview Release 7.0.0-preview3.25342.7 - December 8, 2025

Added

Support for .NET 10

What Changed:

Updated pipelines and test suites to compile the driver using the .NET 10 SDK. Cleaned up unnecessary dependency references.
(#3686)

Who Benefits:

Developers targeting .NET 10.

Impact:

Addressed .NET 10 warnings regarding unused/unnecessary dependencies.

Enable SqlClientDiagnosticListener in SqlCommand on .NET Framework

What Changed:

Enabled SqlClientDiagnosticListener functionality on SqlCommand for .NET Framework.
(#3658)

Who Benefits:

Developers requiring diagnostic information on .NET Framework.

Impact:

Improved observability and diagnostics for SqlCommand on .NET Framework.

Enable User Agent Extension

What Changed:

Enabled User Agent Feature Extension.
(#3606)

Who Benefits:

Telemetry and diagnostics consumers.

Impact:

When the Switch.Microsoft.Data.SqlClient.EnableUserAgent app context switch is enabled, the driver sends more detailed user agent strings. This switch is disabled by default. This change will assist with troubleshooting and quantifying driver usage by version and operating system.

Fixed

... (truncated)

7.0.0-preview2

This update brings the following changes since the 7.0.0-preview1 release:

Bug Fixes

Fixed a debug assertion in connection pool (no impact to production code) (#3587)
Prevent uninitialized performance counters escaping CreatePerformanceCounters (#3623)
Fix SetProvider to return immediately if user-defined authentication provider found (#3620)
Allow SqlBulkCopy to operate on hidden columns (#3590)
Fix connection pool concurrency issue (#3632)

Added

App Context Switch for Ignoring Server-Provided Failover Partner

What Changed:

A new app context switch Switch.Microsoft.Data.SqlClient.IgnoreServerProvidedFailoverPartner was introduced to let the client ignore server-provided failover partner info in Basic Availability Groups (BAGs). When the switch is enabled, only the failover partner specified in the connection string is used; server-supplied partner values are skipped. This context switch was introduced in PR #3625.

Who Benefits:

Applications connecting to SQL Server BAGs using TCP and custom ports, especially where the server's provided partner name lacks the protocol, host, or port. This avoids connection failures when the server-provided partner is incompatible or incomplete.
Teams who manage availability groups and rely on client-side control of failover behavior in heterogeneous networking environments.

Impact:

If your environment might be affected (i.e., you operate a BAG with custom ports, or have experienced failures after failover), you can enable the new switch in your application:

AppContext.SetSwitch("Switch.Microsoft.Data.SqlClient.IgnoreServerProvidedFailoverPartner", true);

Then, ensure your connection string includes your preferred failover partner (with correct tcp:host,port) so that the client uses that instead of the server's suggestion.
Without enabling this, by default, the client continues to prefer the server-provided partner, maintaining backwards compatibility.

Other Additions

Add app context switch for enabling asynchronous multi-packet improvements (#3605)

Changed

Deprecation of `SqlAuthenticationMethod.ActiveDirectoryPassword`

What Changed:

Username/Password authentication for Microsoft Entra (formerly Active Directory) has been deprecated. SqlAuthenticationMethod.ActiveDirectoryPassword is now marked as [Obsolete]. This change occurred in PR #3671

Who benefits:

Teams moving toward stronger, passwordless or MFA-compliant auth (in line with changes across MSAL/Azure.Identity and Entra MFA enforcement). This aligns Microsoft.Data.SqlClient with Microsoft's direction to avoid username/password (ROPC) flows. See https://learn.microsoft.com/en-us/entra/identity/authentication/concept-mandatory-multifactor-authentication for more explanation of why this change is being made across Microsoft products/services.

... (truncated)

7.0.0-preview1

Changes Since 6.1.0

This update brings the following changes since the 6.1.0 release:

Breaking Changes

Removed Constrained Execution Region error handling blocks and associated SqlConnection cleanup which may affect how potentially-broken connections are expunged from the pool. (#3535)

Bug Fixes

Packet multiplexing disabled by default, and several bug fixes. (#3534, #3537)

Added

SqlColumnEncryptionCertificateStoreProvider now works on Windows, Linux, and macOS. (#3014)

Changed

Updated SqlVector.Null to return a nullable SqlVector instance in the reference API to match the implementation. (#3521)
Performance improvements for all built-in SqlColumnEncryptionKeyStoreProvider implementations. (#3554)
Various test improvements. (#3456, #2968, #3458, #3494, #3559, #3575)
Codebase merge project and related cleanup. (#3436, #3434, #3448, #3454, #3462, #3435, #3492, #3473, #3469, #3394, #3493, #3593)
Documentation improvements. (#3490)
Updated Azure.Identity dependency to v1.14.2. (#3538)

Changes Since 6.0.2

This update brings the following changes since the 6.0.2 release. Changes already noted above are omitted:

Additions

Added dedicated SQL Server vector datatype support

What Changed:

Optimized vector communications between MDS and SQL Server 2025, employing a custom binary format over the TDS protocol. (#3433, #3443)
Reduced processing load compared to existing JSON-based vector support.
Initial support for 32-bit single-precision floating point vectors.

Who Benefits:

Applications moving large vector data sets will see beneficial improvements to processing times and memory requirements.
Vector-specific APIs are ready to support future numeric representations with a consistent look-and-feel.

Impact:
... (truncated)

Commits viewable in compare view.

Updated Microsoft.Data.Sqlite from 10.0.2 to 10.0.5.

Release notes

Sourced from Microsoft.Data.Sqlite's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.SourceLink.GitHub from 10.0.102 to 10.0.201.

Release notes

Sourced from Microsoft.SourceLink.GitHub's releases.

10.0.201

You can build .NET 10.0 from the repository by cloning the release tag v10.0.201 and following the build instructions in the main README.md.