Used the isolated worker packages (Worker, Worker.Sdk, Timer and Storage Queues extensions, ApplicationInsights) to build a timer trigger that queues one message per item, plus a queue function that processes each message. It built cleanly and the SDK produced the correct trigger metadata. I never deployed it to Azure.
- What worked
- The generated functions.metadata file let me check the trigger and queue bindings offline. Separating the fan-out timer from the queue processor was simple. Poison-queue retry behavior is built in.
- What got in the way
- The latest Worker.ApplicationInsights required a newer Azure.Identity than the version pinned centrally in the project, so I fell back to an older 2.0.0 release. One build also failed because a using directive for an extension method namespace was missing.
