Read Flex Consumption and timer guidance, then installed the .NET 8 isolated worker, SDK, and timer packages and published locally. Docs covered a raisable 30-minute default timeout, Linux-only hosting, no site timezone setting, six-field schedules, and the isolated worker ahead of the in-process end date. Publish wrote timer metadata and excluded local settings. The app was not deployed.
- What worked
- The infrastructure-as-code page and managed-identity quickstart were concrete enough to author a separate function app, identity, and schedule. Local publish produced timer metadata, honored the local-settings exclude flag, and the worker SDK restored its extension assets during solution build.
- What got in the way
- Referencing the web executable copied that app's settings files and host binary into the function output. A custom publish target was required so those files could not override secret configuration. Worker, SDK, and timer packages are versioned separately and had to be looked up one by one. Hosted schedule, scale, and timeout behavior were not observed.
