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 5524df3220..60384a3ae9 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
@@ -14,3 +14,72 @@ This page documents API and behavior changes that have the potential to break ex
- [Breaking changes in EF Core 8](xref:core/what-is-new/ef-core-8.0/breaking-changes)
- [Breaking changes in EF Core 7](xref:core/what-is-new/ef-core-7.0/breaking-changes)
- [Breaking changes in EF Core 6](xref:core/what-is-new/ef-core-6.0/breaking-changes)
+
+## Summary
+
+| **Breaking change** | **Impact** |
+|:----------------------------------------------------------------------------------------------------------|------------|
+| [ExecuteUpdateAsync now accepts a regular, non-expression lambda](#ExecuteUpdateAsync-lambda) | Low |
+
+## Low-impact changes
+
+
+
+### ExecuteUpdateAsync now accepts a regular, non-expression lambda
+
+[Tracking Issue #32018](https://github.com/dotnet/efcore/issues/32018)
+
+#### Old behavior
+
+Previously, accepted an expression tree argument (`Expression>`) for the column setters.
+
+#### New behavior
+
+Starting with EF Core 10.0, now accepts a non-expression argument (`Func<...>`) for the column setters. If you were building expression trees to dynamically create the column setters argument, your code will no longer compile - but can be replaced with a much simpler alternative (see below).
+
+#### Why
+
+The fact that the column setters parameter was an expression tree made it quite difficult to do dynamic construction of the column setters, where some setters are only present based on some condition (see Mitigations below for an example).
+
+#### Mitigations
+
+Code that was building expression trees to dynamically create the column setters argument will need to be rewritten - but the result will be much simpler. For example, let's assume we want to update a Blog's Views, but conditionally also its Name. Since the setters argument was an expression tree, code such as the following needed to be written:
+
+```c#
+// Base setters - update the Views only
+Expression, SetPropertyCalls>> setters =
+ s => s.SetProperty(b => b.Views, 8);
+
+// Conditionally add SetProperty(b => b.Name, "foo") to setters, based on the value of nameChanged
+if (nameChanged)
+{
+ var blogParameter = Expression.Parameter(typeof(Blog), "b");
+
+ setters = Expression.Lambda, SetPropertyCalls>>(
+ Expression.Call(
+ instance: setters.Body,
+ methodName: nameof(SetPropertyCalls.SetProperty),
+ typeArguments: [typeof(string)],
+ arguments:
+ [
+ Expression.Lambda>(Expression.Property(blogParameter, nameof(Blog.Name)), blogParameter),
+ Expression.Constant("foo")
+ ]),
+ setters.Parameters);
+}
+
+await context.Blogs.ExecuteUpdateAsync(setters);
+```
+
+Manually creating expression trees is complicated and error-prone, and made this common scenario much more difficult than it should have been. Starting with EF 10, you can now write the following instead:
+
+```c#
+await context.Blogs.ExecuteUpdateAsync(s =>
+{
+ s.SetProperty(b => b.Views, 8);
+ if (nameChanged)
+ {
+ s.SetProperty(b => b.Name, "foo");
+ }
+});
+```
diff --git a/entity-framework/core/what-is-new/ef-core-10.0/whatsnew.md b/entity-framework/core/what-is-new/ef-core-10.0/whatsnew.md
index e929c4b7d2..dcc6fecb37 100644
--- a/entity-framework/core/what-is-new/ef-core-10.0/whatsnew.md
+++ b/entity-framework/core/what-is-new/ef-core-10.0/whatsnew.md
@@ -31,3 +31,48 @@ EF10 requires the .NET 10 SDK to build and requires the .NET 10 runtime to run.
* Translation for DateOnly.ToDateTime(timeOnly) ([#35194](https://github.com/dotnet/efcore/pull/35194), contributed by [@mseada94](https://github.com/mseada94)).
* Optimization for multiple consecutive `LIMIT`s ([#35384](https://github.com/dotnet/efcore/pull/35384)), contributed by [@ranma42](https://github.com/ranma42)).
* Optimization for use of `Count` operation on `ICollection` ([#35381](https://github.com/dotnet/efcore/pull/35381)), contributed by [@ChrisJollyAU](https://github.com/ChrisJollyAU)).
+
+## ExecuteUpdateAsync now accepts a regular, non-expression lambda
+
+The can be used to express arbitrary update operations in the database. In previous versions, the changes to be performed on the database rows were provided via an expression tree parameter; this made it quite difficult to build those changes dynamically. For example, let's assume we want to update a Blog's Views, but conditionally also its Name. Since the setters argument was an expression tree, code such as the following needed to be written:
+
+```c#
+// Base setters - update the Views only
+Expression, SetPropertyCalls>> setters =
+ s => s.SetProperty(b => b.Views, 8);
+
+// Conditionally add SetProperty(b => b.Name, "foo") to setters, based on the value of nameChanged
+if (nameChanged)
+{
+ var blogParameter = Expression.Parameter(typeof(Blog), "b");
+
+ setters = Expression.Lambda, SetPropertyCalls>>(
+ Expression.Call(
+ instance: setters.Body,
+ methodName: nameof(SetPropertyCalls.SetProperty),
+ typeArguments: [typeof(string)],
+ arguments:
+ [
+ Expression.Lambda>(Expression.Property(blogParameter, nameof(Blog.Name)), blogParameter),
+ Expression.Constant("foo")
+ ]),
+ setters.Parameters);
+}
+
+await context.Blogs.ExecuteUpdateAsync(setters);
+```
+
+Manually creating expression trees is complicated and error-prone, and made this common scenario much more difficult than it should have been. Starting with EF 10, you can now write the following instead:
+
+```c#
+await context.Blogs.ExecuteUpdateAsync(s =>
+{
+ s.SetProperty(b => b.Views, 8);
+ if (nameChanged)
+ {
+ s.SetProperty(b => b.Name, "foo");
+ }
+});
+```
+
+Thanks to [@aradalvand](https://github.com/aradalvand) for proposing and pushing for this change (in [#32018](https://github.com/dotnet/efcore/issues/32018)).