Azure Functions
Azure Functions is an event driven, compute-on-demand experience that extends the existing Azure application platform with capabilities to implement code triggered by events occurring in other Azure services, SaaS products, and on-premises systems. With Azure Functions, your applications scale based on demand and you pay only for the resources you consume. Azure Functions provides an intuitive, browser-based user interface allowing you to create scheduled or triggered pieces of code implemented in a variety of programming languages.
-
Azure Function - Event Grid Output Binding
Presently there is only an Azure Service Bus output binding for Azure Functions, there is nothing to pass the output on to another Event Grid Endpoint.
This would be very useful.
Kind Regards
Paul
15 votesThis makes a ton of sense. We don’t have this work fully designed or scheduled, so marking as “unplanned” for now, but we will be looking to tackle this.
- Matthew
-
Support for Azure Managed Service Identities in EventHub (and other) triggers
In Event Hub, I can add my Function App's MSI as a data reader, but in the function I cannot use trigger bindings to read from the queue without using a SecureAccess Key. We are trying to go password free wherever possible, and Azure has been promoting this course of action, so why do we need secret keys for reading from the queue? It then forces us to create and share a secret key for partner teams to read from our queue, rather than just permissioning them in Event Hub.
7 votesGreat request, but we do not have a timeline for when we will deliver this. We definitely want to get here though.
- Matthew
-
Add ability to register Service Bus plugins
Azure Service Bus .NET Standard client supports plugins registration for incoming and outgoing pipeline customizations. Already existing plugings are:
- Message ID (to follow message ID conventions or for de-duplication)
- Attachments (claim check)Service Bus customers can implement and plug their own plugins to satisfy encryption requierments and other aspects internal to their business. By allowing plugins registration via trigger configuration API, the code normally distributed with the functions would be reduced to a package reference. This will allow Functions authors focus on the logic and not the miscelanious aspects.
GitHub issue: https://github.com/Azure/azure-functions-host/issues/2504
7 votesNo change, but unplanned is a better tracking status.
—Colby
-
Azure Services/PaaS or E2E-scaffolding for Facebook GraphQL/Relay
There is something beyond Azure App-Services and Functions; Facebook GraphQL as a service, end-to-end which should in clude a CQRS "back-end" (REDIS...) and API-Mgmt/Monitoring features. Here are some examples: https://www.graph.cool/features/ and https://scaphold.io/... but we leverage Azure, so we are currently developing with graphql in AppServices...
6 votesWhile we like this idea, it’s not something that is specific to Functions, and not something we have a schedule for. If you’d like to know more about using Functions with GraphQL, check out this workshop:
https://github.com/simonaco/serverless-graphql-workshop
—Colby
-
Azure B2C Trigger
It would be really helpful to be able to have triggers on Azure B2C, for example on new user added take some action etc.
4 votesThis remains unplanned – please keep the votes coming!
-
Add binding attribute to control function scaling
We use azure functions extensively. One of the issues we have is not being able to control individual functions scaling. I am not talking bout the function app here, but the functions themselves.
Using the new attribute binding system could be a very nice way to set the max number of instances a function can spawn.
[MaxParallelExecution(5)] or something like that.this would make it so that particular function does not scale over 5 instances.
4 votesWe do plan to provide more control over scaling on an app level in the future – as the app is the unit of scale. As such will likely manifest as an app setting and not a function binding. Thanks for the feedback.
-
Jeff -
Wildcard within path of blob input bindings
I wish we could specify blob storage input bindings path that included wildcard.
--- function.json
{
"type": "blob",
"name": "faces",
"path": "face/profile-{date}-*.png",
"connection": "AzureWebJobsDashboard",
"direction": "in"
}Then, I hope to process these as array of Blob objects.
---index.js
module.exports = function (context, myQueueItem) {
const fileSizeList = context.bindings.faces.map(face => face.size);
context.log(fileSizeList);
context.done();
};3 votesNot currently in plans – would recommend looking into event grid filters and event grid trigger. But keep votes coming.
-
Jeff -
SMTP Triggers
Functions are great for building HTTP-based Apis. Our SMS-api supports both HTTP(S) and SMTP(Mail 2 SMS).
In order to use Functions, we would need to be able to bind one or more email domains to it and use email as triggers
2 votesOur recommendation for now would be to use a 3rd-party SMTP service. Azure Logic Apps may be a good option to look at for some of these integrations.
- Matthew
-
Function inputs with query or path support should be able to make use of query/body parameters
The documentation for SqlQuery inputs mentions that this capability is not *yet* supported, and points to a GH comment, but I saw no actual feature request so here it is.
"You can pass route data to the SqlQuery parameter as shown, but currently you can't pass query string values." (link to comment https://github.com/Azure/azure-functions-host/issues/2554#issuecomment-392084583)
Is there any sort of timeline that users can expect this?
Also, I think the documentation could be improved to explain that the Route Templates are based on ASP.NET routing, which is where the limitation stems from (because route templates in ASP.NET do not encompass…
1 voteThis is some awesome functionality!
We will update this item when there is a plan to implement it.
Thanks for the feedback!
Alex
Azure Functions Team -
MQTT Subscriber trigger support as a first class trigger
Please add support for listening to MQTT 3.0 and 3.1 servers as a subscriber for a trigger. This would be immensely useful in IoT scenarios.
1 voteGood ask. No current plans. Keep votes coming.
-
Jeff -
Support international SMTPUTF8 email addresses in Sendgrid output
It seems like international characters in email addresses are not supported.
I think SendGrid supports SMTPUTF8, as indicated here: https://sendgrid.com/blog/episode-2-of-the-grid-podcast
It would be nice if Azure Functions could successfully implement support for this as well.
When I send email to an address containing 'ø', the SendGrid portal displays the address as containing 'ø' in place of the 'ø', which is a typical ASCII/UTF-8 encoding mismatch. And the message is dropped with Reason 'Invalid'.
1 voteOpened this issue to help track
https://github.com/Azure/azure-webjobs-sdk-extensions/issues/471
Nothing planned short term to address.
-
Jeff
- Don't see your idea?