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.
-
Visual Studios tooling with local execution, debugging
Integrated support for Azure Functions projects in Visual Studio including being able to execute and test locally.
86 votesWe’re planning to get VS tooling for Azure Functions. Will share more on our GitHub after work starts.
-
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.
44 votes -
Add binding to Key Vault
Functions often need password, API keys, and connection strings to connect to other services and retrieve data. It would be great if those secrets could easily be obtained from Key Vault.
32 votesThis is a good idea. We’ll look at this later when we’re ready to start adding more bindings (likely after we GA).
-
Should be support real-time Storage blob triggers
Azure Functions is awesome! I'd like to propose for more convenience.
Currently, Storage blob triggers do NOT support real-time. Because write at
"https://azure.microsoft.com/en-us/documentation/articles/functions-reference/""The Functions runtime scans log files to watch for new or changed blobs. This process is not real-time;"
It is very inconvenience for me. I feel troublesome to use queue.
Amazon Lambda has storage event. They can notice real-time and very easy setting.
http://docs.aws.amazon.com/lambda/latest/dg/with-s3.html
http://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html31 votesThis is something we’d like, as well. Working with the storage team to address this.
-
Application Insights intergration
It would be great to have out-of-the-box integration with Application Insights. The Invocation log is ok but Application Insights much better.
How I see it:
- HTTP requests as Request telemetry
- TraceWriter.Info/Warning/Verbose as Custom Event
- TraceWriter.Error as Exception
- Input/Outputs as Dependency callsThe instrumentation key and other related configs could be placed in the host.json:
{
"applicationInsights": {
"instrumentationKey": "6e82db88-1d7b-411b-84cc-818cf195a91f",
"maxTelemetryItemsPerSecond": "10",
"telemetryModules": [
"Microsoft.ApplicationInsights.DependencyCollector.DependencyTrackingTelemetryModule",
"Microsoft.ApplicationInsights.Web.ExceptionTrackingTelemetryModule"
],
"telemetryInitializers":[
"Microsoft.ApplicationInsights.Web.ClientIpHeaderTelemetryInitializer",
"Microsoft.ApplicationInsights.Web.OperationNameTelemetryInitializer"
]
}
}18 votes -
Enable calling of other functions via internal ID
I'd like to be able to call other functions via an internal "ID" and worst case not to have to go back out to the internet and then come back in to Azure to call another function.
17 votesThis is something we’d like to make easier. We’ve had a few prototypes from hackathons on this. We’ll review whether we pick this up in our next planning cycle.
Some questions I have:
1. Do you want results back or are you ok with just triggering? (synchronous vs asynchronous)The current best practice for this, for asynchronous, is to use a Queue (SB or Storage).
-
Enable dependency injection in C# Functions
It would be useful to have a form of DI in our C# Functions, so we can consistently inject things like our logger class, or other Autofac DI services, into every C# Function we create.
I'd like to create a SDK package which developers can import into their Function and get access to some common functionality via DI, to remove boilerplate redundancy.
Any solution for this kind of thing?
17 votesThis is something we’d like to give proper support to. We’ll review this during our next planning cycle.
-
Add TypeScript support to Azure Functions
Please support writing TypeScript in Azure Functions when you're creating Node functions
12 votesWe’d like to support this. There is some experimental stuff for TypeScript here: https://github.com/christopheranderson/azure-functions-typescript
We’ll look at this closer during our next planning cycle.
-
Add new "HTTP Webhook" output type
It would be great to see an *outgoing* HTTP Request as an output type. Currently, the HTTP output is only the response object back to the caller. I can see the need and desire to output to other custom API's, perhaps that perform functionality that isn't currently captured in the existing outputs, such as Azure Automation/Application Insights/My Custom SAP API.
10 votesMarking this under review – we may end up just leaning more heavily on Logic Apps for this. We’ve had some thoughts around a direct Logic Apps binding/integraiton.
-
Should support hybrid connections
would be great if Azure functions would support Hybrid connections like other Web Apps. this intro blog says it does: https://azure.microsoft.com/en-us/blog/introducing-azure-functions/
but I cannot find it anywhere since the networking tab is not available in settings in the app.9 votesWe plan on supporting that via the UX at GA. Will confirm.
-
9 votes
This is tracked via this item. It’s currently in alpha – https://github.com/Azure/azure-webjobs-sdk-script/issues/335
-
9 votes
-
Bring the context object to more languages
https://azure.microsoft.com/en-us/documentation/articles/functions-reference/#comment-2605996917
The javascript runtime provides a "context" object that is referenced to include things like parameters, bindings, and the 'done' reporting mechanism.
For simplicity and consistency purposes, I'd expect to see this across languages.
9 votesAs this is planned for other languages, I’m marking it planned. Once we’ve added more langauges that use context, I’ll mark complete.
-
Support 64 bit functions
Currently only 32 bit functions supported.
8 votesWe’ll probably keep this under review until we have a clear reason to use 64 bit. It mostly is more expensive in our model. Feel free to provide scenarios where 64 bit would be necessary.
-
7 votes
We’ll look at this again after we GA; for dynamic tier. You can use Function Apps in dedicated app service plans using normal strategies for connecting to VNET. https://azure.microsoft.com/en-us/documentation/articles/web-sites-integrate-with-vnet/
-
Provide high-level monitoring experience (similar to Data Factory)
It would be great to have high-level monitoring available that visualizes all the functions in an instance, similar to how Azure Data Factory does it in the Monitor-feature.
Following information would be interesting:
- Failure rate per function
- Dependency metrics per binding, per function _(similar to AI Dependency)_
- Function state _(enabled/disabled)_
- ...7 votes -
Create new function by cloning/copying existing function
When creating a new function I'd like to start from an existing function I already created.
In my particular case I have a function where I've uploaded multiple additional files (python modules) and each function will need the same files, but today I have to re-upload them all.
7 votesThis is something we could conceivably support. In the meantime, you could use our console to copy the directory.
Also, for your use case in particular, why not upload them at the “root” of the Function App? Then reference them all from root?
-
Support for session-enabled Azure Service Bus queues/subscriptions
Currently the queue/subscription trigger only works with queues and subscriptions that does not use sessions (RequiresSession = false). It would be very useful if the runtime would detect that sessions are enabled and adapt accordingly. As far as I can see, the actual function code would not even have to be aware.
7 votesI’ve added a feature planning item for this in our GitHub – https://github.com/Azure/azure-webjobs-sdk-script/issues/563
-
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.
7 votes -
5 votes
- Don't see your idea?
