Event Grid Event Grid
Get reliable event delivery at massive scale
Event Grid is a fully managed event routing service that provides reliable message delivery at massive scale. Developers use Event Grid to build reactive, event-driven apps in a modern, serverless compute architecture—eliminating polling and its associated cost and latency. One-to-many mapping, in which a single event can trigger multiple actions, provides a uniform event consumption experience. A pay-per-operation model complements and extends your serverless solutions and lets you focus on innovation rather than infrastructure.
Event Grid consumption pricing
Event Grid is priced as pay-per-use based on operations performed. Operations include ingress of events to Domains or Topics, advanced matches, delivery attempts, and management calls. Plan pricing includes a monthly free grant of 100,000 operations.
| Price per million operations | Free usage per month |
|---|---|
| ￥ 0.611 | 100,000 operations |
Event Grid pricing example 1
Azure Functions is connected to Blob Storage through Event Grid, to process images each time a new image is added. In the blob storage container 5 million images are created—each one triggering the Function through Event Grid.
- You publish 5 million events to Event Grid in a month.
- All events are published to 1 https endpoint.
| NUMBER OF OPERATIONS | |
|---|---|
| Published events | 5 million operations |
| Delivery attempts | 5 million operations |
| Monthly free grant | - 100,000 operations |
|
Total operations
Price per million operations |
9.9 million
￥ 0.611 |
| Total monthly cost | ￥ 6.0489 |
Event Grid pricing example 2
Incoming logs to Event Hubs are being sent to storage through Event Hubs Capture. Five million log batch events are pushed by Event Grid to Logic Apps for monitoring. All events are also pushed to one of several custom-monitoring endpoints based on the event type, and in some cases the origin of the event. One million of these events require advanced matching. One of the endpoints experiences outages and retries are necessary to successfully deliver the events.
- You publish 5 million events to Event Grid in a month.
- All events are published to 2 https endpoints.
- 1 million of the events require advanced matching.
- 1 million of the events required 2 delivery attempts.
| NUMBER OF OPERATIONS | |
|---|---|
| Published events | 5 million operations |
| Delivery attempts | 11 million operations (1 million for second delivery attempt) |
| Advanced match | 1 million operations |
| Monthly free grant | - 100,000 operations |
|
Total operations
Price per million operations |
16.9 million
￥ 0.611 |
| Total monthly cost | ￥ 10.3259 |
FAQ
Expand AllOverview
-
What are operations and how are they billed?
Operations in Event Grid include all ingress events, advanced match, delivery attempt, and management calls. You’re charged per million operations with the first 100,000 operations free each month.
-
How many Event Subscriptions can I have for each account?
By default, you can have up to 500 Event Subscriptions per topic as per the Event Grid limits documentation.
-
How many custom Topics can I have for each account?
The default limit for custom topics is 100 per Azure Subscription
-
How many Event Grid subscriptions can I have for each account?
You can have up to 1,000 Event Grid subscriptions during the preview period.
-
Which endpoints are supported in Event Grid?
Currently, we support https endpoints. Other endpoints will be supported later.
-
Is there a limit on delivery attempts?
Event Grid will perform an exponential back off for all deliveries. If your WebHook does not return a 2xx, the retry begins immediately. When the back off interval reaches one hour, retries will be performed every hour. After 24 hours, the service will stop attempting to deliver events.
-
What is the maximum retention period?
Event Grid will buffer data for a maximum of 24 hours. At the end of this time, events will be deleted.
-
How is Event Grid event size calculated and charged?
Each 64KB chunk of delivered data is billed as 1 request. For example, a single event of 256KB will be billed as 4 events.
-
Is there a separate charge for using Event Domains?
No, Domains and Topics are treated the same way from a billing perspective. Ingress of an event to Azure Event Grid system is one operation regardless of entry point.
Support & SLA
If you have any questions or need help, please visit Azure Support and select self-help service or any other method to contact us for support.
To learn more about the details of our Service Level Agreement, please visit the Service Level Agreements page.