NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet · #1990 most downloaded on NuGet
Microsoft Azure WebJobs SDK EventHubs Extension
Last release 29 days ago
09 Sep 2026
Release timing varies
gaps range from 3 weeks to 11 months
Most releases are documented
notes for 26 of 39 stable releases
Nothing withdrawn
no release was ever pulled
9 years old
46 releases · first in 2017
Fixed an issue where the checkpoint store's BlobServiceClient was constructed using the hard-coded core.windows.net suffix when AzureWebJobsStorage__a
BlobServiceClient was constructed using the hard-coded core.windows.net suffix when AzureWebJobsStorage__accountName was set, even if an explicit AzureWebJobsStorage__blobServiceUri was also present. The explicit __blobServiceUri is now preferred over __accountName, and an optional __endpointSuffix setting is honored when constructing the URI from __accountName. This unblocks Event Hub triggers that use managed-identity storage in sovereign clouds (e.g. Azure US Government, Azure China). (#57543)LogFunctionScaleWarning extension method to enable Scale Controller App Insights diagnostics.net10.0 target and updated .NET runtime dependencies to the 10.x line. The package now targets net10.0, net8.0, and netstandard2.0.Microsoft.Extensions.Hosting package reference.One column per quarter.
Fixed an issue where a legacy ownership record without checkpoint data was interpreted as a valid checkpoint and used to initialize a partition when n
Fixed a bug where the data types of broker-owned properties were being adjusted when an event was read by the client, causing the underlying AMQP data
EventData projection.Updated the Microsoft.Azure.Amqp dependency to 2.7.0, which contains several bug fixes and adds support for AOT. (see: commits)
Added a compatibility hack to the binding data associated with the trigger to preserve the previous service behavior of Offset being a valid numeric value. As this data is not local to the trigger context and is surfaced upstream, the change in service behavior for GeoDR namespaces caused issues with some custom language workers making invalid assumptions about the string-based offset format. To work around this, the Offset is being populated with OffsetString if it can be parsed as a number. In the case that OffsetString is not a valid numeric value, it will default to -1 which would position readers at the beginning of the stream, causing duplicates but preventing data loss. A key for OffsetString was added that reflects the actual offset returned by the service in all scenarios.
Fixed a bug which caused the placeholder value used to represent missing offsets in v5.11.3 - v5.11.6 to not be properly detected and incorrectly used
Support for the Event Hubs geographic data replication feature has been enabled. As part of this feature, the type of offset-related data has been cha
Support for the Event Hubs geographic data replication feature has been enabled. As part of this feature, the type of offset-related data has been changed from long to string to align with changes to the Event Hubs service API. To preserve backwards compatibility, the existing offset-related members have not been changed, and new members with names similar to OffsetString and string-based parameters for method overloads have been introduced.
The long-based offset members will continue to work for Event Hubs namespaces that do not have GeoDR replication enabled, but are discouraged for use and have been marked as obsolete.
Bump dependency on Azure.Messaging.EventHubs to 5.11.5.
Azure.Messaging.EventHubs to 5.11.5.When the trigger's connection property is set to a valid connection string instead of an informational name, the mistake will be detected and sensitiv
To mitigate a vulnerability, updating the transitive dependency for Azure.Identity to v1.11.4 via version bump to Microsoft.Extensions.Azure.
Azure.Identity to v1.11.4 via version bump to Microsoft.Extensions.Azure.Fixed an issue with scale metrics computation, potentially causing unnecessary scale-up.
To mitigate a disclosure vulnerability, updating the transitive dependency for Azure.Identity to v1.11.1 via version bump to Microsoft.Extensions.Azur…
Azure.Identity to v1.11.1 via version bump to Microsoft.Extensions.Azure.Added a new setting to EventHubOptions to allow checkpointing to be disabled for applications that always want to use their initialOffsetOptions when
EventHubOptions to allow checkpointing to be disabled for applications that always want to use their initialOffsetOptions when starting to process a new partition.Adjusted checkpointing logic to no longer write a checkpoint when the listener is shutting down. This was necessary to prevent potential data loss fro
Adjusted checkpointing logic to no longer write a checkpoint when the listener is shutting down. This was necessary to prevent potential data loss from occurring when shutting down Function retries. Because the trigger cannot know if the Function host would have retried a failure if it were not shutting down, we cannot assume that it is safe to checkpoint. This change ensures that the batch of events being processed when shut down was requested will be retried by another instance or the next time the Function app is run.
Updated the Azure.Messaging.EventHubs, which includes a new build of the AMQP transport library. The notable bug fix addresses an obscure race condition when a cancellation token is signaled while service operations are being invoked concurrently which caused those operations to hang.
The SystemProperties binding will now return certain item as string values instead of an AMQP structure that requires calling ToString() to read. The
The SystemProperties binding will now return certain item as string values instead of an AMQP structure that requires calling ToString() to read. The affected system properties are:
Avoid race condition when determining whether to checkpoint when the host is in the process of shutting down.
Azure.Messaging.EventHubs dependency, which includes optimized defaults of the host platform to be used for AMQP buffers. This offers non-trivial performance increase on Linux-based platforms and a minor improvement on macOS. This update also enables support for TLS 1.3.Bump dependency on Microsoft.Extensions.Azure to prevent transitive dependency on deprecated version of Azure.Identity.
Microsoft.Extensions.Azure to prevent transitive dependency on deprecated version of Azure.Identity.Added support for the legacy checkpoint format when making scaling decisions.
We recommend testing to ensure no breaking changes are introducing to your function app before updating existing applications to version 6.0.0 or newe…
The default batch size has changed to 100 events. Previously, the default batch size was 10.
This setting represents the maximum number of events from Event Hubs that the function can receive when it's invoked. The decision to change the default was based on developer feedback, testing, and a desire to match the defaults used by the Azure SDK for Event Hubs. This change will be beneficial to the average scenario by helping to improve performance as well as lower costs due to fewer function executions.
We recommend testing to ensure no breaking changes are introducing to your function app before updating existing applications to version 6.0.0 or newer of the Event Hubs extension, especially if you have code code that was written to expect 10 as the max event batch size.
When binding to a CancellationToken, the token will no longer be signaled when in Drain Mode. To detect if the function app is in Drain Mode, use depe
CancellationToken, the token will no longer be signaled when in Drain Mode.
To detect if the function app is in Drain Mode, use dependency injection to inject the
IDrainModeManager, and check the IsDrainModeEnabled property. Additionally, checkpointing
will now occur when the function app is in Drain Mode.Added support for binding to EventData with the Event Hubs trigger in Functions using the isolated process model.
EventData with the Event Hubs trigger in Functions using the isolated process model.Fixed a race condition when Function instances are scaling that could cause a checkpoint to be written before the Function code was invoked to process events. This would result in the new owner for the partition skipping those events causing them to go unprocessed.
Fixed an issue that could cause the trigger to miss that a cancellation token has been signaled, slowing down responsiveness to scaling and shutdown.
It is now possible to configure a desired minimum for the number of events included in each batch that the trigger build and how long the trigger shou
It is now possible to configure a desired minimum for the number of events included in each batch that the trigger build and how long the trigger should wait while trying to a batch of that size. This is intended to help control costs by having the trigger invoke the Function fewer times, but with more events in each batch.
It is important to note that neither the minimum batch size or maximum wait time are guarantees; the trigger will make its best effort to honor them but you may see partial batches or inaccurate timing. This scenario is common when a Function is scaling.
Code | Docs
Support: Active
Text Authoring
Azure.AI.Language.Text.Authoring
Added the an overload for IAsyncCollector allowing a partition key to be specified. Because IAsyncCollector is owned by the Functions runtime, this me
Added the an overload for IAsyncCollector<EventData> allowing a partition key to be specified. Because IAsyncCollector<T> is owned by the Functions runtime, this method could not be directly added. Instead, this has been implemented as an extension method within the Event Hubs extension package. Unfortunately, this knowingly makes the overload unable to be mocked.
Target-based scaling support has been added, allowing instances for Event Hubs-triggered Functions to more accurately calculate their scale needs and adjust more quickly as the number of events waiting to be processed changes. This will also reduce duplicate event processing as the instance count changes.
A new setting, UnprocessedEventThreshold, has been added to help tune target-based scaling. More details can be found in the host.json documentation.
eventHubName that does not match the one that appears as EntityPath in the connection string would throw. The behavior now follows that of other clients and gives precedence to the entity path in the connection string.Fixed a bug in the runtime scale controller that could result in a null reference exception when encountering a null checkpoint. Also, correct the ass
Fixed a bug in the runtime scale controller that prevented function apps from scaling in.
Adding support for retry policy (SupportsRetryAttribute)
Cancel function execution after partition ownership is lost.
General availability of Microsoft.Azure.WebJobs.Extensions.EventHubs 5.0.0.
Code | Docs
Support: Active
Event Grid Namespaces
Azure.Messaging.EventGrid.Namespaces
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Functions Extensions - WebPubSub
Code | Docs
Support: Active
Functions Extensions - WebPubSub
Microsoft.Azure.Functions.Worker.Extensions.WebPubSub
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →