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. Add binding support for Append Blob storage for Python and JavaScript functions

    If it is supported, it is not in the documentation. It is documented for C#.

    2 votes
    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 →

    Under review because we have been evaluating how to surface this in other languages but is something we plan to do. Pending review and hoping to circle back. Part of a larger effort called “rich bindings” to allow easier integration with underlying Azure SDKs as bindings.

    -
    Jeff

  2. Upgrade CosmosDb binding to support new SDK (v3)

    New CosmosDb SDK have been released but the Cosmos Db binding still uses the old one.

    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 →
  3. Bind to QueueTrigger using HostId

    I would like to bind to a queue with a name including the function runtime host name (referenced as HostId in some doc). %AzureFunctionsWebHost__hostid% works when that value is set explicitly, but I cannot access it when the default HostId is used.

    1 vote
    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 →

    This feels a bit problematic – I’m not quite sure what is attempted here. It sounds like you want one queue per instance of the host, but hosts can be created and disposed at anytime so wary of allowing any dependencies on binding to an instance of the host. Feel free to add more context into the scenario and what is hope to be achieved.

    -
    Jeff

  4. Use a more unique query param than "code"

    I ran into an issue with an Oauth redirect because the Oauth provider (Kloudless) was also using the code query param for the Oauth redirect. Since the function required this query param I was not able to get the code sent by Kloudless to get an access token. Therefore, I had to just make the function anonymous, since there is no way for me to have Kloudless send it in the headers( I have no control over that). The query param Azure uses for authentication should not be such a vanilla query param. It should at least be like ms-code…

    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 →

    Having this configurable makes a ton of sense. Perhaps this could be a host.json setting or similar. We will look into it.

    It’s worth noting that for clients that can set headers, the, x-functions-key header is a good solution here. That of course doesn’t apply to the OP’s case.

    - Matthew

  5. CosmosDB Output bindings should have an option to prevent overwriting a document that changed while the function was executing.

    Currently if you have an Azure function with CosmosDB input and output bindings (with the intent to process and update a document) there is no way to specify that the document should not be overwritten if it was changed (by another entity) between the time the function was invoked and the time it completes and performs the CosmosDB output binding document update operation. That makes the use of input and output bindings together in a single function pretty much worthless for processing and updating a document. The function should return a 409 Conflict error if the etag on the document…

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

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Bindings  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Azure Functions

Categories

Feedback and Knowledge Base