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
-
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).
156 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.
123 votesStill unplanned, but please keep the votes coming!
-
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.
87 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
-
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.
71 votesNo plans for this one, but please keep the votes coming!
-
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..62 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 -
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…
56 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 -
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
40 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.
-
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.
39 votesThis is something we’re looking to enable.
-
azure cli from azure functions
I would like to run az cli from azure fuction.
it will help me to manage my Azure environment.
So far azure cli is not able from azure function. I'm getting:
2019-05-13T13:19:33.237 [Error] ERROR: The term 'az' is not recognized as the name of a cmdlet, function, script file, or operable program.Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
Microsoft.Azure.WebJobs.Script.Rpc.RpcException : Result: ERROR: The term 'az' is not recognized as the name of a cmdlet, function, script file, or operable program.
38 votes -
38 votes
Apologies on last message – we have started work for controlling checkpoints, not yet for resetting checkpoints. I updated the wrong issue. This is still planned though.
-
Jeff -
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.33 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
-
Support for "delete" DocumentDB Change Feed Trigger
Currently there is support for DocumentDB Change Feeds which only trigger for Insert and Update changes, however there is no way of picking up Delete changes to a collection
My use case has a real-time web application which relies on these change triggers to update the User Interface through Web Sockets that a change to a document/collection has taken place, at the moment I am having to implement this manually through a delete API call but that does not solve the problem if a document is manually deleted at source (for example).
A Delete of a document (IMHumbleO) is as…
29 votesCurrently unplanned and also blocked as the change feed for CosmosDB doesn’t support delete notifications which is what we use to power the trigger https://docs.microsoft.com/en-us/azure/cosmos-db/change-feed#change-feed-and-different-operations
-
Jeff -
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.
27 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 -
Blob trigger support with Service Principle/Managed identity
We are trying to setup a Blob Triggered Function, but we have a limitation to use only Service principal/managed identity to access the storage because of the security concerns in directly using access keys.
We did not find a way to by-pass blob trigger to using connection string.
Theoretically, since Blob Storage is integrated with Azure Active Directory, it should be possible to provide the right RBAC permissions on my Blob Containers so that the Function's identity (Managed Service Identity)/Service principle has whatever permissions are necessary to create the trigger and read from the blobs.
We are expecting azure functions…
25 votesThis is something we are planning. Likely this would be accomplished through DefaultAzureCredential with the newest Storage SDKs, allowing more flexibility for local development.
-
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…25 votesI believe in our latest SDK versions you should be able to use connection strings specific to a single queue / listen-only. These connection strings are stored in app settings and can be updated / rolled without having to modify or redeploy the code. Believe this would be sufficient today? Not sure if anything blocking anymore
-
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
25 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.
-
Support visibilityTimeout of Queue Trigger to be maintained after restarting Functions host.
The automatic retry with visibilityTimeout of Queue Trigger happens when the function host is up and running.
But after restarting Functions host, sometimes retry interval does not refer to visibilityTimeout.
Could you please support visibilityTimeout to be maintained after restarting Functions host?
https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-error-pages#retry-support22 votesThanks for the idea! Keep the votes coming!
-
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.19 votesThank you for the feedback! We are exploring options via Event Grid. There is planned work for a redis trigger.
-Cary
- Don't see your idea?