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

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

    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 →
  4. 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 →
  5. 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 →
  6. 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 →
  7. 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":…

    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 →
  8. 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 →
  9. 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 →
  10. 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

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

    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 →
  14. 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 →
  15. 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 →
  16. 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 →
  17. Connect CosmosDB

    Similar to the CosmosDB ChangeFeed, please provide Insert, Update, Delete events for Documents (SQL), Vertices and Edges (Graph), STored Procedures, Users, Attachments, etc.

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

    We’ll send you updates on this idea

    0 comments  ·  Event Sources  ·  Flag idea as inappropriate…  ·  Admin →
  18. Ability to specify event source that some subscribers can use to filter events

    Allow event publishers to specify their names or source types when publishing events so that subscribers can use that information to specify events they want to receive. Yes, you can combine the publisher name/type within the event types but this increases the number of event types.

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

    We’ll send you updates on this idea

    0 comments  ·  Event Sources  ·  Flag idea as inappropriate…  ·  Admin →
  19. Better way to specify Event Type using the Azure Portal

    Azure Portal allows me to specify event types that each subscriber accepts. One event type at a time through the UI. This is horribly cumbersome because I have a lot of event types and a lot of subscribers. There must be a better way. Maybe I can submit a list of event types in comma delimited or json format?

    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 →
  20. Allow/Deny the Publisher for specific Event Types

    Allow / Deny Publisher for specific Event Types to publish to the Event Grid. Otherwise we have to build a router service for this. Detailed discussion is https://stackoverflow.com/questions/49865705/is-it-possible-to-restrict-the-event-publisher-to-send-specific-event-types-in-a

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

    We’ll send you updates on this idea

    0 comments  ·  Event Sources  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Azure Event Grid

Categories

Feedback and Knowledge Base