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.
-
Forwarding the client certificates in Azure Functions Proxies.
Our customer would like to have the features for forwarding the client certificates in Functions Proxies.
1 vote -
Allow to set message property such as sessionId to Service Bus output bindings for node.js
There is no option to set the sessionId in Service Bus output bindings for node.js environment.
I suggest to add that1 vote -
Add a "Run" button to the portal
There are 2 documented ways to "manually" run a funciton.
HTTP triggered: https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-first-azure-function#test-the-function
Non-HTTP triggered: https://docs.microsoft.com/en-us/azure/azure-functions/functions-manually-run-non-http
Both approaches are quite clunky. Since running a function manually is obviously possible and documented, it seem like a glaring omission that a simple "Run" button isn't provided in the portal.
1 vote -
Azure Function functionTimeout needs to be configurable per-environment via app settings, not only through host.json
I need to configure my functionTimeout on an Azure Function per-environment. I have dev deployments that should just use a default timeout, and production deployments that can handle a long timeout (dedicated app service).
1 vote -
Project Version Display in Portal
It would be helpful if the Portal displayed the currently deployed function DLL version for easy IT reference. We deploy our Functions through our IT team via the Zip Deploy process in all UAT and Production environments and it would be great if they could easily confirm that the currently deployed/running version.
2 votes -
Do not execute Timer Trigger in Azure Functions Deployment Slots (other than production)
Currently Timer Trigger still execute in Deployment Slots, which renders them useless for any Functions containing Timer Triggers, because you will then have two running instances.
As I understood the slots, their intention is to make the deployment as seemless as possible. So if I have to stop the slot auto-manually (CI/CD) after the swap, I might stop a running function in the middle of something. If I dont, I will have effectively two running instances of the same Azure Functions, doing everything twice.
So could it be possible to have Timer Triggers not be exectuted when the Function runs…
3 votesThanks for the request! We recommend folks disable functions in the environment they don’t want it to run. Here is our guidance to do that: https://docs.microsoft.com/en-us/azure/azure-functions/disable-function#:~:text=How%20to%20disable%20functions%20in%20Azure%20Functions%201,3%20Other%20methods.%20...%204%20Next%20steps.
-
Java 11
Right now the Java Function App in both version ~2 and ~3 is limited to JDK 8. It would be great to have support for JDK 11.
2 votesPlease try out Java 11 functions in preview on the tool of your choice, including VSCode! https://azure.microsoft.com/en-us/updates/java-11-for-azure-functions-is-now-available-in-preview/
-
Allow regex or port ranges in CORS rules
Not sure if this is Azure Functions specific, but it would be great to be able to specify a regex statement or a range of ports for a CORS rule for my function app.
My specific use case is I am working on a Twitch.tv extension, and the "developer rig" they provide for hosting the frontend files when developing locally uses a new random port number every time the files are reloaded, and I can't change that behavior. I would love to be able to specify a CORS rule like " http://localhost:[50000-60000] " but it seems this isn't allowed. I…
1 vote -
Visual Studio always uses name of req in the function.json file
Visual Studio always puts name : req in the function.json file. There appears to be no way to set this from code, and when publishing, it overwrites any manual changes you may have made. This name needs to be the different when using an additional parameter to your function method, like an auth token from Azure AD.
1 vote -
Visual Studio should warn that Functions developed in-portal will be overwritten
As the title states: Visual Studio should warn that Functions developed in-portal will be overwritten.
The design behaviour of Visual Studio deployments is to overwrite the whole app. This can be a problem for customers who have developed their Functions via the in-portal editor, and were not expecting them to be entirely overwritten.
I would think that we could detect this scenario and throw a warning screen before deploying.
2 votesThanks for the suggestion and please keep the votes coming!
-
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.
153 votesCurrently unplanned but please keep the votes coming. – Anthony
-
Allow non-public constructor for Function DI
A (non-static) Function's constructor that is used for dependency injection must currently be public.
Sometimes a Function has dependencies that (even as interfaces) are internal to its own project. As parameters of a public constructor, they are forced to become public, even though that is not the correct visibility modifier for them.
Non-public constructors (particularly internal ones) are the natural solution to this.
1 vote -
support http input binding
support http input binding
I found that input binding for HTTP did not exist.In my case, I needed to have a function request data via HTTP, and then write to Azure Table. (timer trigger)
1 vote -
CPU Time/%/Memory should be available in metrics when running on an App Service Plan
When getting alerts on high cpu ( or memory) for an app service plan, it is currently impossible to see what is consuming the cpu if both webapps and functions are running on the same App Service Plan
1 vote -
What is the problem when you cannot create new functions (Add button dimmed out)?
Why not provide some useful diagnostic information?
1 vote -
Misleading warning on function Integrate blade
The functions Integrate blade displays a warning that the bindings are missing the required direction property. This warning seems to display for all deployed functions even if the property is included.
0 votes -
First class support for Deno
Will we get first class support for Deno now that its reached version 1.0 https://deno.land/v1?
1 vote -
Set partitionKey property in Event Hub output binding
In an IoT scenario combining EventHub with StreamAnalytics, it is important that the EventHub is partitionned properly to allow writing a "parallel" query in Stream Analytics.
The current EventHub SDK allows to specify the partition key on a new batch of event before sending to EventHub, but this option is not available when we use an EventHub output binding.
Using the EventHub SDK in an Azure function is not an option as the function has to recreate the connection at each execution, and this is very slow, causing a function timeout in our tests.
1 vote -
Allow exploring functions across function apps in Azure Portal
We have several functions and function apps. The only reason we have separate function apps is that their deployments and host.jsons are different. All functions (even though they reside in different apps) are related to the same business cases. Allow exploring all functions within a resource group in a single search view.
2 votes -
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…
19 votesThis is something we are planning. Likely this would be accomplished through DefaultAzureCredential with the newest Storage SDKs, allowing more flexibility for local development.
- Don't see your idea?