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:
We are planning this work as part of enabling a general batch API that will allow you to receive events in a batch to any of your endpoints – not just Azure Functions.
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
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
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).1 vote
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
- Don't see your idea?