The primary intent of having a naming convention for Azure resources is to be able to identify essential information about a resource, for example: * related
Last fall Microsoft announced a new cost-saving option for your workloads in Azure called Savings Plans. Many customers who already were using Reservations (aka Azure Reserved Instances) to save on their cloud costs mistakenly perceived Savings Plans as a replacement for them.
This is probably one of the Top-10 questions I hear from the customers running their workloads in Azure. The question’s intent might vary, but
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.
Using Azure Reservations is one of many technics to optimize your cloud spend in Azure. They are a great option to reduce costs for Azure resources with a long lifespan and predictable utilization.