dotnet · roji · Jan 9, 2026 · Jan 8, 2026
diff --git a/entity-framework/core/providers/provider-log.md b/entity-framework/core/providers/provider-log.md
diff --git a/entity-framework/core/providers/writing-a-provider.md b/entity-framework/core/providers/writing-a-provider.md
@@ -26,12 +26,6 @@ The EF team produces "community standup" videos, where we discuss various aspect
 * [IQueryable, LINQ and the EF Core query pipeline](https://www.youtube.com/watch?v=1Ld3dtnTrMw&list=PLdo4fOcmZ0oX0ObHwBrJ0vJpZ7PiYMqeA)
 * [Model Building](https://www.youtube.com/watch?v=FYz0rAxQkC8&list=PLdo4fOcmZ0oX0ObHwBrJ0vJpZ7PiYMqeA)
 
-## Keeping up-to-date with provider changes
-
-Starting with work after the 2.1 release, we have created a [log of changes](xref:core/providers/provider-log) that may need corresponding changes in provider code. This is intended to help when updating an existing provider to work with a new version of EF Core.
-
-Prior to 2.1, we used the [`providers-beware`](https://github.com/dotnet/efcore/labels/providers-beware) and [`providers-fyi`](https://github.com/dotnet/efcore/labels/providers-fyi) labels on our GitHub issues and pull requests for a similar purpose. We will continue to use these labels on issues to give an indication which work items in a given release may also require work to be done in providers. A `providers-beware` label typically means that the implementation of a work item may break providers, while a `providers-fyi` label typically means that providers will not be broken, but code may need to be changed anyway, for example, to enable new functionality.
-
 ## Suggested naming of third party providers
 
 We suggest using the following naming for NuGet packages. This is consistent with the names of packages delivered by the EF Core team.

diff --git a/entity-framework/core/what-is-new/ef-core-11.0/provider-facing-changes.md b/entity-framework/core/what-is-new/ef-core-11.0/provider-facing-changes.md
@@ -10,6 +10,10 @@ uid: core/what-is-new/ef-core-11.0/provider-facing-changes
 
 This page documents noteworthy changes in EF Core 11 which may affect EF providers; none of these should affect end-users of EF - this page is only meant for EF provider maintainers. The list is maintained on a best-effort basis, some changes may be missing.
 
+## Changes
+
+* Collation names are now quoted in SQL, like column and table names ([see #37462](https://github.com/dotnet/efcore/issues/37462)). If your database doesn't support collation name quoting, override `QuerySqlGenerator.VisitSql()` and `MigrationsSqlGenerator.ColumnDefinition()` to revert to the previous behavior, but it's recommended to implement some sort of restricted character validation.
+
 ## Test changes
 
 * The inheritance specification tests have been reorganized into a folder of their own ([PR](https://github.com/dotnet/efcore/pull/37410)).
diff --git a/entity-framework/core/what-is-new/ef-core-3.x/breaking-changes.md b/entity-framework/core/what-is-new/ef-core-3.x/breaking-changes.md
@@ -9,7 +9,6 @@ uid: core/what-is-new/ef-core-3.x/breaking-changes
 # Breaking changes included in EF Core 3.x
 
 The following API and behavior changes have the potential to break existing applications when upgrading them to 3.x.
-Changes that we expect to only impact database providers are documented under [provider changes](xref:core/providers/provider-log).
 
 ## Summary
 

diff --git a/entity-framework/toc.yml b/entity-framework/toc.yml
@@ -456,8 +456,6 @@
         href: core/providers/in-memory/index.md
       - name: Write a database provider
         href: core/providers/writing-a-provider.md
-      - name: Provider-impacting changes
-        href: core/providers/provider-log.md
 
     - name: Tools & extensions
       href: core/extensions/index.md