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.
-
Please support calls to System.Drawing.Bitmap ?
Hello Team,
Azure function v2 engine does not support calls to System.Drawing.Bitmap class. I understand that this limitation has been documented under https://github.com/projectkudu/kudu/wiki/Azure-Web-App-sandboxI find System.Drawing.Bitmap very useful when it comes to reading image files. Our current product (on .NET Framework) relies on System.Drawing for image processing and works very well. However we are unable to port to Azure because of the sandbox restrictions.
I request the team to consider this support in future versions of the runtime.
6 votesMy suspicion is that we will not do this. As you mentioned, the sandbox explicitly blocks calls like this. But, we will check to see.
- Matthew
-
PowerShell cmdlets for Functions
Customer is requesting support in PowerShell to Start and Stop an Azure Function app. For more info, please see https://stackoverflow.com/questions/56168831/how-to-stop-start-azure-function-from-powershell.
3 votesWe are currently working on having a PowerShell module to manage Azure Function applications.
A preview is available on https://www.powershellgallery.com/packages/Az.Functions/0.0.1-previewWe will be adding update function app before GA.
-
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.
36 votes -
Infinite Recursion Loop does not give error
I accidentally created an infinite recursion loop in my C# dll. This was hit during Azure function execution. However, instead of giving an error, the host would simply die with no error or further logging. While the loop should've been detected by me earlier, the fact that I got no errors lead me down the wrong path for a while and made it much harder to debug.
1 voteThanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.
-
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 -
Address Azure Functions Resiliency Weakness to Azure Service DNS issues
Azure DNS issue R50C-5RZ caused multiple core Azure function triggers to fail across our subscriptions due to loss of access to Storage Accounts.
The DNS issue made all our storage accounts temporarily unresolvable by DNS and because of the tight coupling with Azure functions, function triggers failed due to the inability to resolve storage account urls but did not recover when the DNS issue was corrected.
There were some Socketexception / 'remote host not found' errors logged in App insights but seemed to be no way to know that the trigger was in a failed state (unless a build up…
5 votesThis is an awesome idea!
We’re very unlikely to be able to reduce our dependency on DNS, but we can generally handle failing triggers more gracefully.“Handle temporary loss of a storage account without requiring a manual restart” is a scenario we’re targeting.
Keep the feedback coming!
Alex -
add proxy header removal option
Would it possible to not only override/add headers, but also remove header like x-forwarded-for.
5 votesThis is a valid request, but we don’t have an ETA.
-
Provide memory usage data in context object
It would be great if we could manage memory in realtime in our code. Please provide a method to check memory usage in the context object so that we can take mitigating steps in our code if there is not enough memory.
4 votesThis is a valid request but not currently planned – please keep the votes coming.
—Colby
-
When publishing through Visual Studio, create the storage account on the same region as the function
I deployed my function through Visual Studio, creating a new one on an existing resource group.
I chose to create a new Storage Account as well.
I chose eastus2 as the region for my function. But after the deployment succeeded, I noticed that the region for the storage I created during the functions deployment was set for Central US.
I'd like the created storage to be on the same region of the function. I double checked and there's no way to select a region for the storage you create in deployment time.
2 votesThis is valid, but not planned anytime in the short term – I’ll keep it open to track priority.
—Colby
-
Share RUs with a Serverless Function
A popular pattern is to build a REST API using serverless Function with Http trigger, backed by Cosmos DB. Serverless is a very popular paradigm, and Cosmos is the best cloud database, so it's no wonder that customers are interested in this combination. However, the problem in this scenario is the cold start of the serverless Function, which negates the low-latency benefits of CosmosDB provisioning.
It would be great to allow sharing the RUs provisioned for Cosmos DB collection with serverless functions running against the same collection. Let the Function execution consume some extra RUs, depending on the complexity of…
2 votesThis is not something that we are currently looking at doing.
We currently have premium functions available that remove the cold start challenge and hopefully would meet your current needs.
Thanks,
Eamon -
local settings json
Add the ability to create a template local.settings.json file in the dev tooling for VSCode and Visual Studio. Since local.settings is git-ignored by default, when a developer clones down a repo they often have to re-create a local.settings.json file. To do this it involves simply creating a bare json file and hand-coding the right schema/values. It would improve developer productivity to add a "New local settings file..." option to the dev tooling which creates the same skeleton file a dev is given in a new function project.
4 votesI don’t believe we plan on doing this, but it’s a valid ask, and I’ll leave open for feedback.
—Colby
-
openId connect plugin / guidance
In MVC, we have Microsoft OpenId Connect / Owin to secure the application using Hybrid flow with a Single Page Application on the front end.
The request is to have capabilities to move from MVC SPA (self hosted VM) to Serverless (Azure blob + Azure function as backend) to do Hybrid flow authentication.
1 voteI read this item as two things:
1. A desire for OIDC capabilities, in which case there is another item that may be related: https://feedback.azure.com/forums/355860-azure-functions/suggestions/13286541-enable-custom-3rd-party-authentication-providers
2. A desire for guidance for migrating from MVC, which we do not currently have a solution for.- Matthew
-
Geo-availability integration a la CosmosDB for Consumption Plan
For Functions in a Consumption Plan, it's a bit arduous to get them to be geo-distributed (have to set up deployment to all the various regions you want to support, add APIM/Traffic Manager to handle). It would be super awesome if Functions had a setup like CosmosDB where you deployed them once, then "lit up" the geos you want the code replicated to. Then, not too much different than the request in #214 , an "invisible" Traffic Manager service could be provided on the endpoint for the Function to hit the nearest geo to the end user.
3 votesThis is a great feature ask though we have no concrete plans on this right now.
We will check back to see if there is more community support.
Thanks,
Oded -
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…
26 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 Visual Basic language support
This would be a great way to extend the reach of teams with heavy VB skills and investment in existing VB projects.
1 voteNothing planned around this currently. Keep the votes coming.
-
Jeff -
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....
222 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
-
Add ability to restrict deployment from dev environments
I recently created a new function app in our team's tenant to handle some custom monitoring. Now that I'm done prototyping it and have it in a workable state, I've created an Azure DevOps build and release to handle publishing the app.
I need to do this, rather than simply use the CD from git branch option, because I'm using Typescript (currently unsupported), and need to install both node_modules and extensions for the app (because the app won't perform those steps itself based on package.json or extensions.csproj)
While the pipeline now works, I can't find a way to lock down…
1 voteNo current plans for this but it’s a valid feature request so I’ll leave open to keep votes coming.
As an aside, we support TypeScript now!
https://azure.microsoft.com/en-us/blog/improving-the-typescript-support-in-azure-functions/
—Colby
-
Add documentation and guidelines to test Java Functions
Currently there are documentation exists on testing java functions. Nice to have a document explaining how to unit test and perform integratioin test on various java functions(bindings)
1 voteLove the feedback. Keep the votes coming.
-Sonia
Azure Functions PM team
-
Fine grained function billing please
Please add a more fine grained billing please.
A minimum execution of 100 ms and 128 MB is to coarse. A lot of my functions execute within 10ms or less and use less than 128 MB of RAM.
Please add more fine grained executions possible (10ms or even per ms) and in smaller memory steps, maybe 16 or 32 MB.
Also make async execution time not count toward function execution time, because if is often not in our control (waiting for an slow external service, database or slow response writing because the caller of the Azure Function has a very…
3 votesHello, thanks for the feedback on this. This isn’t in our plans at the moment. we’ll keep this item around to observe demand for such finer granularity.
-
Manage Function Proxies using the Azure REST API
Similar to how functions work, it would be useful if we can programmatically manage Proxies within Functions using the Azure REST API.
7 votesWe are note planning additional functionality to Function Proxies.
Please use consumption billed API Management, and if they do not support this functionality open a uservoice against API Management.
Thanks,
Eamon
- Don't see your idea?