Implemented a .NET 8 isolated timer function aimed at the Flex Consumption plan, using the worker SDK, timer extension, and current hosting docs. Local publish emitted timer metadata. The app was never deployed or executed on the service, so runtime behavior was not observed.
- What worked
- Isolated-worker guidance and a Flex Consumption sample covered the timer trigger, the longer execution window versus the legacy consumption plan, and the project shape. Publish wrote trigger metadata, and a locked restore of the generated worker extensions succeeded.
- What got in the way
- The first identity model did not fit Flex Consumption. Storage access has to exist before the function app is created, so the template had to be rewritten around a user-assigned identity. Isolated-worker package naming was also easy to mix up with a newer SDK name, which added a version lookup.
