●Change8

Migrating to Azure Functions v4.1038.100

Version v4.1038.100 introduces 2 breaking changes. This guide details how to update your code.

Released: 3/14/2025

2
Breaking Changes
2
Migration Steps
5
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

DefaultHttpProxyServiceHttpForwardingExceptionInvalidOperationExceptionCosmosDB trigger StartFromTime parameterScriptApplicationHostOptions

Breaking Changes

●Issue #1

The target framework for `WebJobs.Script` has been updated from .NET Standard 2.1 to .NET 8. If your project relies on compatibility layers provided by .NET Standard 2.1 that are not present in .NET 8, you may need to update your dependencies or code.

●Issue #2

The `DefaultHttpProxyService` now throws `HttpForwardingException` instead of `InvalidOperationException` when a `ForwarderError` occurs during client disconnection handling. Code catching `InvalidOperationException` specifically for this scenario must be updated to catch `HttpForwardingException`.

Migration Steps

  1. 1
    Review code that catches `InvalidOperationException` in HTTP forwarding scenarios and update it to catch `HttpForwardingException`.
  2. 2
    If targeting older frameworks, ensure compatibility when moving to the new .NET 8 target for `WebJobs.Script`.

Release Summary

This release focuses on enhancing observability through improved log forwarding and managed identity support, alongside several bug fixes related to binding parsing and worker stability. A key change is the migration of WebJobs.Script to target .NET 8.

Need More Details?

View the full release notes and all changes for Azure Functions v4.1038.100.

View Full Changelog