Azure Event Grid Topic
Does ZopNight manage Azure Event Grid Topic?
Event Grid topics bill per operation, and their costs are usually small; the value of tracking them is structural. ZopNight discovers every custom topic via Resource Graph and attributes its per-operation spend; checking for topics left with 0 active subscriptions after their consumers were deleted is a manual review.
Rules that fire on Azure Event Grid Topic
No active rule family targets Azure Event Grid Topic today. Rules that used to are retired, and retired rules publish no pages and fire no findings. Scheduling and permissions coverage are unaffected.
At a glance
| Field | Value |
|---|---|
| Scheduling notes | discovery only. |
Event Grid topics route events between services on a pay-per-operation model. Costs are usually small, but topics map the event-driven wiring of an environment.
Pay-per-operation events, near-zero idle cost
Event Grid meters operations: event ingress, delivery attempts, and management calls. A topic’s bill scales with the events flowing through it, and an idle topic costs effectively nothing. That places topics near the bottom of any cost-ranked inventory and near the top of the architectural one: every subscription on a topic is an edge in the environment’s event-driven graph, naming exactly which service reacts to which signal.
Topic discovery as a dependency map
Discovered via Azure Resource Graph as a topic record; ZopNight does not read event subscriptions, so the wiring check happens in the portal. When the services around a topic come up for stopping or rightsizing, that wiring is what says who publishes into it and who consumes out of it, context a raw resource list cannot provide. Topics themselves are discovery-only in ZopNight; with no reserved capacity, there is no meter worth scheduling against.
Orphaned topics after consumers move on
The hygiene patterns here are structural rather than financial. Topics whose subscriptions all point at deleted functions or dead webhooks, delivering into the void and burning retries. Topics with no subscriptions left at all, publishing events nobody hears. And custom topics duplicated per environment long after those environments were consolidated. Each one costs very little on its own, and each is a small piece of architectural debt that makes the event graph harder to reason about, which is why cleanup is worth doing even when the invoice barely notices.
Event Grid topics in the portal list
Azure portal → Event Grid Topics lists custom topics in the subscription. Each topic’s Overview shows its event subscriptions, its publish endpoint, and per-topic charts for published and delivered events, enough to tell a live topic from an abandoned one in a few seconds.