{"id":1155,"date":"2021-05-28T13:00:44","date_gmt":"2021-05-28T20:00:44","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/azure-sdk\/?p=1155"},"modified":"2021-10-28T11:24:24","modified_gmt":"2021-10-28T18:24:24","slug":"introducing-the-new-azure-function-extension-libraries-beta","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/azure-sdk\/introducing-the-new-azure-function-extension-libraries-beta\/","title":{"rendered":"Introducing the new Azure Function Extension Libraries **Beta**"},"content":{"rendered":"

10\/28\/21 Update – We are pleased to announce that the libraries discussed below are now GA!<\/strong><\/span><\/p>\n

We are pleased to announce the release of beta versions for Storage<\/a>, Event Hubs<\/a>, Service Bus<\/a>, and Event Grid<\/a> Functions extensions, following the new Azure SDK guidelines<\/a>. This post will highlight a few new features of the libraries. We encourage you to try out the libraries and provide feedback before they go GA!<\/p>\n

New Features<\/h2>\n

Secretless configuration<\/h2>\n

Storage, Event Hubs, and Service Bus extensions now support secretless configuration via Azure Active Directory. This allows your function app to authenticate with these services without providing a connection string as part of your function config. Here is how the configuration works for each library in the Application settings section of your function app in the portal. More details on configuring application settings for Functions apps can be found here<\/a>.<\/p>\n

Similar configuration is possible when running locally by modifying the local.settings.json file<\/a>. In the local experience, you may run into a warning about missing connection strings in your local.settings.json<\/code> file when using secretless configuration. This will be fixed prior to the GA of the extensions.<\/em><\/p>\n

General setup<\/h3>\n

For all of the extensions being discussed, you will need to set the AzureWebJobsStorage<\/code> setting to use a general-purpose storage account as this is required by the Functions runtime.<\/p>\n\n\n\n\n\n
Name<\/th>\nValue<\/th>\n<\/tr>\n<\/thead>\n
AzureWebJobsStorage__accountName<\/td>\n{account name}<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

For local development, you can still use Azurite<\/a> by setting the value of AzureWebJobsStorage<\/code> to UseDevelopmentStorage=true<\/code>.<\/em><\/p>\n

Unless otherwise specified, each of the configurations is powered by the DefaultAzureCredential<\/a> type. This implies that your functions app (or your local environment when running locally) would need to be able to authenticate with the corresponding Storage account, Event Hubs namespace, or Service Bus namespace using at least one of the authentication mechanisms used by the DefaultAzureCredential<\/code>.<\/p>\n

Storage<\/h3>\n

Blobs<\/h4>\n\n\n\n\n\n
Name<\/th>\nValue<\/th>\n<\/tr>\n<\/thead>\n
MyConnection__blobServiceUri<\/td>\nhttps:\/\/{account name}.blob.core.windows.net<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Here is a simple function that will run whenever the specified blob is modified:<\/p>\n

[FunctionName(\"BlobTriggerFunction\")]\r\npublic static void Run(\r\n    [BlobTrigger(\"sample-container\/sample-blob\", Connection = \"MyConnection\")]\r\n    Stream blobStream,\r\n    ILogger logger)\r\n{\r\n    using var blobStreamReader = new StreamReader(blobStream);\r\n    logger.LogInformation($\"Blob sample-container\/sample-blob has been updated with content: {blobStreamReader.ReadToEnd()}\");\r\n}<\/code><\/pre>\n
Queues<\/h4>\n\n\n\n\n\n
Name<\/th>\nValue<\/th>\n<\/tr>\n<\/thead>\n
MyConnection__queueServiceUri<\/td>\nhttps:\/\/{account name}.queue.core.windows.net<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Here is a simple function that will run whenever a message is delivered to the specified queue:<\/p>\n
[FunctionName(\"QueueTriggerFunction\")]\r\npublic static void Run(\r\n    [QueueTrigger(\"sample-queue\", Connection = \"MyConnection\")] \r\n    string message,\r\n    ILogger logger)\r\n    {\r\n        logger.LogInformation($\"Received message from sample-queue, content={message}\");\r\n    }<\/code><\/pre>\n
Event Hubs<\/h3>\n\n\n\n\n\n
Name<\/th>\nValue<\/th>\n<\/tr>\n<\/thead>\n
MyConnection__fullyQualifiedNamespace<\/td>\n{namespace name}.servicebus.windows.net<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Here is a simple function that will run whenever an event is delivered to the specified event hub:<\/p>\n
[FunctionName(\"EventHubTriggerFunction\")]\r\npublic static void Run(\r\n    [EventHubTrigger(\"<event_hub_name>\", Connection = \"MyConnection\")]\r\n    EventData eventData,\r\n    ILogger logger)\r\n{\r\n    logger.LogInformation($\"C# function triggered to process a message: {eventData.EventBody}\");\r\n    logger.LogInformation($\"EnqueuedTime={eventData.EnqueuedTime}\");\r\n}<\/code><\/pre>\n
Service Bus<\/h3>\n\n\n\n\n\n
Name<\/th>\nValue<\/th>\n<\/tr>\n<\/thead>\n
MyConnection__fullyQualifiedNamespace<\/td>\n{namespace name}.servicebus.windows.net<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Here is a simple function that will run whenever a message is delivered to the specified queue:<\/p>\n
[FunctionName(\"ServiceBusTriggerFunction\")]\r\npublic static void Run(\r\n    [ServiceBusTrigger(\"<queue_name>\", Connection = \"MyConnection\")]\r\n    ServiceBusReceivedMessage message,\r\n    ILogger logger)\r\n{\r\n    logger.LogInformation($\"C# function triggered to process a message: {message.Body}\");\r\n    logger.LogInformation($\"EnqueuedTime={message.EnqueuedTime}\");\r\n}<\/code><\/pre>\n
Advanced Configuration<\/h3>\n
In each of the preceding examples, the DefaultAzureCredential<\/a> type would be used by the extensions to attempt to authenticate with the service. It’s also possible to configure more fine-grained authentication. We will use Blob Storage as an example, but the same settings are available for Storage Queues, Event Hubs, and Service Bus. To configure using Managed Identity, which uses the ManagedIdentityCredential<\/a> type:<\/p>\n\n\n\n\n\n\n\n
Name<\/th>\nValue<\/th>\n<\/tr>\n<\/thead>\n
MyConnection__blobServiceUri<\/td>\nhttps:\/\/{account name}.blob.core.windows.net<\/td>\n<\/tr>\n
MyConnection__credential<\/td>\nmanagedIdentity<\/td>\n<\/tr>\n
MyConnection__clientId<\/td>\n{myClientId}<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
To configure using a client secret credential, which uses the ClientSecretCredential<\/a> type:<\/p>\n\n\n\n\n\n\n\n\n
Name<\/th>\nValue<\/th>\n<\/tr>\n<\/thead>\n
MyConnection__blobServiceUri<\/td>\nhttps:\/\/{account name}.blob.core.windows.net<\/td>\n<\/tr>\n
MyConnection__tenantId<\/td>\n{myTenantId}<\/td>\n<\/tr>\n
MyConnection__clientId<\/td>\n{myClientId}<\/td>\n<\/tr>\n
MyConnection__clientSecret<\/td>\n{myClientSecret}<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
And finally, to configure using a client certificate, which uses the ClientCertificateCredential<\/a> type:<\/p>\n\n\n\n\n\n\n\n\n
Name<\/th>\nValue<\/th>\n<\/tr>\n<\/thead>\n
MyConnection__blobServiceUri<\/td>\nhttps:\/\/{account name}.blob.core.windows.net<\/td>\n<\/tr>\n
MyConnection__tenantId<\/td>\n{myTenantId}<\/td>\n<\/tr>\n
MyConnection__clientId<\/td>\n{myClientId}<\/td>\n<\/tr>\n
MyConnection__certificate<\/td>\n{myCertificate}<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
CloudEvent Binding<\/h2>\n
When writing a C# function, it is now possible to use the new CloudEvent<\/a> type which conforms to the CloudEvents V1 schema<\/a> for output functions:<\/p>\n
Output:<\/p>\n
[FunctionName(\"CloudEventBindingFunction\")]\r\npublic static async Task<IActionResult> RunAsync(\r\n    [HttpTrigger(AuthorizationLevel.Anonymous, \"get\", \"post\", Route = null)]\r\n    HttpRequest req,\r\n    [EventGrid(TopicEndpointUri = \"EventGridEndpoint\", TopicKeySetting = \"EventGridKey\")]\r\n    IAsyncCollector<CloudEvent> eventCollector)\r\n{\r\n    CloudEvent e = new CloudEvent(\"IncomingRequest\", \"IncomingRequest\", await req.ReadAsStringAsync());\r\n    await eventCollector.AddAsync(e);\r\n    return new OkResult();\r\n}<\/code><\/pre>\n
Trigger functions are not yet supported as an Event subscription can currently only be created using the EventGridSchema from Azure Functions.<\/p>\n
Conclusion<\/h2>\n
Azure Functions is one of Azure’s core serverless offerings, that can greatly simplify your application. The latest set of packages are our effort to make integrating with Azure functions quick and painless, allowing you to quickly jumpstart your applications and get running.<\/p>\n
For more information about each of the extensions from this article please see the following README files:<\/p>\n