Skip to content

Latest commit

 

History

History
76 lines (53 loc) · 4.15 KB

File metadata and controls

76 lines (53 loc) · 4.15 KB

Release Notes

Stable Release 7.0.2 - 2026-06-24

This update brings the following changes since the 1.0.0 release of Microsoft.Data.SqlClient.Extensions.Azure.

Version alignment: Starting with this release, the package version is aligned with the core Microsoft.Data.SqlClient driver version (7.0.2). The previous release of this package was 1.0.0.

Breaking change (.NET Framework only): As part of this alignment, the assembly's AssemblyVersion changed from 1.0.0.0 to 7.0.0.0. On .NET Framework, AssemblyVersion is part of the strong-name identity, so applications that replace this assembly in an existing deployment without rebuilding must rebuild against 7.0.2 (or add a binding redirect). Applications on .NET / .NET Core are not affected.

Added

WAM broker support for Entra ID authentication (Windows only)

What Changed:

  • Added support for the Web Account Manager (WAM) broker for Microsoft Entra ID authentication flows. A new ActiveDirectoryAuthenticationProviderOptions options bag and a corresponding ActiveDirectoryAuthenticationProvider(ActiveDirectoryAuthenticationProviderOptions options) constructor were introduced, exposing a UseWamBroker property (alongside ApplicationClientId and DeviceCodeFlowCallback).
  • Added a cross-platform SetParentActivityOrWindowFunc(Func<object>?) method so callers can supply the parent window/activity used for interactive authentication UI — a window handle on Windows (where it also integrates with the WAM broker), or an Activity/UIViewController on Android/iOS. This supersedes the .NET Framework-only SetIWin32WindowFunc. (#4288, #4388)

Who Benefits:

  • Applications using ActiveDirectoryInteractive and other supported Entra ID authentication modes on Windows benefit from the WAM broker's improved security (tokens are brokered by the OS), single sign-on with the logged-in Windows account, and support for Conditional Access and Windows Hello.

Impact:

  • Enable the WAM broker by setting ActiveDirectoryAuthenticationProviderOptions.UseWamBroker to true and passing the options to the new constructor. Consider enabling it when you want OS-brokered token security, single sign-on with the signed-in Windows account, or support for Conditional Access and Windows Hello.
  • UseWamBroker is a Windows-only setting and has no effect on non-Windows platforms, where interactive Entra ID flows always use the system browser.
  • Prefer the new options-bag constructor over the positional-argument overloads in new code.
var options = new ActiveDirectoryAuthenticationProviderOptions
{
    ApplicationClientId = "<your-app-client-id>",
    UseWamBroker = true, // Windows only
};
var provider = new ActiveDirectoryAuthenticationProvider(options);
SqlAuthenticationProvider.SetProvider(SqlAuthenticationMethod.ActiveDirectoryInteractive, provider);
  • A new AzureSqlConnector sample demonstrating interactive Entra ID authentication with and without the WAM broker was added under doc/apps/AzureSqlConnector.

Changed

  • Updated Dependencies (#4288):
    • Added Microsoft.Identity.Client.Broker v4.84.2 (required for WAM broker support).
    • Updated Microsoft.Identity.Client to v4.84.2.

Target Platform Support

  • .NET Standard 2.0
  • .NET Framework 4.6.2+

Dependencies

.NET Standard 2.0

  • Azure.Core 1.51.1
  • Azure.Identity 1.18.0
  • Microsoft.Data.SqlClient.Extensions.Abstractions 7.0.2
  • Microsoft.Data.SqlClient.Internal.Logging 7.0.2
  • Microsoft.Extensions.Caching.Memory 8.0.1
  • Microsoft.Identity.Client 4.84.2
  • Microsoft.Identity.Client.Broker 4.84.2

.NET Framework 4.6.2+

  • Azure.Core 1.51.1
  • Azure.Identity 1.18.0
  • Microsoft.Data.SqlClient.Extensions.Abstractions 7.0.2
  • Microsoft.Data.SqlClient.Internal.Logging 7.0.2
  • Microsoft.Extensions.Caching.Memory 8.0.1
  • Microsoft.Identity.Client 4.84.2
  • Microsoft.Identity.Client.Broker 4.84.2