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.

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

    23 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. Generate signature header for event consumers

    My team is exploring using Event Domains to provide webhook capabilities to 3rd party consumers. A few of our stakeholders have concerns about relying on a query string parameter as the security mechanism to protect webhook consumers from spoofed event payloads.

    Ideally, our event consumers would be able to verify the sender of an event by inspecting a signature somewhere in their request (likely a header) that only "we" (or Event Grid) can generate.

    However, in order for us to do this as event producers, our team would either need to employ one, global, difficult-to-rotate private/public key combo for all…

    8 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. support blob update

    In addition to blob creation and deletion, please add blob update when metadatas are updated

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

    We’ll send you updates on this idea

    2 comments  ·  Event Handlers  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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 →
  5. provide endpoint to explicitly acknowledge successful receipt of events

    If processing of an event handler takes more than 30 seconds, then event grid considers this a failed event delivery, and will incorrectly and unnecessarily retry delivering the event to the subscriber. A subscriber should be able to explicitly acknowledge the receipt of an event, before it finishes processing, otherwise event grid cannot be used with handlers that can take more than 30 seconds to complete. Please note that using LongRunningOperationRetryTimeout does not solve this problem, because processing times generally are not fixed and not predictable, and setting the timeout to a very large number, will have a negative impact…

    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 →
  6. 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 →
  7. Include User-Agent header on event delivery

    My team has started providing webhook capabilities to 3rd party consumers using Event Domains to fulfill the delivery of event messages. One of our customers has requested that our webhook payload requests include the User-Agent header. This seemed like a reasonable request and a best practice, supported by most other webhook vendors I've come across (though not always documented).

    A few examples where this is documented:
    Github uses a User-Agent value of GitHub-Hookshot/##
    Box uses Box-WH-Client/##

    Ideally, I’d like for our team to be able to set the User-Agent header that our event consumers see, but I understand if that…

    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 →
  8. Ability to set UserProperties for Service Bus Topic when used as an event handler

    The docs (https://docs.microsoft.com/en-us/azure/event-grid/handler-service-bus) make it seem like we can set the "aeg-event-type" header when publishing to an Event Grid Topic, but in my experience it is always set to "Notification" when routed. I don't see a way to pass the event-type information in a way to leverage Service Bus Topic Filters/Rules? Perhaps the header pass through suggestion (https://feedback.azure.com/forums/909934-azure-event-grid/suggestions/33306310-header-pass-through) could be used to set User Properties?

    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 →
  9. Event Grid to Azure Batch

    Make Azure Batch and AKS endpoints direct event handlers in Event Grid without the need to use Azure Functions to parse the request

    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 →
  10. Enrich messages with AEG Subscription

    Allow to pass some metadata from Subscription to the event data object.

    It will be very useful if the Labels property will be added to the data object of the event message. In this case, we can pass to the subscriber some metadata stored in the Subscription Labels property.

    Thanks

    Roman

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

Categories

Feedback and Knowledge Base