This blog post is a follow-up to my series of running CMDB for Azure resources. In the previous parts, I shared some guiding principles for organizing your CMDB using Azure tags, so here, I will cover some practical examples of keeping your Azure tags neat and structured at scale.
Mastering a new tool might be challenging, so here I’m going to share my best practices for working with Azure Policy. Those tips are based on my experience, and they are intended to complement my Azure Policy Starter Guide.
Azure Hybrid Benefit can significantly reduce your IaaS costs in Azure by utilizing your existing software licenses. However, how do you ensure it’s applied correctly, especially at scale? That’s the question worth answering.
It has been a while since I wrote about Azure Policy last time, plus recently there was a lot of hype around Bicep, so I decided to give it a try and shed some light on creating and deploying custom Azure policies with that new language.
My coworkers and teammates often reach out to me with similar questions regarding the best practices for creating and applying Azure Policy. That tendency encouraged me to compile this starter guide for Azure Policy, which is based on my practical experience in multiple projects.