Azure Functions 4.0 brings first-class .NET 6 support and the **Isolated Process Model** (out-of-process), which decouples your app from the Functions runtime version.
In-Process vs Isolated
| Feature | In-Process | Isolated (Recommended) |
|---|---|---|
| .NET Version Dependency | Tied to Host | Independent |
| Middleware | Limited | Full ASP.NET Core Middleware |
| Startup Performance | Faster | Slightly Slower (but improves) |
Creating Isolated Function
[Function("HttpTrigger")]
public HttpResponseData Run(
[HttpTrigger(AuthorizationLevel.Function, "get")] HttpRequestData req)
{
var response = req.CreateResponse(HttpStatusCode.OK);
response.WriteString("Hello from Isolated .NET 6!");
return response;
}
Key Takeaways
- Use Isolated for new projects—it’s the future.
- Gain custom middleware (e.g., for logging or auth).
Discover more from C4: Container, Code, Cloud & Context
Subscribe to get the latest posts sent to your email.