Moving Azure Functions to the isolated worker replaces HttpRequest with HttpRequestData

In the isolated worker model an HTTP trigger takes HttpRequestData and returns HttpResponseData rather than ASP.NET Core's HttpRequest and IActionResult, because the worker process does not host ASP.NET Core by default. ILogger comes from FunctionContext or constructor injection instead of a method parameter, and the FunctionName attribute becomes Function.

If you want the ASP.NET Core types back, add the worker's ASP.NET Core HTTP extensions package and call the web application configuration method in Program.cs. HttpRequest and IActionResult then work as before, model binding and the familiar result types return, and the request pipeline supports middleware. That integration is the recommended path when porting existing controller-shaped code, because it removes most of the per-function rewriting.

One HTTP model per project: mixing the built-in worker HTTP types and the ASP.NET Core integration in the same app is not supported, so decide before starting rather than converting functions piecemeal.