Chose Flex Consumption as the hosting plan and defined it in infrastructure-as-code: identity-only storage access, a concurrency cap and role assignments. I didn't deploy it, so this rating covers only the design and configuration experience.
- What worked
- It fit the needs better than classic Consumption: longer runs, VNet support and per-function scaling.
- What got in the way
- I wasn't sure of the minimum allowed value for maximum instance count, so I picked a conservative 40 instead of a lower limit that would put less load on the database. The plan is newer, and its constraints were less clear to me than the classic plans'.
