diff --git a/aspnetcore/migration/70-80.md b/aspnetcore/migration/70-80.md
index 9e36ff743270..050b37e8b322 100644
--- a/aspnetcore/migration/70-80.md
+++ b/aspnetcore/migration/70-80.md
@@ -90,6 +90,7 @@ The following migration scenarios are covered:
 * [*New article*: HTTP caching issues during migration](#new-article-on-http-caching-issues)
 * [*New article*: New article on class libraries with static server-side rendering (static SSR)](#new-article-on-class-libraries-with-static-server-side-rendering-static-ssr)
 * [Discover components from additional assemblies](#discover-components-from-additional-assemblies)
+* [Drop `[Parameter]` attribute when the parameter is supplied from a query string](#drop-parameter-attribute-when-the-parameter-is-supplied-from-a-query-string)
 
 For guidance on adding Blazor support to an ASP.NET Core app, see <xref:blazor/components/integration#add-blazor-support-to-an-aspnet-core-app>.
 
@@ -523,6 +524,15 @@ For more information, see <xref:blazor/components/class-libraries-with-static-ss
 
 When migrating from a Blazor Server app to a Blazor Web App, access the guidance in <xref:blazor/fundamentals/routing#route-to-components-from-multiple-assemblies> if the app uses routable components from additional assemblies, such as component class libraries.
 
+### Drop `[Parameter]` attribute when the parameter is supplied from a query string
+
+The `[Parameter]` attribute is no longer required when supplying a parameter from the query string:
+
+```diff
+- [Parameter]
+  [SupplyParameterFromQuery]
+```
+
 ## Docker
 
 ### Update Docker images
diff --git a/aspnetcore/release-notes/aspnetcore-8.0.md b/aspnetcore/release-notes/aspnetcore-8.0.md
index 41226b4c8287..febdf1866391 100644
--- a/aspnetcore/release-notes/aspnetcore-8.0.md
+++ b/aspnetcore/release-notes/aspnetcore-8.0.md
@@ -329,6 +329,15 @@ The following articles document changes for Blazor Hybrid in .NET 8:
 * <xref:blazor/hybrid/index?view=aspnetcore-8.0&preserve-view=true#access-scoped-services-from-native-ui>: `BlazorWebView` gains a `TryDispatchAsync` method that calls a specified `Action<ServiceProvider>` asynchronously and passes in the scoped services available in Razor components. This enables code from the native UI to access scoped services such as `NavigationManager`.
 * <xref:blazor/hybrid/routing?view=aspnetcore-8.0&preserve-view=true&pivots=maui#get-or-set-a-path-for-initial-navigation>: Use the `BlazorWebView.StartPath` property to get or set the path for initial navigation within the Blazor navigation context when the Razor component is finished loading.
 
+### `[Parameter]` attribute is no longer required when supplied from the query string
+
+The `[Parameter]` attribute is no longer required when supplying a parameter from the query string:
+
+```diff
+- [Parameter]
+  [SupplyParameterFromQuery]
+```
+
 ## SignalR
 
 ### New approach to set the server timeout and Keep-Alive interval