Saving Money by Deleting Azure Resource the Right Way

[@princefowzan]

Hey Tim, I actually watched your both videos about deploying web apps and static web apps and also followed up. And that's when I actually realized that Azure is big sea is there is a lot to learn. Since I had github student pack, maybe I was also charged. But I'm not really knowledgeable about that. So I would like to ask you to make like a master class or something specifically for Azure. Maybe use web app for example. 😊🎉

[@IAmTimCorey]

I have a complete course on Azure: www.iamtimcorey.com/courses/azure-from-start-to-finish/ You are right, though, that there is a LOT to cover. I'll be doing more courses in the future that will cover it as well.

[@gower1973]

Seems kind of a jank design, why have something that might have resource dependencies and not clearly show that they are tied to that resource, it should warn you that you are about to delete something that has other resources attached.

[@IAmTimCorey]

How would it know? Yes, when you create a resource and it creates other associated resources, you would think that this would tie the two together. However, that's not how it works for a good reason. Imagine for a minute that you create a Virtual Machine (VM). It creates a storage account as part of the setup (it tells you this during the process). Now you want to delete the VM. Should Azure tell you to also delete the storage account? The answer would seem to be yes, but here is the problem: what if, in the meantime, you started using that storage account for something else as well? If you delete it, you delete not just the VM's info but also the other info you've been storing there. Cloud resources are often intertwined. The only real way to delete them is EXTREMELY cautiously. When you are creating resources, you can set yourself up for long-term success by following certain patterns (like only using a resource group for one resource, for example). If you follow those patterns, you can more easily delete resources with confidence. However, Azure can't assume for you that you are doing that.