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 F# scripts (.fsx) in v2 and v3

    F# script usage is about to become much more prevalent due to the improved "#r nuget" imports in F#5. Azure Functions v2 and v3 should support F# scripts so that we can avoid having to create a "function project" when a a simple .fsx would suffice.

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

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  2. Binding for O365 Mailbox - Trigger on incoming emails

    Would be really nice to bind to an office 365 account and trigger a Function for inbound emails. This is available in Logic Apps but not in Function Apps.

    22 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 →
  3. New Built-In Roles for Azure Functions

    Hi,

    It would be nice to have a built in role for Azure functions, As many companies are moving towards more and more DEVOPS teams and it would be very handy to have this Built In role which will enable them to self serve for some of the operations like.


    1. Enable the Function App

    2. Disable the Function App

    3. View the Function App

    I tried to create a custom role but it is giving them way too less ( Not able to enable or disable) or way too high permissions ( Write ability to modify the code inside).

    Is this on…

    11 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 →
  4. Support gRPC in azure function as trigger

    gRPC is a standard for microservices and cloud-native solutions nowadays. It should be supported by azure functions, durable functions and API Management.

    22 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. Allow Key Vault references to access secrets behind Key Vault Firewall

    Key Vault references cannot currently be used to access secrets in a vault that has been configured with Key Vault Firewall / service endpoints.

    It should be possible to resolve secrets from Vaults configured this way (provided the web app / function app is configured with the right VNET integration).

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

    We’ll send you updates on this idea

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

    18 votes
    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 →
  7. Support visibilityTimeout of Queue Trigger to be maintained after restarting Functions host.

    The automatic retry with visibilityTimeout of Queue Trigger happens when the function host is up and running.

    But after restarting Functions host, sometimes retry interval does not refer to visibilityTimeout.

    Could you please support visibilityTimeout to be maintained after restarting Functions host?
    https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-error-pages#retry-support

    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 →
  8. managed mysql connection pooling proxy for azure function

    In short: AWS RDS Proxy equivalent solution for Azure.

    Using managed RDBMS like mySQL from FaaS is often said to be a bad practice because of difficulties of handling connection; FaaS might finish before closing its connection, might consumes too much connections when requests burst.

    Instead, using connectionless database is encouraged, but in many usecases, RDB's functionality is still preferred over connectionless DB(such as CosmosDB), because of its flexibility of queries and transaction.

    AWS resolves this dilemma by providing a managed connection pooling point called RDS Proxy.

    https://aws.amazon.com/rds/proxy/?nc1=h_ls

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

    We’ll send you updates on this idea

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

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

    We’ll send you updates on this idea

    9 comments  ·  Bindings  ·  Flag idea as inappropriate…  ·  Admin →
  10. Support for KeyVault References on KeyVaults with network restrictions

    Support for service endpoints and private endpoints. If the KeyVault has restrictions on network access the KeyVault references break in the app settings.
    https://docs.microsoft.com/en-us/azure/app-service/app-service-key-vault-references

    2 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 →
  11. Network Access Restrictions should support Network Service Tags

    When configuring network access restrictions (see https://docs.microsoft.com/en-us/azure/app-service/app-service-ip-restrictions), Function Apps currently only support IP Ranges. This results in static configurations to dynamic addresses such as Azure Data Center IP ranges.

    To align with the rest of the Azure platform's network access restrictions it should support the use of Network Service Tags. This will allow changes to Azure Data Center IP ranges to be processed automatically and not create a service and maintenance issue.

    Network Service Tags - https://docs.microsoft.com/en-us/azure/virtual-network/service-tags-overview

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

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

    We’ll send you updates on this idea

    20 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Better support for OpenAPI and API-M

    It should be easy to create an API in azure functions, annotate the query arguments with documentation and examples, then export it to API-M - Currently this is difficult.

    First OPENAPI support requires hunting around for the appropriate NUGET packages OpenAPI.NET.CSharpAnnotations - which is in Beta for over year, then you need to export out the definition via a custom endpoint, then that wont appear with the imported azure function in the API-M - so you need to merge it in - etc - All in all its very messy

    Ideally Azure function would support native annotations for openAPI, these…

    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 →
  14. Support Ubuntu 20.10 with repo

    Simple, please support Ubuntu 20.10 with repositories and the rest.
    Thx!

    1 vote
    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 →
  15. integration with App Config

    It would be nice if Function apps would work with Azure App Config. Currently all the connection strings have to be hard-coded into the app or setup as local environment values (in local.settings.json or project's Environment settings) .

    We have been trying to move ALL of our sensitive configuration (connection strings, ect) to Azure App Config and Azure Key Vault. Our Function Apps are sticking out like a sore thumb in this regard, and we are considering converting all our Function Apps to something else because of this.

    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 →
  16. Can you add Scopes to Google Authentication in Function App

    For some reason Scopes aren't included in the Google Authentication / Authorization portion of the Function App and when I try to authenticate using Google it fails and I get the error message that Scopes are required. They are available for Facebook and Microsoft and authentication works fine.

    1 vote
    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 →
  17. Azure Functions should be highly available

    When updating an Azure Function your service become unavailable. During a recent deployment we saw a series of error code such as 503, 404, 502, and 401 (in that order). This is unnecessary and violates the widely recognized high availability attribute of serverless services. I recognize that one is able to use a slot and then swap it into the target slot but this should be the default behavior of every slot, including (or especially) the default slot.

    Not providing a high availability guarantee by default causes faults unnecessarily and requires every one of your customers to solve/mitigate the circumstance…

    1 vote
    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 →
  18. Azure Functions should synchronize triggers with every update

    Currently you can update the package/zip/contents of an Azure Function and it will not automatically scan for updates to the trigger definitions. To get any alterations to triggers to be recognized by the Azure Function infrastructure you must either restart the AppService or run an explicit trigger synchronization using a command such as follows:


    az resource invoke-action --resource-group ${resource_group_name} --action syncfunctiontriggers --name ${function_app_name} --resource-type Microsoft.Web/sites

    This circumstance breaks down to:
    "You have to declare your triggers in the format we tell you to declare them in AND You have to tell us to actually load and use that declaration"

    Even…

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

    We’ll send you updates on this idea

    0 comments  ·  Bindings  ·  Flag idea as inappropriate…  ·  Admin →
  19. Durable Azure Function Development By Visual Studio Not VSCode

    1- We want the function to be development together with other related projects solution
    2- We don't like VSCode

    1 vote
    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 →
  20. 1 vote
    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 →
← Previous 1 3 4 5 11 12
  • Don't see your idea?

Azure Functions

Categories

Feedback and Knowledge Base