You are on page 1of 5

Introduction to Azure Event Grid

Event Grid overview


Azure Event Grid can be used to build applications with event-based architectures. Event Grid not
only has built in support for events coming from Azure services but also support for your own events
using custom topics. Topics Event Subscriptions

Blob Storage
Event Hubs
Media services
Hybrid connections
Azure Subscriptions
Queue Storage
Resource Groups
Webhooks
Event Hubs
Event Grid Azure Automation
IoT Hub
Logic Apps
Service Bus
Azure Functions
Custom Topics
Event Handlers
Event Sources
Event Grid concepts

01 Event – An event is smallest information about something happened in the system

02 Publisher - User or organization that publish events to event grid

03 Event Source – An Event source is where event happened. For e.g. application

04 Topics - Topic provides an end point where the source sends events

05 Subscription - A subscription tells event grid which events on a topic you are interested in.

06 Event handler – An event handler is the place where event is sent.

07 Security – When subscribing, you must have adequate permissions on the resource or event grid topic.
Event Grid security

Webhook event delivery - Event Grid requires you to prove ownership of your Webhook
endpoint before it starts delivering events to that endpoint. Azure will automatically handles this
if you are using Azure Logic apps event grid connector, Azure automation Webhook and Azure
functions with Event Hub trigger. For others validate either programmatically (ValidationCode
Handshake or manually (ValidationURL handshake).

Event subscription - To subscribe to an event, you must prove that you have access to the
event source and handler. You need to have write access to event handler and must have
Microsoft.EventGrid/EventSubscriptions/Write permission on the resource that is the event
source.

Custom topic publishing - Custom topics use either Shared Access Signature (SAS) or
key authentication
Event Grid domains
An event domain is a management tool for large numbers of Event Grid topics related to the same
application. You can think of it as a meta-topic that can have thousands of individual topics.

With a domain, you get fine grain authorization and authentication control over each topic via Azure's
role-based access control (RBAC)

Subscriber X
Event A
Topic 1 Subscriber Y
Event B
Event Domain

Topic 2

You might also like