In a recent post about implementing Azure’s Application Insights in a webjob, I mentioned in passing the need to have a storage account in order to actually run the webjob. I didn’t cover then how to go about creating that because THAT post was already taking close to a minute and a half just to scroll…so here we are.
In addition to being a really convenient and relatively cheap way to store files “on the cloud,” Azure will require storage accounts to be associated with many resources (like webjobs, machine learning workspaces, and virtual machines) so those resources have a place to store their logs, temp files, another other such critical things.
What, you thought Microsoft would just foot the bill for that kinda thing, or build it into the resource price? Come on now.
While docs.microsoft has a really good explanation on the details behind storage accounts, their varieties, how pricing is determined, etc, they don’t actually walk you through it–probably because doing it through the portal is a really easy process. But if you’re anything like me, you appreciate a little handholding the first time you create something you’re paying money for.