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. Header pass-through

    For a custom topic, it would be nice if http headers were passed through the eventgrid. This way extra information (like correlationid, token) could be passed through the eventgrid.

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

    We’ll send you updates on this idea

    unplanned  ·  5 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  2. Support file (share) storage events

    In addition to blob creation and deletion, please add file (share) storage support.

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

    We’ll send you updates on this idea

    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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).

    29 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. New Event Publisher for Azure AD

    I would like to see an event in Azure Event Grid when a new user gets created in Azure AD (also update and delete).
    Best would be to have a Microsft Graph integration in Event Grid:
    Subscribe to events in Microsoft Graph which in turn get published to Event Grid...

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

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add Append Block Event on Blob of type Append Blob in Storage Blob Containers

    Today BlobCreated event support only Block Blobs.
    For Append Blob there is only 1 event when Blob is created with size 0
    and there no events of Append Block which actually write to the blob data. As a result - no visibility that Blob was written with any data, just visibility of empty blob creation :/

    https://docs.microsoft.com/en-us/rest/api/storageservices/append-block

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

    We’ll send you updates on this idea

    0 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  6. AdvancedFilters (2018-09-15-preview) - add more operatorTypes

    Currently this preview has available the following operators for strings:

    StringContains
    StringBeginsWith
    StringEndsWith
    StringIn
    StringNotIn

    I am supprise what was a reason to not implemented the following operators:

    StringNotContains
    StringNotBeginsWith
    StringNotEndsWith

    beside that, we don't have a wildcard (*) feature to simplify expression.

    Please, could you add the above operators in this preview?

    Thanks
    Roman

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

    We’ll send you updates on this idea

    1 comment  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  7. CloudEvents schema: Variables in WebHook url

    Since in CloudEvents 0.1 we deliver single events, it would be useful to be able to pass event properties into the webhook url. This would allow easy routing on the subscriber side. For example a spec version variable and an eventType variable would allow for an webhook url like this:

    https://api.someservice.com/{cloudEventsVersion}/{eventType}/{eventTypeVersion}
    which would result in something like
    https://api.someservice.com/0.1/com.someservice.contacts.added/1.0

    We could then easily build an api that supports all kind of versions and eventTypes without a long list of single eventType subscribtions.

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

    We’ll send you updates on this idea

    1 comment  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  8. Enable/Disable Event Subscriptions

    I often test my event grid subscriptions locally using ngrok, as suggested in some of the tutorials. The problem is that when I want to switch between test endpoints and production endpoints, I have to copy-and-paste the appropriate endpoint in the subscription configuration.
    What I'd like to see is a "Enable" checkbox for event subscriptions. I would have a subscription for both test and production endpoints, and only enable the one I want to use.

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

    We’ll send you updates on this idea

    2 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  9. Routing Event Grid Event to a specific partition in Event Hub

    While creating event subscription and using eventhub as endpoint there is no way of specifying the partitionID to which all messages should be sent.This is used mainly to preserve ordering so that all events for the same publisher land in the same partition.
    This feature is available via event hubs SDK.
    Since Event Grid is now becoming the primary event routing service it would be good if we can add a feature of routing events to a particular partition to ensure ordering.

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

    We’ll send you updates on this idea

    1 comment  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  10. CloudEvents schema: Use 'ce-*' instead of 'aeg-*' headers and include eventType header

    According to the spec 0.1 CloudEvents support a range of headers. I have tried to use them in the NorthEurope region but failed to receive them.
    My idea was to build an aspnetcore app and route the requests based on the 'CE-EventType' as described here:
    https://github.com/cloudevents/spec/blob/v0.1/http-transport-binding.md#3132-http-header-values

    Unfortunately I can not see any 'ce-' headers at all, only the existing 'aeg-' headers, which are covering some properties, but unfortunately not the eventType.

    So my request would be to use the 'ce-' headers if the subscriptions delivery-schema is set to cloudeventv01schema.

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

    We’ll send you updates on this idea

    0 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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 →
  12. Allow to specifiy a delay for event delivery

    Would be great to be able to specify a delay after which an event becomes visible. This way, an event source could generate an event that would be delivered to subscribers after some time. In a way, it would be similar to the ability to specify delay in queues. Ideally, this delay could range from a few milliseconds to a few months.

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

    We’ll send you updates on this idea

    4 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  13. support blob update

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

    7 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 →
  14. Provide Clear command for EventGrid

    During development EventGrid can easily become full of events that you don't want to process. We need an easy way to clear the queue - i.e. something like the old MQSeries clear command. This should be available programmatically as well as from Azure Portal.

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

    We’ll send you updates on this idea

    0 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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…

    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 →
  16. Check for null/not null in Event Grid Advanced Filters

    Add advanced filter options to Event Grid subscriptions to allow filtering on whether a specific data node exists (or does not exist) or does/does not contain a null value

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

    We’ll send you updates on this idea

    0 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  17. Signing requests and verifying signature on response

    We are exploring using Domain Events in a multi tenant financial environment to allow our customers to get notifications around transaction status changes. However, our webhooks need to be signed and the response from the customer must also be signed with a digital signature. Unfortunately Event Grid only requires a 200 response in order to consider a webhook successful whereas we would also require the response to be signed with the correct signature. It would be nice if we could add custom rules/policies that have to be fulfilled for the response to be deemed successful.
    Perhaps introduce request/response policies similar…

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

    We’ll send you updates on this idea

    0 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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 →
  19. Better Azure Portal commands

    Azure Portal should provide more command to support Azure Event Grid. For example,

    STOP/START = stops any events being accepted. This is a useful way to take something out of service

    CLEAR = clears all events from EventGrid - very useful during development - see other post

    I would also like a summary of my queue like last message details, number of messages waiting, messages set for retry, etc. This might be available in Application Insights, but that's a nuclear option for me.

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

    We’ll send you updates on this idea

    0 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  20. Custom Events should be schema agnostic

    When I first read about the idea of custom events, I would expect to ingest any kind of event, straight from the producer to event grid topic without any transformation required.

    In example, if I want to receive a commit event from github via webhook to Event Grid, I have to receive it through a middleware(azure function) to parse it to EventGrid expected schema, otherwise it will fail, and this brings a lot extra work that should not be necessary, also makes my producer coupled with Event Grid.
    If I have to build up all these things to make the…

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

    We’ll send you updates on this idea

    0 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3
  • Don't see your idea?

Azure Event Grid

Categories

Feedback and Knowledge Base