A pipit-meadow worker is not always online and cannot expose a public webhook. How can Event Grid still deliver discrete events when the app is ready?
Select an answer to reveal the explanation.
Short Explanation
No public webhook? Pull when you wake up. Namespace-topic pull delivery lets the worker fetch discrete events on its schedule.
Full Explanation
Event Grid supports push and pull delivery. When a pipit-meadow worker is not always online and cannot expose a durable public webhook, pull delivery on namespace topics lets the app fetch discrete events when it wakes. That preserves the Event Grid discrete-event model without requiring a permanent public endpoint.
Requiring a permanent public webhook even when the worker is offline fails the constraint: an unreachable URL cannot receive push, and inventing uptime just to satisfy push is unnecessary when pull exists.
Replacing the workload with Event Hubs solely because the worker sleeps fails as a default answer: Event Hubs is the streaming firehose; sleep/offline discrete consumers are a documented Event Grid pull scenario on namespace topics.
Storing events only in Application Insights logs for manual copy-paste fails delivery: logs are for diagnostics, not an event retrieval API for the worker.
Exam caveat: pull delivery is tied to the namespace topic model—classic custom topics are push-oriented; do not assume every Event Grid resource supports pull. Operational check: publish to a namespace topic, have the worker authenticate and receive/acknowledge events on its schedule, and confirm no public webhook is required.