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.

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

    We’ll send you updates on this idea

    unplanned  ·  4 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  2. Monitor Event Grid

    Implement monitor capabilities such as Azure Monitor and Alerts for Event Grid.

    30 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 →
  3. Allow EventGrid to add authentication headers on requests it makes to endpoints

    At the moment when EventGrid calls an http endpoint it only allows authentication information to be passed along in the querystring - which means that authentication information can be logged in IIS logs.

    It would be better to allow the option for Event Grid to use an authentication header (such as integrating with AAD to obtain a service token) to prevent leakage of tokens.

    27 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 →
  4. Advanced filtering scenarios, Subject Wildcard, Regex & Data Filters

    The subscription filters are very limited, I can only filter the events based on subject and Event Type, and the current filter options does not help much for advanced scenarios.

    It would be more flexible if we could define filters by regex or wildcard on EventTypes and Subjects, and also have filters on data attributes

    - EventType using WildCards.
    - -> Use: [ "Microsoft.Storage.*", "Microsoft.EventHub.*"]
    - -> Instead of: [ "Microsoft.Storage.BlobCreated", "Microsoft.Storage.BlobDeleted" ]

    - Subject filter by WildCard, Contains or Regex:
    - -> Use > subject : match("blobServices/default/containers/mycontainer/log/*.jpg")
    - -> Or > subject : match("blobServices/default/containers/mycontainer/log/*.[jpg|gif|png]")
    - -> Or > subject…

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

    With our new advanced filters, we’ve added data attribute filters and StringContains as an operator (among many others). Take a look and let us know what you think!

    We will likely not add wildcards and regex for quite some time due to the compute and latency costs it would incur, however, we think, most of the use-cases described (and more) can be addressed with our new filters: https://docs.microsoft.com/en-us/azure/event-grid/event-filtering#advanced-filtering

  5. Support file (share) storage events

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

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

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Allow KeyVault to emit events using Event Grid when secret, certificate or permission changes

    Allow KeyVault to emit events using Event Grid when secret, certificate or permission changes. That will help customers react to KeyVault events like a secret value or content type changed or a secret is enabled or disabled or a permission on KeyVault changed etc

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

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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...

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

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

    We’ll send you updates on this idea

    3 comments  ·  Event Handlers  ·  Flag idea as inappropriate…  ·  Admin →
  9. Add support for AAD authentication

    Add support for AAD authentication and managed identities alternatively to shared secrets access...like ServiceBus is doing already...

    14 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. Static public IP address

    I wish it had a static IP address or IP range which can be allowed on firewall for communication with resources within a VNet or atleast a VNet service endpoint.
    How are we supposed to allow Event grid talk to API sitting inside a Vnet without disabling the firewall?

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

    12 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 →
  12. 11 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Event Sources  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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.

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

    10 votes
    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 →
  15. 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.

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

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

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

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

    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. 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 →
  20. 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 →
← Previous 1 3
  • Don't see your idea?

Azure Event Grid

Categories

Feedback and Knowledge Base