Generally Available: SDK type bindings in Azure Functions

Azure Functions triggers and bindings enable function authors to easily integrate event and data sources. Today, function apps on the isolated worker model can leverage general availability support for an expanded range of types, such as those from the Azure SDK for .NET. Now, a .NET function in an isolated worker process could, for example, start with a [BlobClient](https://learn.microsoft.com/en-us/dotnet/api/azure.storage.blobs.blobclient?view=azure-dotnet) passed into it. Using that type, the function can stream data incrementally and process larger blobs than it could before. Some workloads may see throughput improvements as well. Function authors should be aware that if a binding expression relies on trigger data, the trigger itself cannot be one of the newly supported types. Support covers the extensions for Blobs, Queues, Tables, Cosmos DB, Event Hubs, Event Grid, and Service Bus. Support for the Service Bus trigger does not yet cover message settlement scenarios, but this general availability update does enable use of \`ServiceBusReceivedMessage\`. You can learn more about this support from the [documentation](https://learn.microsoft.com/azure/azure-functions/dotnet-isolated-process-guide#sdk-types). * Azure functions * Features * SDK and Tools * [ Azure functions](https://azure.microsoft.com/en-gb/products/functions/)