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.

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

    We’ll send you updates on this idea

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

    17 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 →
  4. 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.

    17 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 →
  5. 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 →
  6. 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.

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

    11 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 →
  8. Add support for external OAuth2 servers for authentication at webhooks

    Currently the event grid supports only Keys and AAD integration to authenticate the event grid at the webhook endpoints.
    However, its is very common that internet facing web application endpoints are secured in a security domain of an external identity provider rather than the Azure AD. So in these cases, it is really helpful if the event grid can fetch access tokens from the external identity provider using client credential flow and send those tokens as bearer headers to the webhook endpoints.

    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 →
  9. 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 →
  10. Allow Event Grid topics and subscriptions to be in separate resource groups

    I should be able to create an Event Grid topic and an Event Grid subscription in seperate resource groups. The current limitation that they both need to be in the same resource group is problematic for automation in a microservices environment. The topic is owned by the publishing app, but the subscriptions are owned by the subscribing apps. I now have to have both apps deploying changes into the same resource group, meaning I can't use "Complete" mode and I now have to worry about junk not being deleted when items are removed.

    Allowing these topic & subscription to each…

    8 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. 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 →
  12. Unmatched Events - log unmatched events

    There doesn't seem to be a way to view unmatched events in any way.

    Imagine you start receiving unmatched events in Azure Event Grid Topic and you want to figure out what is causing this. In a system with multiple types of events, it is a struggle to find the root cause.

    E.g. unhandled events have dead letters. Something similar in some form would be nice to see for unmatched events as well.

    I don't have a concrete proposal, IMO any of the following makes sense:
    - use a similar approach to dead letters and send whole events to azure…

    6 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 →
  13. persist events to store (cosmos or storage etc...)

    Right now you can persist events to a storage account when an event is dead-lettered.

    It would be great if we could persist ALL events to some storage like (cosmosdb) would be insanely useful to implement patterns like event-sourcing, for example.

    Doing this at the domain or topic level would also be very useful. Specific event topics could be persisted to a cosmosdb container.

    A requirement of this would be that the delivery of the events to the store be guaranteed.

    6 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 →
  14. 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

    6 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. 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 →
  16. 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 →
  17. 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 →
  18. Deplying Event Grid Domains via ARM template

    2 weeks ago Event Grid Domains came out of preview, but there doesn't seem to be a way to deploy these via an ARM template.

    Or are ARM templates no longer the preferred way of deploying resources from Azure DevOps?

    3 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 →
  19. Event Grid Support For Changing Blob Container Access Level

    It would be useful for Security Governance purposes if an event was raised whenever a Blob Container access level was changed. It appears that right now, this event is not published by the blob storage event source. Even resource group/subscription event sources do not seem to publish blob container access level changes as Resource Write events, and changing a blob container access level does not appear in the storage account's Activity Log.

    3 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. Advanced Editor in Portal UI should work

    In the Portal UI, when creating an event subscription, there is an Advanced Editor tab. You can use this to create an ARM-style JSON template for the subscription. It could be a very convenient way to quickly create a number of event subscriptions, but it cannot actually be used.

    The "Create" button at the bottom of the screen only works when focused on the "Basic" tab. But changes in the Advanced Editor do are not reflected in the Basic or Additional Features tab. If you go to the Basic tab to hit Create and then back to the Advanced Editor…

    3 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
  • Don't see your idea?

Azure Event Grid

Categories

Feedback and Knowledge Base