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

  2. Support .Net Core 3 Run time and NetStandard 2.1 function assemblies

    Add support for functions implemented in .Net core assemblies compiled against NetStandard 2.1 running on the .net core 3.0 run time.

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

    We’ll send you updates on this idea

    0 comments  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →
  3. Durable Functions - Prioritize activities queue

    On my project we tried using durable functions with queue-trigger to process resource-consuming requests at a steady pace instead of being overwhelmed with hundreds of messages arriving at the same time. Fairly basic scenario for queues isn't it?
    But after few weeks of conversations with Azure Support team we ended up with conclusion that it isn't possible to achieve and had to remake project to other technology.

    Need to say we had to configure maxConcurrentActivityFunctions setting to limit the load on our SQL DB, so "processing power", available for orchestrators got limited.

    This resulted in situation when hundreds of messages…

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

    We’ll send you updates on this idea

    0 comments  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →
  4. Inlcude CallActivityAsync() with void return type in IDurableOrchestrationContext to enable testing with mock

    We tried to unit test orchestrator with a mock IDurableOrchestrationContext, but CallActivityAsync() with void return type is in DurableContextExtensions rather the interface. The workaround we did is to return a dummy value from the Function, and test it as CallActivityAsync<TResult>() from the IDurableOrchestrationContext.

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

    We’ll send you updates on this idea

    0 comments  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →
  5. local development

    I have had two separate issues where Azure Functions have stopped running in the cloud but work fine on my development machine. One was the extensions.json file not being generated in v1.0.24 of the SDK and another is having to manually add references to the SqlClient package. Neither of which we could replicate locally. Is there a way to ensure that the Azure Functions runtime in VS2019 is the same as what is running in the cloud?

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

    We’ll send you updates on this idea

    0 comments  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →
  6. Ability to schedule Azure function runtime updates from the portal

    Requesting the ability to be able to schedule Azure function runtime updates from the portal. At present the runtime updates are pushed by Microsoft at random times which could impact service availability and customer experience. We need the ability to be able to either define a schedule for the function runtime updates or be able to manually perform those updates at a time that is convenient to the customer.

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

    We’ll send you updates on this idea

    0 comments  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →
  7. Support for 64 bit Powershell runtime

    There is currently no support for loading 64-bit modules into Powershell as the runtime architecture is 32-bit. Even when 64-bit platform has been enabled in Configuration on portal (and the configuration option Use32BitWorkerProcess verified as false).

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

    We’ll send you updates on this idea

    0 comments  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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 →
  • Don't see your idea?

Azure Functions

Categories

Feedback and Knowledge Base