Azure Event Grid

Azure Event Grid is a fully-managed intelligent event routing service that allows for uniform event consumption using a publish-subscribe model. Use Azure Event Grid to react to relevant events across both Azure and non-Azure services in near-real time fashion.

How can we improve Azure Event Grid?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Allow batching of events to Azure Functions

    Currently only a single event can be pushed to an Azure Function.
    Would be nice to have batching functionality like Event Hubs has for Azure Functions:
    https://docs.microsoft.com/en-us/azure/azure-functions/functions-host-json#eventhub

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

    We’ll send you updates on this idea

    1 comment  ·  Event Handlers  ·  Flag idea as inappropriate…  ·  Admin →
  2. Make eventgrid send events to a servicebus queue

    Currently event grid can publish to event hubs, storage queues and event hubs.
    It would be great if it could also publish to service bus queues.

    That way we get events into the brokered infrastructure with auto-forwarding, delays, queue fallbacks and everything.

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

    We’ll send you updates on this idea

    1 comment  ·  Event Handlers  ·  Flag idea as inappropriate…  ·  Admin →
  3. Reuse of Event Grid subscribers

    It would be great to reuse a subscriber(endpoint) such a Webhook. A dropdown where its possible to choose already configured endpoints.
    If the same webhook is used for several topics and it needs to be changed (e.g. auth code on Azure Function) it would have been great to do it once and not on all endpoints.

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

    We’ll send you updates on this idea

    1 comment  ·  Event Handlers  ·  Flag idea as inappropriate…  ·  Admin →
  4. Allow Webhooks to be delivered into VNETS

    Currently Webhook events can only be delivered to public IPs.

    For security reasons, we have a situation where we liked to be Webhook events to be delivered to VMs, Kubernetes Clusters etc. inside a VNET.

    As the target VNET can only be configured with permissions to this VNET, this would also ease the for requirements on authentication on both sides (for which there are other improvement suggestions).

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

    We’ll send you updates on this idea

    0 comments  ·  Event Handlers  ·  Flag idea as inappropriate…  ·  Admin →
  5. innavjn.9.8.0

    jikio.6.0.1

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

    We’ll send you updates on this idea

    0 comments  ·  Event Handlers  ·  Flag idea as inappropriate…  ·  Admin →
  6. Explicit option for validating the subscription

    Currently there are two ways of validating the subscription it's either using Validation code or using Validation URL.

    Currently the Create EventGrid REST API return 201 instantly and wait for 10 mins for manual verification for event subscription if Validation code does not exist.

    Can you provide expicit option for validation the subscription? Maybe default would be validationURL if not provided.

    I would recommend our customer to use Validation code verification only but incase they fail to write that code. We need to handle the fall the 10 min scenario.

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

    We’ll send you updates on this idea

    0 comments  ·  Event Handlers  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Azure Event Grid

Feedback and Knowledge Base