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 ;-) )
253 votesPlease take a look at the custom handlers feature that allows you to write functions in Go. https://docs.microsoft.com/azure/azure-functions/functions-custom-handlers
- Anthony
-
Support for native Rust Azure Functions
As of February 2019, Azure Functions support native .NET, JavaScript and Python.
Could we please have native support to run Azure Functions written in Rust? To host Rust functions currently we have to pay for a Linux App Service plan and embed our functions within a Docker container. This is expensive just to run a few microservices written in Rust.
Peter Huene has an excellent project for anyone interest in writing Azure Functions in Rust....
224 votesPlease take a look at the custom handlers feature that allows you to write functions in Rust. https://docs.microsoft.com/azure/azure-functions/functions-custom-handlers
- Anthony
-
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.
215 votesWe don’t have an exact timeline for this, but this is something we’re eager to light up and have some preliminary work underway for. This will likely show up for Storage first, but messaging services like Event Hub would be shortly after.
-
Enable custom 3rd party authentication providers
Outside of out of the box providers like facebook and google, provide samples and guidance on how to authenticate with others like LinkedIn.
172 votesWe have created an early public preview of OpenID Connect support, allowing you to bring your own OIDC provider: https://docs.microsoft.com/azure/app-service/configure-authentication-provider-openid-connect
If you have an OIDC provider you wish to use, we encourage you to try out this path. There are still some rough edges to the preview, but we’re hoping to smooth those out soon.
-
Support F# scripts (.fsx) in v2 and v3
F# script usage is about to become much more prevalent due to the improved "#r nuget" imports in F#5. Azure Functions v2 and v3 should support F# scripts so that we can avoid having to create a "function project" when a a simple .fsx would suffice.
161 votesCurrently unplanned but please keep the votes coming. – Anthony
-
Allow Key Vault references to access secrets behind Key Vault Firewall
Key Vault references cannot currently be used to access secrets in a vault that has been configured with Key Vault Firewall / service endpoints.
It should be possible to resolve secrets from Vaults configured this way (provided the web app / function app is configured with the right VNET integration).
159 votesThis is now available for Windows apps. Linux support is coming soon.
-
ASP.NET Core MVC/Web API support
Enable developers to create serverless applications using the ASP.NET Core Web API framework.
125 votesStill unplanned, but please keep the votes coming!
-
SQL Azure trigger support
Azure functions are great, but a lot of application logic is driven by data in SQL Azure DBs. It would be great to have a trigger based on a SQL Azure row data.
113 votesThis is currently on our radar and is now planned work. Thanks for voting!
- Cary, Azure Functions
-
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.
91 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
-
Trigger Azure Function From Table Storage
Allow create, update and delete on a table storage row to trigger an Azure Function.
89 votesStill unplanned, but please keep the votes coming.
- Matthew -
Add max calls/per day|hour|minute configuration for throttling
Now- any light ddos attack that Azure will not recognize- will affect me and my account. If I know that my service shouldn't receive more than 10000 calls per day, but I can't setup limits on incoming requests.
"Daily Usage Quota (GB-Sec)"- not bad idea, but it's something internal and synthetic for me. Call/per day- is much more native metrics for users.
88 votesHere’s the latest as there seem to be 2 types of ask here and so two seperate updates. Need comments for if this issue should close to be focused on one or other:
1. I want to control how many calls my function can make to another API (the 3rd party API rate limiting).
– In all plans we now have a way to specify the max instances. This can limit how far a function app instance can scale: https://docs.microsoft.com/en-us/azure/azure-functions/functions-scale#limit-scale-out2. I want to stop my function from triggering more than x times an hour.
Nothing planned in this in the short term. Using API Management for HTTP functions with throttles would be our recommendation for HTTP, nothing out of box for non-HTTP triggers yet. -
Support gRPC in azure function as trigger
gRPC is a standard for microservices and cloud-native solutions nowadays. It should be supported by azure functions, durable functions and API Management.
82 votesNo plans for this one, but please keep the votes coming!
-
Support for R
Are there any plans to support R scripts in the future?
82 votesThanks for your feedback. Currently, we don’t have any plans for R support in Functions. We will monitor the votes on this request to accordingly inform the priority on our backlog.
-
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..67 votesThere are CLI commands today for moving between Consumption and Premium plans. However, we currently still do not support App Service migration. This is still planned work, and we will be investigating. Thank you for your patience
-
Cary -
Should support trigger for Azure Files
This would make hybrid integration scenarios for customers with no IT trivial, anybody can drop a file in a share.
66 votesThe below is still accurate, but updating to better reflect product backlog. Keep the votes coming.
-Colby
-
Handle Storage Queue/Service Bus messages in batches
I want to be able to handle multiple messages per function call - we are using a third-party web service which works much more efficiently if the messages are passed to it in batches. I know we could use a timer to trigger the function and grab messages from the queue ourselves but if we do that the function won't scale out automatically.
66 votesLeaving as started becasue we don’t have full docs out yet but this is completed. Just need to document and provide samples
-
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…
57 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.
-
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.
46 votes -
Function App Service support for Azure B2C
If I build a web app using Azure B2C for authentication, I'd like to use it as the authentication provider for Azure Functions too. Although I can set up the same providers, using B2C would be cleaner and enable me to support users with local logins (traditional username and password) too.
44 votesJust since it’s been a while, I wanted to reconfirm that this is planned.
-
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
42 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.
- Don't see your idea?