Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

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

    205 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    110 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    61 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  4. Function App Service support for Azure B2C

    If I build a web app using Azure B2C for authentication, I'd like to use it as the authentication provider for Azure Functions too. Although I can set up the same providers, using B2C would be cleaner and enable me to support users with local logins (traditional username and password) too.

    42 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  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

    40 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    37 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  7. 37 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  8. 32 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    12 comments  ·  Portal  ·  Flag idea as inappropriate…  ·  Admin →
  9. Add Open Connection count to Function App

    We are using a Function App for consuming events from an EventHub, to process each event we make 4-5 REST calls and we find that our S3 instances run out of outbound connections resulting in ETIMEDOUT errors. We opened a support case and we are troubleshooting. However to make it easier to debug and to allow us to put alerts in place it would be nice to have the number of open connections available through the Portal and be able to attach alerts..
    We tried to run netstat from Kudu but thisis not permitted (Access Denied)

    30 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Update: Still planned!
    -
    This is something that we have enabled internally, and are in the planning process of highlighting TCP connections for customers in the “Diagnose and Solve problems” tab. However, we do not have an ETA yet.

    Thanks for the feedback!
    Alex
    Azure Functions Team

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

    25 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  11. Blob trigger support with Service Principle/Managed identity

    We are trying to setup a Blob Triggered Function, but we have a limitation to use only Service principal/managed identity to access the storage because of the security concerns in directly using access keys.

    We did not find a way to by-pass blob trigger to using connection string.

    Theoretically, since Blob Storage is integrated with Azure Active Directory, it should be possible to provide the right RBAC permissions on my Blob Containers so that the Function's identity (Managed Service Identity)/Service principle has whatever permissions are necessary to create the trigger and read from the blobs.

    We are expecting azure functions…

    24 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  12. Functions Should support Custom Trigger events

    Functions Should be able to support custom triggers
    In my case i need a trigger from azure redis which is not possible in functions now.

    19 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  13. use key vault reference in local.settings.json

    would like the ability to use the new key vault reference in local.settings.json for local debugging instead of needing to have secrets in plain text. this would allow dev teams to leverage key vault as the central location for secret management.

    14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Bindings  ·  Flag idea as inappropriate…  ·  Admin →
  14. Enhance Azure Durable Function performance by enabling use of Redis as a backend store

    Durable functions are great, however they do run into some performance bottlenecks when working with fan out for really large numbers of tasks, reduce the overhead caused by Azure Storage reads and writes by enabling an option to use distributed in memory storage such as Azure Redis to implement the required backend queues & stores.

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. python support for durable function

    As far as I can see durable function is supported only for C#. It would be nice to have a python based azure function orchestrator.

    Or is there a way to orchestrate python based Azure function using C# durable function or is this a stupid question :P

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  16. More Descriptive Error Message - Platform Version discrepancy

    When an exception is thrown based on incorrect platform version please provide more descriptive error messages. The error message received was:
    'Could not load file or assembly 'Microsoft.PrivacyServices.CommandFeed.Client, Version=1.2.0.0, Culture=neutral, PublicKeyToken=74a17481026a49c7'. Could not find or load a specific file.'

    A message indicating could not load foo.dll, found 64-bit version.  App is 32-bit would be very helpful in determining resolution.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    We have work underway and shipping soon to better surface host errors in the portal. Some of this is rolling out this month. We will only be able to bubble up errors as descriptive as the libraries expose, but at least then working to bubble up.

    -
    Jeff

  17. Add error for missing application setting

    Function apps do not show an error when you try to reference an application setting that is not there (or variable misspelled), it returns an empty string. This can lead to local testing functioning properly because the local.settings.json is complete, and then unclear breakages once published to Azure, especially if you are passing that setting on to an API that doesn't have verbose error output.

    At the very least the app should output a warning that it is returning an empty string because application setting X does not exist.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Feature  ·  Flag idea as inappropriate…  ·  Admin →
  20. What is the timeline for supporting the new Azure SDKs?

    I really want to get rid of the connection strings in my functions and I want to be able to switch to the Azure.Identity SDK for auth. I understand that this will be a breaking change, however some communication about the plan would be nice.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

Azure Functions

Categories

Feedback and Knowledge Base