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

    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 →

    Marking to needs feedback per below:
    Nothing planned but still curious on this one. I think the ask is that you could decrypt on trigger. I expect trigger would work today but you’d have to have decrypt in code per execution. Is hope to decrypt before execution? – Jeff

  2. Add VNet integration to the Consumption plan

    Currently, the only serverless solution for VNet integration is to upgrade to the premium consumption plan.

    It seems like overkill to upgrade to a whole new (way pricier) plan, to simply use a static outbound IP with Azure functions.

    0 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 →
  3. support for grpc in azure functions and api management would be a great help

    Now that grpc is a full member of .net it would be great that it is also supported in azure functions and in the azure api managment

    0 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 →
  4. Misleading warning on function Integrate blade

    The functions Integrate blade displays a warning that the bindings are missing the required direction property. This warning seems to display for all deployed functions even if the property is included.

    0 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  ·  Portal  ·  Flag idea as inappropriate…  ·  Admin →
1 2 9 10 11 13 Next →
  • Don't see your idea?

Azure Functions

Categories

Feedback and Knowledge Base