A lupine-hill Event Grid topic exists, but nothing runs when events publish. What delivery contract is still missing?
Select an answer to reveal the explanation.
Short Explanation
A topic without a subscription is a mailbox with no address label. Create an event subscription that points at the Function, webhook, or other official handler.
Full Explanation
An Event Grid topic alone does not invoke anything. Delivery requires an event subscription that binds the topic (or domain/system topic) to a destination—Azure Function, webhook, Event Hubs, Service Bus, Storage Queue, and other supported handlers. Without that subscription on lupine-hill, published events have nowhere to go, which is why “nothing runs.”
A Dockerfile that rebuilds the topic every hour fails because rebuilding infrastructure does not create a delivery contract to a handler.
A Redis cache warming job labeled “subscription” fails: naming a cache job after a subscription does not create an Event Grid event subscription resource.
An Application Insights workbook that replaces handlers fails because workbooks visualize telemetry; they are not Event Grid destinations that execute your Function when events publish.
Exam caveat: filters, dead-lettering, and retry settings live on the subscription—not only on the topic—so operational reliability is configured where delivery is defined. Operational check: create an event subscription pointing at the Function or webhook, publish a test event to the topic, and confirm the destination is invoked; delete the subscription and verify publishes no longer trigger the handler.