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.
-
Golang support for Azure Functions
C# and other environments are already supported; it would be nice if Go / Golang was one of them. I'd love to handle web requests using Golang + Azure Functions.
It could provide the "HTTP Requests" via the stdin, while the "HTTP Response" can be given via the stdout. (or whatever those two are called on Windows ;-) )
182 votes -
Enable triggering of Azure functions based on an event in RabbitMQ
Hello, we are having a scenario where we should be able to trigger a function when a message is added to RabbitMQ. This would be really helpful in using Azure functions to integrate with other Message queuing platforms that support AMQP protocol.
94 votesWe just shipped a preview of this functionality today you can try out. In the coming weeks we will enable support to trigger within the Azure Functions Premium plan to receive serverless scale and a function plan to RabbitMQ endpoints within a private network. Please provide feedback and let us know if this meets needs as expected. Details can be found here:
https://dev.to/azure/announcing-the-rabbitmq-extension-for-azure-functions-2mbo
-
ASP.NET Core MVC/Web API support
Enable developers to create serverless applications using the ASP.NET Core Web API framework.
79 votesGreat ask. Keep the votes coming. Nothing planned short term.
-
Jeff -
Global exception handler
Make it possible to have a global exception handler in C# Azure Functions App project - to be able to handle exceptions in one central location.
32 votesWe are starting to look into the feasibility of this and the experience that people are looking for. If you are interested to provide feedback on how you’d like to see this implemented please comment here https://github.com/Azure/azure-functions-host/issues/4459
-
Retrieve function app keys from ARM template
Make it possible to set/retrieve function app keys via ARM templates.
This will make it easier to store it in the settings of an other service while rolling out an environment.32 votesWe do have APIs which make this easier, now. It involves the listKeys() method that may be familiar from other services.
We are working on formal documentation (which is why this isn’t flagged as “completed” yet), but some of the details are captured in this GitHub issue:
https://github.com/Azure/azure-functions-host/issues/3994- Matthew
-
Julia lang support for Azure Functions
With Julia lang reaching v1.0 last year, it is emerging as a force in machine learning and other scientific computing applications,
https://juliacomputing.com/case-studies/
In particular, BlackRock's Aladdin, Conning Asset Management, and Aviva are all using Julia for financial risk modeling and I see a great opportunity for Julia to impact finance among other things. I'd love to be able to use Julia in Azure Functions for my fintech startup.
27 votes -
Add C++ support for Azure Functions
Allow C++ binaries to contains Azure Functions. It could be done by invoking the main in an executable, or a DLL with a specific export method with predefined signature.
C++ allows to control memory usage and allow users to be incredibly fast when used properly. In an environment where scaling is needed, squeezing a few seconds of CPU or lowering a few KB of RAM can translate to hundreds or thousands of dollars in savings.
If memory leaks are a concern, putting aside the fact that C# code can also leak, you could create fail safes for Azure Functions. A…
26 votesThanks for your feedback. Currently, we don’t have any plans for C++ support in Functions. We will monitor the votes on this request to accordingly inform the priority on our backlog.
-
25 votes
This is planned. Thought there was another issue to merge with but couldn’t find it – so keeping this for now.
-
Jeff -
Allow moving Function from Consumption to Service Plan
Currently if you deploy your function on a consumption plan there is no way to move it to an existing Service Plan like any other App Service.
You would need to delete the existing one and redeploy it..24 votesQuick update here – with the announcement of the premium plan we do support moving from consumption to a premium plan. Today this may not work for all consumption apps in a region only because some consumption apps may exist in a “webspace” that doesn’t yet have premium turned on. That said we have CLI commands rolling out in the next few weeks to make this seamless.
Moving to app service plan is a bit trickier as the actual code often lives in a different place on an app service plan (app service local storage) than where consumption needs them (azure storage files) – so moving may not work and currently don’t have any immediate plans to do like “code migration” in addition to changing plans.
You can see a sample of moving plans between apps in this sample here as well: https://github.com/Azure-Samples/functions-csharp-premium-scaler
-
Jeff -
Support Service Bus trigger with use of SAS token
In our company we are using Service Bus with a framework that deals out the SAS tokens to queues. These tokens are living for few days only and concern hierarchical queues (eg. queue name could be productA/event-type-B/subtypeC) and only Listen policy.
This would mean that listening on a different level then root level of namespace would be needed.
Best if also the whole connection to SB described by this token would be separate object from the Function, so we could modify it (by altering with new SAS token/whole connection string) without modifying the Function code (as API Connections in Logic…24 votesNo plans for this right now, but please keep the votes coming.
-
Don't 'hardcode' the storage account connection string for the storage account that backs azure functions
Currently each Function App has an application setting string "WEBSITE_CONTENTAZUREFILECONNECTIONSTRING"which is a fixed (=hardcoded) connection string. This breaks when performing key rotation on the connection string and is opaque to diagnose since that setting is automatically setup by the portal UI/wizard.
Can you instead just store the subscription ID and storage account name and then fetch the latest connection string for the storage account using the management API? This will make sure that the function app survives storage account key rotations
19 votesThis makes sense. We are working on solutions to enable storing the secret in Key Vault and account for rotation. There is some additional validation logic that needs to be relaxed to enable these scenarios.
-
Add support for Open API (Swagger 3)
Azure Functions currently supports Open API (Swagger 2) (https://azure.microsoft.com/en-in/updates/announcing-azure-functions-open-api-swagger-support-preview/).
Now that Open API 3 has been released, it would be helpful if the latest standard could also be supported
19 votesWe have just released integration with API management as there is a consumption plan. Please review https://docs.microsoft.com/en-us/azure/azure-functions/functions-openapi-definition to see if this meets your needs.
-
Add support for hybrid connections to Consumption Plan
Can we add Hybrid Connections to functions running in Consumption Plans
I'm aware of the idea ...
https://feedback.azure.com/forums/355860-azure-functions/suggestions/14807298-should-support-hybrid-connectionsBut this is for App Service Plans, and only mentions Consumption Plan in the response.
18 votesHello, we’re looking into more networking options for Azure Functions, but no plans on bringing Hybrid Connections to consumption plan at this time.
Thanks,
Alex -
Support authentication for Azure Function Core Tools
Azure Functions has been great, especially the ability to run the Core Tools locally. However, there are often scenarios where you return data depending on the currently authenticated user. This appears to be supported in Azure Functions in Azure now but there are no options within the Core Tools. This would be hugely useful for local development.
16 votesThis is something we’re looking to enable.
-
Enable direct internal Function-to-Function calls
There is a need to call one Function from another Function without an Internet round-trip, and without dependencies on additional services. (To me, "no Internet round-trip" implies the same region, but if "anywhere within Azure" optimizations could be made without a direct http call to go elsewhere, that would also be ideal.)
Since the request linked below was closed as Completed even though the "resolution" refers to orchestration, a completely different concern, I'm opening this to re-request with the original intent.
14 votesThis continues to be unplanned, but it’s a great item. Please keep the votes coming!
- Matthew
-
Functions Should support Custom Trigger events
Functions Should be able to support custom triggers
In my case i need a trigger from azure redis which is not possible in functions now.14 votesWe aim to make this possible via Azure Event Grid. The specific request for Redis will depend on Azure Redis support for Event Grid.
- Matthew
-
Set environment variable override for AuthorizationLevel.Function key
When running within the Azure Functions Runtime inside of a Docker container, we can't use AuthorizationLevel.Function as there is no way to retrieve the key from the runtime. It'd be great if we could directly set a function key in our compose.yml as an environment variable. For deployment, we just leave the environment variable blank and the App Service can set the keys.
Related SO question:
https://stackoverflow.com/questions/52174892/how-to-set-authorzationlevel-per-an-environment-condition-when-running-csproj-fu13 votesWe do have this set up for Kubernetes deployments, but there is not yet anything for standard Docker. This is a valid request, but we don’t have a timeline attached to it.
- Matthew
-
Support for queue settings per function
As I was looking for a way to configure the visibility timeout for queue messages I found that the only configuration seemed to be at the host level. The problem is that my queues have different needs and one setting will not work optimally for all queues. I am looking for a way to configure each queue independently.
11 votesGood request and thanks for insight, keep the votes coming. No current plans on this
-
Jeff -
consumption plan china
Currently Azure Function Apps cannot be hosted on a Consumption Plan if the target Cloud is China.
We would like to have the capability to use the Consumption Plan also on this Azure Region.
9 votesThank you for your feedback! We’ve started the work to enable Consumption Plan in China North 2. Please expect the next update by August.
-
Add support to Open Tracing/Zipkin
Opentracing (http://opentracing.io/) is a popular standard for tracing correlated requests across many different services communicating via RPC. It contains implementations on several different platforms and various tools (zipkin being one of the most popular ones). The standard can be easily extended over HTTP using dedicated headers from client/server side. It would be great if Azure functions would be able to provide more or less transparent support for it.
9 votesWe are currently working on supporting a suite of Azure based distributed tracing solutions. We have no current plans to support this tool, but would love to hear from the community, and are leaving this item open to collect feedback :)
Thanks!
Alex
Azure Functions Team
- Don't see your idea?