Azure Function App
Does ZopNight manage Azure Function App?
Azure Functions on the Consumption plan bill per execution and scale to zero, but Premium and dedicated plans reserve compute that bills while idle. ZopNight tracks execution activity over 60 days and stops non-production apps via the Web Apps stop operation, though the underlying plan keeps billing until rightsized.
Rules that fire on Azure Function App
At a glance
| Field | Value |
|---|---|
| Scheduling notes | stopped and started via the Web Apps stop/start operation, taking the app fully offline while stopped. |
Azure Functions run event-driven code, either serverless on Consumption or on always-on Premium and dedicated plans. Functions on dedicated plans bill for reserved compute even when idle.
Which plan a function runs on decides its meter
The word “serverless” in a function’s description says nothing about its bill; the hosting plan does. On Consumption, executions are metered as they happen and an idle function costs effectively nothing. On Premium, pre-warmed instances hold compute continuously to eliminate cold starts, and that reservation bills whether a single trigger fires or none do. On a dedicated App Service plan, the plan’s SKU bills around the clock and the function is just a tenant. The same code, deployed three ways, produces three unrelated invoices.
Taking a Function App offline on schedule
ZopNight stops and starts Function Apps through the Web Apps stop/start operation, which takes the app fully offline while stopped: triggers stop firing, HTTP endpoints stop answering. For dev and staging apps on Premium or dedicated hosting, that removes the idle execution layer overnight. The caveat carried on this type’s stub is the important one: stopping the app does not shrink an underlying dedicated App Service plan, which continues billing at its SKU until it is downsized or emptied. Pair app schedules with plan rightsizing for the full saving.
Function-app evidence ZopNight gathers
Discovery via Azure Resource Graph includes plan and runtime detail, so every function is known by what hosts it. A 60-day Azure Monitor lookback shows execution activity, Cost Management ties spend back to the app, ML auto-tagging covers this type, and schedules handle non-production apps outside working hours.
Idle functions on reserved compute
Watch for Premium plans chosen to fix one cold-start complaint and never revisited; timer-triggered jobs on dedicated plans that run minutes per day; and staging slots of production function apps inheriting always-on hosting they never needed.
Function Apps in the portal
Azure portal → Function App → select the app. The Overview shows its status and, critically, its App Service plan, the link to follow before assuming a stopped function costs nothing.