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. 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 →
  2. 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 →
  3. 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 →
  4. 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

    4 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 →
  5. Bug/Feature: Support DateTimeOffset instead converting to UTC

    When passing a DateTime(Offset), EventGrid takes the liberty of converting it to a UTC DateTime, which is really not acceptable. I assume this happens when EventGrid deserializes the data, but it should really not change the content of the data property in any way. So, could you please add an option on a topic to configure this behaviour?

    An example payload would be:

    {

    "cloudEventsVersion": "0.1",
    
    "eventType": "SomeType",
    "eventTypeVersion": "1",
    "source": "#something",
    "eventID": "173d9985-401e-0075-2497-de268c06ff25",
    "eventTime": "2018-04-28T02:18:47.1281675Z",
    "data": {
    "DateInUtc": "2018-04-28T02:18:47.1281675Z",
    "DateWithOffset": "2018-04-28T02:18:47.1281675+03:00"
    }

    }

    This then results in (see the changed value of ‘DateWithOffset’):
    {

    "cloudEventsVersion": "0.1",
    
    "eventType": "SomeType",
    "eventTypeVersion":
    4 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 →
  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. 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.

    4 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. Enable Virtual Network Service Endpoints for Event Grid

    Hello Event Grid team!

    We are an internal Microsoft team that uses Event Grid heavily in Azure Functions.

    We would like to ask what is the ETA for you to support Service Endpoints for Event Grid, such that we can access Event Grid from inside our virtual network, as opposed to going through NAT port translation. This is an important feature to us because traffic that goes through the virtual network does not count against the number of outbound connections, which are limited and can cause SNAT port exhaustion.

    Reference: https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-service-endpoints-overview

    3 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 →
  9. We can't see EventGrid.Domains.Topics’ subscriptions in "Event Grid Subscriptions" tab

    We can see EventGrid.Domains and EventGrid.Topics’ subscriptions in this tab. But we can't see EventGrid.Domains.Topics’ subscriptions.

    It is not convenient for customer, please add a new topic type "Event Grid Domain Topic" in this tab's topic type drop down list.

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

    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 →
  11. 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 →
  12. Allow sending event for all topics in a domain

    As an event grid source, I want to publish an event that applies to all tenants of the domain-where each tenant is a topic, so that all topics (tenants) receive the same event and each tenant can manage subscriptions to their topic independent of each other.

    3 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. 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 →
  14. Setup configurable alerts on event grid topic similar to Application Insights

    Be able to configure and have alerts delivered based on delivery (or non-delivery) criteria.

    3 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 →
  15. Make the authentication more flexible, permit keys via QueryString and Anonymous Access

    Event Grid makes custom event integration hard to implement because it requires an authentication key to be passed as part of the request header, but many applications are not flexible enough to define custom headers on webhooks, so it limits a wide usage.

    Expected scenario:
    I would expect to choose different ways of sending the key, via headers, via query-strings or anonymous access.

    3 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 →
  16. Bug/Feature: Advance filtering using source field with Cloud Event Schema v1.0

    Advance filtering does not work properly for some fields when using the new Cloud Event Schema v1.0. Creating a new filter using source field as a key and the string is not in operator do not work. The subscriber receives all the events regardless the source value in the event.

    What's more, advance filtering does not allow using fields from Cloud Event Schema v1.0 spec even if the subscription and the topic are using this v1.0 spec. Those fields are id, type and specversion. According to the validation in the screen, the valid keys are the old one…

    2 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 →
  17. Event Grid

    Enable service endpoints for EventGrid.

    2 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 →
  18. Support for Kafka publisher and subscriber to use EventGrid

    It will be great if EventGrid supported Kafka event publisher and subscriber, ie.. support for Kafka protocol similar to what was done with Azure Event Hub.

    2 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 →
  19. Ability to only accept events being published from whitelisted IP addresses

    Would be great to limit the IP ranges from which the topic endpoint would accept events. Currently a topic endpoint is open to the public internet with no way of securing it further beyond using Key or SAS token authentication.

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

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

Azure Event Grid

Categories

Feedback and Knowledge Base