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.

How can we improve Azure Event Grid?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Validating a custom topic and event domain endpoints for subscription webhook event handler

    This feature will simplify cascading of the Azure Event Grids for multi-tenants across the different AD accounts.
    Currently, we can subscribe an Azure Event Grid via the custom topic to the event subscription, but we need to add an EventGridTrigger function for validatingUrl.

    See more details about the AEG cascading in the example: https://stackoverflow.com/questions/55342241/handle-blob-events-from-storage-accounts-in-multiple-azure-subscriptions-in-diff

    Thanks
    Roman

    1 vote
    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. 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.

    1 vote
    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. Explicit option for validating the subscription

    Currently there are two ways of validating the subscription it's either using Validation code or using Validation URL.

    Currently the Create EventGrid REST API return 201 instantly and wait for 10 mins for manual verification for event subscription if Validation code does not exist.

    Can you provide expicit option for validation the subscription? Maybe default would be validationURL if not provided.

    I would recommend our customer to use Validation code verification only but incase they fail to write that code. We need to handle the fall the 10 min scenario.

    1 vote
    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 →
  4. 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.

    1 vote
    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 →
  5. 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?

    1 vote
    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. Dynamically delay for sending a dead-letter message to the dead-letter endpoint

    Currently, there is a five-minute delay between the last attempt to deliver an event and when it is delivered to the dead-letter location. This delay is intended to reduce the number Blob storage operations.

    Note, that this delay time is the same for any retry interval, so for instance, when the maxDeliveryAttempts = 3 (such as 1 minutes) we can received an event from the dead-letter storage after 5 minutes. For eventing driven push model is this latency too much.

    On the other hands, where the maxDeliveryAttempts > 7 (such as over 1 hour) this latency time is not significant…

    1 vote
    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 →
  7. Azure Event Grid available in more regions

    I like the idea of Event Grid. But we cannot use it unless it becomes available for regions we are using for our software.

    For us the missing region is Australia.

    1 vote
    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. Filter Azure Subscription topics by resource type

    It seems like a common requirement to filter events from an Azure Subscription topic by resource type, but this is currently not possible. The subject of these events contains a resource ID, which of course has the resource type in the middle. This means we can't use the supports startsWith/endsWith filters to filter by resource Type.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    unplanned  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
1 3 Next →
  • Don't see your idea?

Azure Event Grid

Feedback and Knowledge Base