azurerm_eventgrid_domain cost estimation

An azurerm_eventgrid_domain is a management container for many Event Grid topics, used to publish and route events to large numbers of subscribers (e.g. per-tenant or per-customer topics). Cost is per operation — ~$0.60 per million, with the first 100,000 operations each month free. 10M operations is ~$6/month.

An operation is an event ingress, a delivery attempt, an advanced filter match, etc. — so cost scales with event volume and fan-out (more subscribers means more delivery operations per event). It's an inexpensive, pure-usage service with no standing fee; even high-volume event routing stays in the tens of dollars for typical workloads.

There's little to optimize beyond not generating operations you don't need: avoid unnecessary subscriptions (each delivery is an operation), and use filtering at the subscription level so events only route to subscribers that want them rather than fanning out broadly and discarding.

c3x prices the domain from monthly operations as usage, so projected cost can be modelled.

Terraform example

A minimal but realistic configuration that C3X can estimate.

resource "azurerm_eventgrid_domain" "events" {
  name                = "tenant-events"
  location            = azurerm_resource_group.main.location
  resource_group_name = azurerm_resource_group.main.name
}

Pricing dimensions

What you actually pay for when you provision azurerm_eventgrid_domain.

Dimension	Unit	What's being charged
Event operations	per 1M operations	Ingress, delivery attempts, and advanced filter matches. First 100K/month free, then ~$0.60/million. Scales with event volume and fan-out. $0.60/million (after 100K free) → 10M ≈ $6/month

Sample C3X output

10M event operations in a month:

azurerm_eventgrid_domain.events
└─ Event operations   10 × 1M-operations   $6.00
                      Monthly               $6.00

Optimization tips

Common ways to reduce azurerm_eventgrid_domain cost without changing the workload.

Filter at the subscription level

Proportional to deliveries avoided

Each delivery is a billable operation. Use subscription filters so events route only to subscribers that want them, rather than fanning out broadly and having subscribers discard events they didn't need.

Avoid unnecessary subscriptions

Per subscriber removed

Fan-out multiplies delivery operations — N subscribers to a topic means N delivery operations per event. Keep the subscription set to consumers that actually process the events.

Use the free tier for low-volume routing

Up to 100K operations/month free

The first 100K operations each month are free, covering small or bursty event workloads entirely. Event Grid only becomes a meaningful (still small) cost at millions of operations.

FAQ

How is an Azure Event Grid Domain billed?

Per operation — ~$0.60 per million, with the first 100K/month free — where an operation is an ingress, delivery attempt, or advanced filter match. 10M operations is ~$6/month. It's an inexpensive, pure-usage service with no standing fee.

What counts as an Event Grid operation?

Event ingress, each delivery attempt to a subscriber, and advanced filter evaluations. So fan-out matters — more subscribers means more delivery operations per event. Filtering keeps deliveries (and operations) to relevant subscribers.

How does c3x estimate the cost?

Event Grid is usage-driven, so c3x models it from monthly operations in c3x-usage.yml (above the free 100K). There's no standing fee to price.

Related resources

AWS

aws_sqs_queue

AWS messaging counterpart — compare event/messaging patterns and cost

`azurerm_eventgrid_domain` cost estimation