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.
-
1 vote
-
1 vote
-
Support for Java in Windows
There is currently support for Azure Functions using Java in Linux Environments, however adding support for Java Functions to Windows Environments would be helpful as some don't have the want/need to use linux.
1 vote -
Increase VM SKU options for premium plan
As durable functions for python become GA this year, it would make sense to increase the limit for number of cores available to be used for a function app. For ETL jobs that can be parallelized, it would be very beneficial. Is there a plan to offer more SKUs?
3 votesThanks for the idea! Keep the votes coming!
-
Consumption plan for Linux-based function apps in Canadian regions
Hi, are there any plans to open up consumption plans for Linux-based function apps in Canada Central or Canada East regions?
Thanks.
--Lalindra
3 votesThanks for the suggestion! We are currently planning this to roll out in Mid 2021
-
Allow configuration of Storage Account for Function with Event Hub input binding
Currently, an Azure Function gets one Storage Account, which is configured via the AzureWebJobsStorage property.
This Storage Account is then used for any meta-data that the Function may need to store to work as expected.
In the case of an Event Hub input bound Function, a blob container is created, which tracks the checkpoint of every partition in the Event Hub.
Due to the Storage Account requirements for a Function, it is not possible to take advantage of Premium Storage for the Event Hub checkpointing process.
While it makes sense to require a Storage Account that can support multiple types…
2 votesIt would be great to get an a sense for some of the specific features you need from the storage configuration, but this seems like a perfectly reasonable request. There has been some recent exploration of the AzureWebJobsStorage usage, so we’ll look to see how that all lines up with this.
-
use key vault reference in local.settings.json
would like the ability to use the new key vault reference in local.settings.json for local debugging instead of needing to have secrets in plain text. this would allow dev teams to leverage key vault as the central location for secret management.
14 votesThis is something we’re looking to enable through the Core Tools.
-
Support properties of {DateTime}
Binding expression {DateTime} should support all properties of C# DateTime object - e.g. using {DateTime.Year} to only get the year
the syntax {DateTime.Year} currently does not throw an error but still returns the same as {DateTime} which is also inconsistent behavior
1 vote -
Durable Function Trigger Throttling
When triggering a durable function from a queue, there should more controls to throttle function executions. Need a way to limit the total number of executions running at one time. Executions need to finish before more can be started. As currently implemented more and more functions are started before others are finished. This overwhelms downstream resources. I have tried the options outlined in https://github.com/Azure/azure-functions-durable-extension/issues/1067 but it doesn't help and there is no traction in that thread.
2 votes -
Do not hardcode EventHubName and ConsumerGroup in c# trigger attributes
Currently, EventHubName and ConsumerGroup are hardcoded in the trigger attribute:
[EventHubTrigger("eventHubName", Connection = "ConnectionStringSettingKey", ConsumerGroup = "ConsumerGroup")] EventData[] events
Only the connection string is read from configuration and can be changed between local debug and different slots.
Create a possibility to read EventHubName and ConsumerGroup from the slots configuration.
1 vote -
authentication
Allow authentication to Azure functions with accounts that have MFA enabled.
Currently, if you use functions as middleware for a non-authenticated client app (like wasm blazor), there is no way to authenticate to a function middleware layer if your account is MFA enabled. This could be either a) having some kind of ms auth phone-like app connection to do the auth or 2) to do pre-auth like is done with logic apps and some of the connectors (e.g. twitter).
I think this could take any of a number of forms, but is definitely a current limitation when integrating serverless applications.
1 voteIt’s unclear exactly what is breaking in the example scenario. MFA as a feature of AAD can work here, especially if the public client is using one of the identity SDKs for login. Is this specific to a given provider, or more around a general pattern?
There are patterns in Durable Functions for dealing with human interaction flows if looking to build your own MFA flow: https://docs.microsoft.com/en-us/azure/azure-functions/durable/durable-functions-overview?tabs=csharp#human
-
'indirect' strings
I have created several Azure Functions, and recently saw that it is possible to use 'indirect' strings using the "%setting-value%" format.
This approach is seriously flawed - I added some such connection strings, but adding them caused the function to stop writing a message to the out queue.1 vote -
Client cert authentication support in Azure functions
the ability to support mutual authentication with client certs. Today the only way to do this is built it into your functions
https://stackoverflow.com/questions/49686316/azure-functions-configure-client-certificate-authentication
it would be great to have this as a feature of the platform.you could compare this lack of functionality to the something like Kubernetes ingress controller that easily allows you to do mutual auth https://github.com/kubernetes/ingress-nginx/tree/master/docs/examples/auth/client-certs
4 votesNo current plans for this at the moment, but it’s a great suggestion. Please keep the votes coming.
-
Add RPC support for Azure Functions
RPC support for Azure functions to allow compile-time verification of RPC calls. As it is, HTTP trigger endpoints are not verifiable at compile-time.
3 votesWaiting for more feedback in the comments to assign this item
Alex
Azure Functions PM Team -
Make it possible to restrict the used storage account to a virtual network
Make it possible to restrict the used storage account to a virtual network. Some customers, especially in the finance industry, have the requirement to secure and protect any storage account. So it is mandatory for them to also limit access of the storage accounts used for Azure Functions.
4 votesThis work has been started. Check the following docs page, as that will be updated first when this feature becomes available https://docs.microsoft.com/en-us/azure/azure-functions/functions-networking-options
Thanks for the feedback!
Alex
Azure Functions PM Team -
Built-in role for Azure functions
There is now built-in role Azure functions. I would like see soem built-in role for Azure Functions. For example,
- Developer Role
- Platform Admin role
- Read-only role
- Security role.
is there any roadmap for built-in role for Azure Functions.
1 voteI believe the request here is for roles like an equivalent of “Web App Contributor” which adjusts specific permissions different from the standard “Contributor” Role.
It’s a valid request, but currently unplanned. Please keep the votes coming, and it would be great to get some examples of what proposed roles might look like.
Do remember that you can always create custom roles: https://docs.microsoft.com/en-us/azure/role-based-access-control/custom-roles
-
Can we test azure http trigger with API_KEY locally?
I am creating some http triggers and want to know if we can create API_KEY locally to simulate the actions.
1 voteThis does not exist today, but it’s a valid request. Please keep the votes coming.
-
Reduce the price of Premium instances
I could run a VM that costs me much less for the same configuration. To me, the price for pre-warmed instances seems too high.
7 votesThis is a great suggestion! Keep the votes coming and we’ll periodically re-evaluate this request.
Alex
Azure Functions PM Team -
Use token instead of session to call azure function from client app in browser on behalf authorized user
Return an access token instead of the session after the user authenticated in azure functions.
To allow functions call from any domain.Here it the description of the case and idea
https://stackoverflow.com/questions/60087293/calling-azure-function-from-client-app-in-browser-on-behalf-authorized-user1 voteThis is a great suggestion! While there is a path to this today (using the provider SDK and exchanging for a session token), it’s not well documented, and it certainly could be easier to set up. We will look into this!
- Matthew
-
vnet integration
function app and web app cloning
When cloning apps and adding it to a different ASP you need to add conditions or checks whether the app is vnet integrated and not allow the cloning. This breaks the destination ASPs network configuration and none of the existing apps be able to communicate or function properly.
12 votesThis is a great idea! Keep the votes coming. We will update this item if there is an immediate plan to add this functionality
Alex
Azure Functions PM Team
- Don't see your idea?