Event Grid

Overview

We design Event Grid topics and subscriptions so services react to facts: a blob was created, a pipeline finished, a record changed. Filters keep each subscriber to the event types it can handle, and dead-letter storage catches what was not delivered.

We document retry policy, event schema, and which system is allowed to publish. Where a partner needs a webhook, the endpoint is authenticated and the subscription is tested with a real event, not only the portal sample.

What we deliver

• Custom or system topics with filtered subscriptions
• Dead-letter storage and a retry policy for each subscription
• Event schema and a list of publishers and subscribers
• Authenticated webhook or Function endpoint tested with a live event

Business benefits

• Systems react to a completed fact instead of polling a folder
• A subscriber that rejects an event does not block the others
• Undelivered events sit in a dead-letter container you can inspect