Built a .NET 8 isolated worker with a monthly timer trigger and an HTTP replay function, targeted at the Flex Consumption plan. Plan docs made the longer default timeout and scale-to-zero behavior clear enough to choose Flex over classic consumption. Worker 2.52.0, the worker SDK, the timer extension 4.3.1, and the ASP.NET Core HTTP extension restored and published locally, including generated function metadata. Quickstart material disagreed on a storage role id and included ftpsState, which Flex rejects, so the template and deploy step were corrected from those docs. The plan was not deployed.
- What worked
- The isolated worker programming model fit the existing .NET 8 stack. Local publish produced function metadata, and the Flex plan page explained the timeout gap versus the 10-minute classic consumption cap.
- What got in the way
- Hosting samples were hard to apply safely. A quickstart role id conflicted with another published built-in id, and ftpsState in site config is unsupported on Flex and is associated with deployment failures. Cloud scale, timeout, and identity behavior were not observed.
