Last year I ran into a solution composed primarily of WebJobs processing queue items. The daily bill for the WebJobs plus the associated storage account averaged out to about $800 a day.
These services processed several million queue messages a day.
We attempted to use the WebJobs dashboard for debugging but given the quantity of requests the UI was mostly unusable. In order to cut down storage costs we turned off the WebJob dashboard by removing the AzureWebJobsDashboard connection string.
This change cut the cost down to a little over $400 a day. Almost $150k year saved by turning off an unusable feature.
As far as I know this is only relevant to legacy WebJobs before version 3. The official documentation has also been updated to note WebJobs dashboard shouldn’t be used in high throughput production scenarios.
Might be old news to most WebJobs users, but I’m sure there are quite a few production deployments out there with this still enabled. If you’re one of them hurry up and disable it. Turn it on when you need to do debugging, If you need persistent logging look into an Application Insights implementation.