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 documentation and guidelines to test Java Functions

    Currently there are documentation exists on testing java functions. Nice to have a document explaining how to unit test and perform integratioin test on various java functions(bindings)

    1 vote
    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 →
  2. Code-To-Function - Specify git location for the function code.

    Code-To-Function is idea similar to the Code-To-Container when where Azure function has only pointer to the function code git location.

    Additional features could -"well known branches" where master is associated with prod and trunk with pre-prod deployment slots.

    The failure of the exxecutin would configurably create an issue in the Git

    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 →
  3. certificate

    Can Azure Functions support SSL certificate for consumption plan?
    I found on https://docs.microsoft.com/en-us/azure/azure-functions/scripts/functions-cli-configure-ssl-certificate that "To bind an SSL certificate, your function app must be created in an App Service plan and not in a consumption plan."

    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 →
  4. Offer ability to train a Neural Network Model using Azure Functions with GPU

    Offer ability to train a Neural Network Model using Azure Functions with GPU. this will be very useful, especially if you want to train Models using different parameters or hyper-parameter optimization.

    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 →
  5. EventHub Trigger filtering based on properties

    It would be great to be able to provide a filtering expression in the binding of an eventHubTrigger. Using this I could configure my function to only be invoked for certain events that match the filter. For example, I store a property called "eventType" in the application properties of each event. My function is potentially only interested in events of one or more specific types. Currently I code this logic into the function, which works fine. However, it counts as an unnecessary invocation and increases the cost. Ideally the filtering would take place in the host and not incur a…

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

    Unsure on this one but marking as unplanned. The filtering would also have to happen at the client to preserve ordering. However even if we did the filtering before the execution it’s still consuming compute so I don’t think it makes sense for it to be “free.” Just because the trigger is doing filtering before execution wouldn’t necessarily negate the price aspect. And since filtering often has some custom parsing / decoding / conditions it’s almost better to do it in code.

    -
    Jeff

  6. Expose StorageClientFactory or QueueProcessorFactory to enable triggering on client-side-encrypted queues

    With WebJobs, a custom StorageClientFactory can set an EncryptionPolicy in the DefaultRequestOptions such that encrypted queue messages are transparently decrypted when triggering a WebJob.

    Alternatively, the EncryptionPolicy can be set on a queue by queue basis using a custom QueueProcessorFactory.

    If these, or a more general way to modify the JobHostConfiguration were provided, then we would be able to store the storage connection string in Azure KeyVault and use client side encryption with Azure Functions apps.

    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 →
1 2 4 Next →
  • Don't see your idea?

Azure Functions

Categories

Feedback and Knowledge Base