How can I keep Azure prices down
Last week we had a new person join our team at work. His name is Jack. I asked Jack what the job market was like. He said it wasn't good. I also asked him what skills he believes are in demand. He said cloud.
So, I've got to get experience at Azure, the cloud I know something about. However, I am not going to get much experience at using Azure, or any cloud for that matter, at work. I have experience at migrating small SQL Server databases to Azure SQL. I've created Resource Groups and have done some basic IAM. And I've created several Azure Key Vaults. But I don't have any experience at things like Azure Functions, Azure Logic Apps, using PaaS in Azure, etc. Things that a developer who works designing and implementing cloud solutions would know and do. I have always shied away from getting a cloud account because of the alarmist stories I've heard of developers signing up for an account with a public cloud provider one month, then the following month getting stuck with a bill that runs into the thousands of dollars. Of course, I could sign up for a simple Azure tutorial. I've done that, more than once, but they tend to be very narrow and once I'm done with the course, that's it as far as using Azure anymore goes. (At least, that's always been my understanding.)
But now, given what Jack said, I think I've got to bite the bullet and get an Azure account. But I've GOT to keep it as cheap as possible. For those of you with experience at using your own Azure account, how do you keep the costs down? What advise can you give me, please?
7 Replies
azure gives you $200 of credit for free to start
Azure spending limit - Microsoft Cost Management
This article describes how an Azure spending limit works and how to remove it.
Microsoft doesn't want to over-bill you either. So various configuration and monitoring tools are available to help you understand your spending. Hope you can explore further and slowly gain your confidence on migrating to the cloud.
why dont they just let you set a spending limit
because you limit the functionality of your whole azure to a number
you can set spending limits with budgets
and so when IF something is over the budget it gets disabled (eg you dont get billed anymore) but you whole azure infrastructure doesn't stop working
out of the blue
i think you need to write some scripts to stop the resources tho, but at least u get informed
rule of thumb: NEVER CREATE ANYTHING PUBLIC FACING
someone will find a way to exploit it
i once made the mistake of assigning a public ip to a vm running windows server and somehow they found a vulnerability to exploit the DC through netlogon, this fuck up costed me about 2000 dollars because i had alerts set up in place, otherwsie it would have been a lot more
almost every fuck up comes from egress GB
but that just sends a notification
i mean they could implement it properly UX wise
with warnings and whatnot
and i imagine people who use it would have that in mind
its not for companies its for individual users
yeah i agree 100%, but i guess they want to keep it as hard as possible to make as much money as possible