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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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....

    https://github.com/peterhuene/azure-functions-rs

    98 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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.

    28 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    unplanned  ·  3 comments  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  3. Support for Azure Managed Service Identities in EventHub (and other) triggers

    In Event Hub, I can add my Function App's MSI as a data reader, but in the function I cannot use trigger bindings to read from the queue without using a SecureAccess Key. We are trying to go password free wherever possible, and Azure has been promoting this course of action, so why do we need secret keys for reading from the queue? It then forces us to create and share a secret key for partner teams to read from our queue, rather than just permissioning them in Event Hub.

    16 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Bindings  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add Elastic Scale Plan (pre-warmed instances) in Gov Cloud

    When auto-scaling the number of instances for a Function, API requests are routed to new instances before they are ready (warmed up) causing failures/timeouts for those requests. In regular cloud, this is solved by using the Elastic Scale consumption plan that lets you specify the number of pre-warmed instances (https://docs.microsoft.com/en-us/azure/azure-functions/functions-premium-plan#pre-warmed-instances). Please bring this same plan to Gov Cloud.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  5. Please eliminate sandbox restrictions while running in Docker

    Right now the sandbox applies to azure function apps even when they're running in docker. Docker is the sandbox in that case. Further, things like System.Drawing.Common aren't effected on Linux the same as they are on Windows so there should be no issue requiring the sandbox to interfere.

    So Azure Functions should disable the sand-boxing when running in docker entirely.

    Failing that, it should disable the System.Drawing.Common limitations if running on Linux.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    unplanned  ·  1 comment  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →
  6. Allow running headless Chrome (or other browser) in Function apps or Web apps

    Basically it's this:
    https://cloud.google.com/blog/products/gcp/introducing-headless-chrome-support-in-cloud-functions-and-app-engine

    Now obviously Google has a bit of an advantage here what with Chrome being their own tech but there are so many blogs out there with people talking about complicated Docker solutions just to run headless Chrome in the cloud.

    It would be great if we could get a solution where we could run Puppeteer in much the same way, or allow web apps to run Chrome without having to be inside Docker and we could manage a pool of Chromes without having to manage Docker as well.

    56 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →

    Headless Chrome requires some libraries to be installed that aren’t available in the containers we use in Linux consumption. You can, however, run your function app in a Docker container with the libraries installed. Custom containers are currently supported in the Premium and App Service plans. Take a look at this example from a community member of a Dockerfile with the dependencies: https://github.com/estruyf/azure-function-node-puppeteer/blob/master/Dockerfile

    - Anthony

  7. Specify a custom window for platform updates to WebApps, Functions, etc.

    I want to be able to request platform upgrades only restart my site within a specific window, say outside of business hours.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →

    This is great feedback.
    We strive for platform upgrades to happen transparently to you, however, they will restart every worker for your function app while performing a platform upgrade.

    We do not currently have the infrastructure to make this publicly available, but keep the votes coming!

    Thanks!
    Alex
    Azure Functions Team!

  8. 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…

    27 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  9. Connecting to PostgreSQL Database hosted in Azure (Linux + Python)

    Azure Functions Bindings works with Azure Cosmo DB, but as of now there is no way to create a Function that writes to a PostgreSQL db stored in Azure. Locally, I can just use Psycopg2 in Python to connect, but this isn't possible without creating a custom container with libpq-dev (for pg_config).

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    unplanned  ·  1 comment  ·  Bindings  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow moving from AppServicePlan to Consumption plan (in Azure portal)

    It should be easy to move between hosting plans for Azure functions so we can change this based on the current needs. At the moment, I would like to move away from app service plan for a lot of functions (use consumption plan instead), but in the future, high continous demand might move some back to an app service plan. Changing between the to modes should be as easy as scaling out on an app service plan

    I have read somewhere that there is a problem if a function was created as an app service plan because of missing storage.…

    16 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Portal  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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…

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    This 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

  12. 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.

    https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{name}/proxies

    7 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  15. ASP.NET Core MVC/Web API support

    Enable developers to create serverless applications using the ASP.NET Core Web API framework.

    81 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    11 comments  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  16. Add Event Domain or Event Grid output binding

    Add Event Domain or Event Grid output bindings to azure functions

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  17. SMTP Triggers

    Functions are great for building HTTP-based Apis. Our SMS-api supports both HTTP(S) and SMTP(Mail 2 SMS).

    In order to use Functions, we would need to be able to bind one or more email domains to it and use email as triggers

    2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Bindings  ·  Flag idea as inappropriate…  ·  Admin →
  18. Set environment variable override for AuthorizationLevel.Function key

    When running within the Azure Functions Runtime inside of a Docker container, we can't use AuthorizationLevel.Function as there is no way to retrieve the key from the runtime. It'd be great if we could directly set a function key in our compose.yml as an environment variable. For deployment, we just leave the environment variable blank and the App Service can set the keys.

    Related SO question:
    https://stackoverflow.com/questions/52174892/how-to-set-authorzationlevel-per-an-environment-condition-when-running-csproj-fu

    13 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5
  • Don't see your idea?

Azure Functions

Categories

Feedback and Knowledge Base