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.

How can we improve Microsoft Azure Functions?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Retrieve function app keys from ARM template

    Make it possible to set/retrieve function app keys via ARM templates.
    This will make it easier to store it in the settings of an other service while rolling out an environment.

    29 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  2. Allow moving Function from Consumption to Service Plan

    Currently if you deploy your function on a consumption plan there is no way to move it to an existing Service Plan like any other App Service.
    You would need to delete the existing one and redeploy it..

    18 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Quick update here – with the announcement of the premium plan we do support moving from consumption to a premium plan. Today this may not work for all consumption apps in a region only because some consumption apps may exist in a “webspace” that doesn’t yet have premium turned on. That said we have CLI commands rolling out in the next few weeks to make this seamless.

    Moving to app service plan is a bit trickier as the actual code often lives in a different place on an app service plan (app service local storage) than where consumption needs them (azure storage files) – so moving may not work and currently don’t have any immediate plans to do like “code migration” in addition to changing plans.

    You can see a sample of moving plans between apps in this sample here as well: https://github.com/Azure-Samples/functions-csharp-premium-scaler

    -
    Jeff

  3. Add support for Open API (Swagger 3)

    Azure Functions currently supports Open API (Swagger 2) (https://azure.microsoft.com/en-in/updates/announcing-azure-functions-open-api-swagger-support-preview/).

    Now that Open API 3 has been released, it would be helpful if the latest standard could also be supported

    17 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  4. 15 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  5. Don't 'hardcode' the storage account connection string for the storage account that backs azure functions

    Currently each Function App has an application setting string "WEBSITE_CONTENTAZUREFILECONNECTIONSTRING"which is a fixed (=hardcoded) connection string. This breaks when performing key rotation on the connection string and is opaque to diagnose since that setting is automatically setup by the portal UI/wizard.

    Can you instead just store the subscription ID and storage account name and then fetch the latest connection string for the storage account using the management API? This will make sure that the function app survives storage account key rotations

    14 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  6. Support authentication for Azure Function Core Tools

    Azure Functions has been great, especially the ability to run the Core Tools locally. However, there are often scenarios where you return data depending on the currently authenticated user. This appears to be supported in Azure Functions in Azure now but there are no options within the Core Tools. This would be hugely useful for local development.

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

    We’ll send you updates on this idea

    1 comment  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  7. Want to be able to enable Application Insights via the azure cli when creating a function without having to rely on an ARM template.

    I want to be able to enable Application Insights via the azure cli when creating a function without having to rely on an ARM template. It seems like all you should have to do is have an option to say enable it and an option to state location information.

    4 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  8. Azure auth populate request.user

    When using the azure auth over functions, specifically those that take a http trigger, it would be great if it would populate the request.user in a similar way you can do using node.js and passport (https://github.com/Azure-Samples/active-directory-b2c-javascript-nodejs-webapi/blob/master/index.js) rather than just providing some headers.

    This would make it much easier to work with authenticated users and interact with their information

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

    We’ll send you updates on this idea

    0 comments  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  9. Specifying a name for a premade function

    If no function is present in a Function App, the “getting started” assistant is shown which allows adding a premade function. However, you can’t specify a name for the resulting function there, which is why you’ll end up with insignificant names such as “HTTPTriggerCSharp1” or “HTTPTriggerJS1”. It would be great if the user could optionally specify a function name in this dialog.

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

    We’ll send you updates on this idea

    0 comments  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  10. better error handling for EventGrid calls that you want to retry

    The Microsoft sample documentation (link below) suggests using a Run method with void return type. This doesn't allow convenient handling of errors that you want to handle by getting EventGrid to retry invoking the Azure Function again after a period. For example, my Azure Function sends a message to a server (Azure Container Instance) which may be down. In this situation I want EventGrid to invoke my Azure Function again after a period when the server might be up. However, with a void return type my only option seems to be that of throwing an exception (InvalidOperation?). Agreed, I could…

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

    We’ll send you updates on this idea

    1 comment  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Azure Functions

Feedback and Knowledge Base