From 912ff998d2d3f6c3569e652606962da3ec96a834 Mon Sep 17 00:00:00 2001
From: Copilot <198982749+Copilot@users.noreply.github.com>
Date: Fri, 16 Oct 2026 10:43:15 -0700
Subject: [PATCH 1/2] Document SqlClient 6.1.6 dependency size impact in EF
Core 10 (#5486)
Co-authored-by: AndriySvyryd <6539701+AndriySvyryd@users.noreply.github.com>
---
.../ef-core-10.0/breaking-changes.md | 23 +++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git a/entity-framework/core/what-is-new/ef-core-10.0/breaking-changes.md b/entity-framework/core/what-is-new/ef-core-10.0/breaking-changes.md
index bff4e83ec0..25950e9d91 100644
--- a/entity-framework/core/what-is-new/ef-core-10.0/breaking-changes.md
+++ b/entity-framework/core/what-is-new/ef-core-10.0/breaking-changes.md
@@ -23,6 +23,7 @@ This page documents API and behavior changes that have the potential to break ex
| **Breaking change** | **Impact** |
|:--------------------------------------------------------------------------------------------------------------- | -----------|
| [EF tools now require framework to be specified for multi-targeted projects](#ef-tools-multi-targeting) | Medium |
+| [SQL Server: Microsoft.Data.SqlClient adds a broker dependency](#sqlclient-broker-dependency) | Low |
| [Application Name is now injected into the connection string](#sqlserver-application-name) | Low |
| [SQL Server json data type used by default on Azure SQL and compatibility level 170](#sqlserver-json-data-type) | Low |
| [Parameterized collections now use multiple parameters by default](#parameterized-collections) | Low |
@@ -83,6 +84,28 @@ You'll need to choose one of the frameworks (e.g., `net9.0`) when running the EF
## Low-impact changes
+
+
+### SQL Server: Microsoft.Data.SqlClient adds a broker dependency
+
+#### Old behavior
+
+Earlier versions of Microsoft.Data.SqlClient did not depend on Microsoft.Identity.Client.Broker.
+
+#### New behavior
+
+Microsoft.Data.SqlClient 6.1.6 introduces a dependency on Microsoft.Identity.Client.Broker, which is required for Microsoft Entra ID authentication and can drastically increase the size of the published application when using the EF Core SQL Server provider.
+
+#### Why
+
+The additional dependency is introduced by Microsoft.Data.SqlClient, rather than EF Core itself.
+
+#### Mitigations
+
+If your application doesn't use Microsoft Entra ID authentication, explicitly reference Microsoft.Data.SqlClient 7.1.x in your project to override the version used by EF Core. Starting with version 7.0, Microsoft.Data.SqlClient no longer includes Azure/Entra ID authentication dependencies in its core package.
+
+For details, including the additional package required for Entra ID authentication, see [Microsoft.Data.SqlClient has been updated to 7.0](xref:core/what-is-new/ef-core-11.0/breaking-changes#sqlclient-7).
+
### Application Name is now injected into the connection string
From b8216e48aeb4a8828cd378939a45e77798de64b3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jiri=20Cincura=20=E2=86=B9?=
Date: Fri, 16 Oct 2026 19:44:56 +0200
Subject: [PATCH 2/2] Fix absolute link. (#5487)
---
entity-framework/core/managing-schemas/migrations/teams.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/entity-framework/core/managing-schemas/migrations/teams.md b/entity-framework/core/managing-schemas/migrations/teams.md
index 71ab94eb6e..cee36f9de9 100644
--- a/entity-framework/core/managing-schemas/migrations/teams.md
+++ b/entity-framework/core/managing-schemas/migrations/teams.md
@@ -60,7 +60,7 @@ dotnet ef migrations script --idempotent -o artifacts/migrate.sql
Note that idempotent scripts depend on provider support. For example, SQLite doesn't currently support generating them; in that case generate a versioned script pair instead.
-Use Azure DevOps [approvals and gates](https://learn.microsoft.com/azure/devops/pipelines/process/approvals) (or the equivalent in your CI system) to hold the deployment until a reviewer signs off on the exact SQL:
+Use Azure DevOps [approvals and gates](/azure/devops/pipelines/process/approvals) (or the equivalent in your CI system) to hold the deployment until a reviewer signs off on the exact SQL:
```yaml
stages: