Idle Azure Function App
On a dedicated or Premium plan the function app bills for its reserved instances continuously, only the Consumption plan scales the charge to zero.
Free to start. No card. The playground just needs your work email.
Azure
Found, explained, handed over.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across Azure, with read-only access to the account.
Explain
Every finding says exactly what to change: Delete the function app with no executions. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Function Apps on Azure
- The fix, by hand
- Check Azure Monitor
FunctionExecutionCount/FunctionExecutionUnitsover 30 days. - If every present execution axis is below the idle floor, the function is unused.
- Delete the function app if no longer needed.
- Otherwise downgrade from Premium/Dedicated to the Consumption plan to drop the standing charge.
- Pausing/stopping the app alone does NOT stop the standing plan charge. Only delete or downgrade reclaims the reported savings.
These are the steps the finding carries in the product.
- Check Azure Monitor
- Category
- Idle resources. Resources running but doing no useful work: zero invocations, no connections, no traffic.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-221- Full reference
Related checks
See the idle resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.